Description
Preserve explicitly supplied restorative-session attendance consent metadata.
Justice records separate consent status, case identifiers, interpreter appointments, document versions and event clocks. A supplied time-string match does not establish a scheduling conflict, and a precision label does not anonymize a record. Local reimbursement and hearing-date arithmetic do not determine legal eligibility, compliance or appropriate action.
Preserve explicitly supplied restorative-session attendance consent metadata.
When to use this tool
Use Restorative Session Attendance Consent Token when you already have sessionId, attendeeId, suppliedConsentCode and need to preserve explicitly supplied restorative-session attendance consent metadata.
How to use the tool and how it works
- Enter sessionId, attendeeId, suppliedConsentCode. 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 sessionId, attendeeId, suppliedConsentCode 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 |
|---|---|---|
| sessionId | Session Id | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| attendeeId | Attendee Id | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| suppliedConsentCode | Supplied Consent Code | 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": {
"sessionId": "S17",
"attendeeId": "A4",
"suppliedConsentCode": "recorded"
},
"output": {
"token": "[\"S17\",\"A4\",\"recorded\"]"
}
}Limitations and assumptions
- The result records supplied values without establishing consent validity. 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
Check authoritative case, service, consent and scheduling records with the applicable rules for an actual justice matter. Verify timestamps, permissions and interpretation context; local labels and signed intervals do not establish legal effect, identity or a valid proceeding.
References
Similar or alternative tools
- Public Case Number Year Token
Encode an exact public case-number and year transcription with a supplied court namespace.
- Justice Referral Document Version Pair
Record explicit justice-referral document and version identifiers.