Skip to content

Main content

Public Peace Notice Region Precision Code

Preserve an explicit public-notice region precision code without deriving or exposing a location.

Loading tool…

Description

Preserve an explicit public-notice region precision code.

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.

Preserve an explicit public-notice region precision code.

When to use this tool

Use Public Peace Notice Region Precision Code when you already have noticeId, suppliedRegionPrecisionCode, source and need to preserve an explicit public-notice region precision code.

How to use the tool and how it works

  1. Enter noticeId, suppliedRegionPrecisionCode, source. 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 token. Use the output convention below.

Enter noticeId, suppliedRegionPrecisionCode, source 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 fieldMeaning and unitsAccepted input
noticeIdNotice IdRequired. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192.
suppliedRegionPrecisionCodeSupplied Region Precision CodeRequired. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192.
sourceSourceRequired. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192.
Output fieldInterpretationReturned shape
tokenTokenRequired. Text; maximum UTF-16 length 8192.
json
{
  "input": {
    "noticeId": "N17",
    "suppliedRegionPrecisionCode": "REGION-ONLY",
    "source": "Source A"
  },
  "output": {
    "token": "[\"N17\",\"REGION-ONLY\",\"Source A\"]"
  }
}

Limitations and assumptions

  • The result records supplied values without deriving or exposing a location. 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

  1. Calculation and input contract: peace-studies/public-peace-notice-region-precision-code — tool.io

Similar or alternative tools