Description
Preserve explicit treaty-notice dispatch and receipt date wording.
Treaty and diplomatic records separate action labels, recorded conditions, versions, source locators and financial contributions. A set of true condition flags differs from a verified legal act or entry into force. Dates and translations need the authoritative record and applicable definitions before legal interpretation.
Preserve explicit treaty-notice dispatch and receipt date wording.
When to use this tool
Use Treaty Notice Received Dispatched Date Pair when you already have noticeId, dispatchedDateText, receivedDateText and need to preserve explicit treaty-notice dispatch and receipt date wording.
How to use the tool and how it works
- Enter noticeId, dispatchedDateText, receivedDateText. 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 noticeId, dispatchedDateText, receivedDateText 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 |
|---|---|---|
| noticeId | Notice Id | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| dispatchedDateText | Dispatched Date Text | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| receivedDateText | Received Date Text | 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": {
"noticeId": "N17",
"dispatchedDateText": "2026-10-28",
"receivedDateText": "2026-11-01"
},
"output": {
"token": "[\"N17\",\"2026-10-28\",\"2026-11-01\"]"
}
}Limitations and assumptions
- The result records supplied values without choosing the legally effective date. 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 treaty, notice, authentic text and status record when assessing an obligation or effective act. Reconcile full contribution ledgers and condition evidence; a local count, share or source-qualified key does not establish legal effect.
References
Similar or alternative tools
- Public Agreement Translation Version Pair
Pair explicit agreement and translation version identifiers.
- International Resolution Amendment Suffix
Qualify an explicit resolution amendment label by source edition.