Skip to content

Main content

Professional Boundary Scenario Tag

Encode an explicit scenario/category/assessor annotation without evaluating professional conduct.

Loading tool…

Description

Encode an explicit scenario/category/assessor annotation.

Ethical records distinguish assumptions, permissions, role assignments, reported conflicts and source-qualified claims. A supplied truth flag can be negated mechanically without evaluating a rule, while a disclosure marker does not prove an acceptable practice. Ethical interpretation depends on evidence, context and the affected people.

Encode an explicit scenario/category/assessor annotation.

When to use this tool

Use Professional Boundary Scenario Tag when you already have scenarioCode, boundaryCategory, assessorCode and need to encode an explicit scenario/category/assessor annotation.

How to use the tool and how it works

  1. Enter scenarioCode, boundaryCategory, assessorCode. Use the units and conventions below.
  2. Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
  3. Read tag. Use the output convention below.

Enter scenarioCode, boundaryCategory, assessorCode using the field constraints below. Encode these values, in exactly that order, as a JSON array and return the serialized array as text in tag. String values are preserved without trimming or external terminology lookup.1

Input fieldMeaning and unitsAccepted input
scenarioCodeScenario CodeRequired. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192.
boundaryCategoryBoundary CategoryRequired. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192.
assessorCodeAssessor CodeRequired. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192.
Output fieldInterpretationReturned shape
tagTagRequired. Text; maximum UTF-16 length 8192.
json
{
  "input": {
    "scenarioCode": "S17",
    "boundaryCategory": "dual-role",
    "assessorCode": "A3"
  },
  "output": {
    "tag": "[\"S17\",\"dual-role\",\"A3\"]"
  }
}

Limitations and assumptions

  • The result records supplied values without evaluating professional conduct. Sources and asserted relationships are not independently authenticated.
  • Inputs must satisfy both the field types and the cross-field conditions above. Invalid input causes an error; a successful false flag or documented placeholder is a different result.

Alternative or Complementary methods

Read the underlying case, source, policy and consent records. Assess duties, authority, affected interests and actual circumstances through the appropriate professional process; local tokens and boolean checks do not resolve an ethical or legal question.

References

  1. Calculation and input contract: applied-ethics/professional-boundary-scenario-tag — tool.io

Similar or alternative tools