Description
Build an explicit source-qualified public-event version key.
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.
Build an explicit source-qualified public-event version key.
When to use this tool
Use Ceasefire Public Event Double Count Key when you already have sourceNamespace, publicEventId, sourceVersion and need to build an explicit source-qualified public-event version key.
How to use the tool and how it works
- Enter sourceNamespace, publicEventId, sourceVersion. 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 sourceNamespace, publicEventId, sourceVersion 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 |
|---|---|---|
| sourceNamespace | Source Namespace | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| publicEventId | Public Event Id | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| sourceVersion | Source Version | 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": {
"sourceNamespace": "SRC17",
"publicEventId": "EV2",
"sourceVersion": "v2"
},
"output": {
"token": "[\"SRC17\",\"EV2\",\"v2\"]"
}
}Limitations and assumptions
- The result records supplied values without verifying events or performing probabilistic matching. 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
- Public Peace Notice Region Precision Code
Preserve an explicit public-notice region precision code.
- Community Dialogue Transcript Consent Marker
Record explicit community-dialogue transcript purpose-permission metadata.