Description
Encode an ordered pair of explicitly affected roles for an ethics case.
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 ordered pair of explicitly affected roles for an ethics case.
When to use this tool
Use Ethics Case Affected Role Pair when you already have caseId, firstRole, secondRole and need to encode an ordered pair of explicitly affected roles for an ethics case.
How to use the tool and how it works
- Enter caseId, firstRole, secondRole. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read token. Use the output convention below.
Enter caseId, firstRole, secondRole using the field constraints below. Encode these values, in exactly that order, as a JSON array and return the serialized array as text in token. String values are preserved without trimming or external terminology lookup.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| caseId | Case Id | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| firstRole | First Role | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| secondRole | Second Role | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| token | Token | Required. Text; maximum UTF-16 length 8192. |
{
"input": {
"caseId": "C17",
"firstRole": "participant",
"secondRole": "researcher"
},
"output": {
"token": "[\"C17\",\"participant\",\"researcher\"]"
}
}Limitations and assumptions
- The result records supplied values without ranking interests. 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
Similar or alternative tools
- Procurement Claim Source Version Label
Associate a procurement claim with its explicit source and version.
- Professional Boundary Scenario Tag
Encode an explicit scenario/category/assessor annotation.