Description
Record explicit community-dialogue transcript purpose-permission metadata.
Peace-program records distinguish stated preferences, source-version event keys, reported fulfillment and actual verified agreements. A recorded closed issue does not establish consent or compliance. Local time and funding balances organize supplied administrative evidence without contacting people, identifying locations or adjudicating events or rights.
Record explicit community-dialogue transcript purpose-permission metadata.
When to use this tool
Use Community Dialogue Transcript Consent Marker when you already have transcriptId, permittedPurpose, permissionRecorded and need to record explicit community-dialogue transcript purpose-permission metadata.
How to use the tool and how it works
- Enter transcriptId, permittedPurpose, permissionRecorded. 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 transcriptId, permittedPurpose, permissionRecorded 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. Boolean permission or verification fields are recorded assertions, not authorizations.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| transcriptId | Transcript Id | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| permittedPurpose | Permitted Purpose | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| permissionRecorded | Permission Recorded | Required. Boolean. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| token | Token | Required. Text; maximum UTF-16 length 8192. |
{
"input": {
"transcriptId": "TR17",
"permittedPurpose": "analysis",
"permissionRecorded": true
},
"output": {
"token": "[\"TR17\",\"analysis\",true]"
}
}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 the original agreement clause, event source, reported status and recorded consent purpose when evaluating a claim. Reconcile funding and report timelines separately; one key or status label does not authenticate an event, verify fulfillment or initiate contact.
References
Similar or alternative tools
- Ceasefire Public Event Double Count Key
Build an explicit source-qualified public-event version key.
- Peace Accord Clause Fulfillment Source Label
Preserve an explicitly sourced peace-accord clause fulfillment label.