Description
Pair explicit primary and deputy continuity-role identifiers.
Defensive administrative records connect notices, approvals, owners, policy versions and declared clock conventions. A signed-off label or an active-owner flag describes supplied records rather than granting access or authenticating a control. Clock offsets require an explicit sign and common epoch before timestamps can be compared as an ordered log.
Pair explicit primary and deputy continuity-role identifiers.
When to use this tool
Use Continuity Role Primary Deputy Label when you already have roleId, primaryRecordId, deputyRecordId and need to pair explicit primary and deputy continuity-role identifiers.
How to use the tool and how it works
- Enter roleId, primaryRecordId, deputyRecordId. 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 roleId, primaryRecordId, deputyRecordId 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 |
|---|---|---|
| roleId | Role Id | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| primaryRecordId | Primary Record Id | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| deputyRecordId | Deputy Record Id | 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": {
"roleId": "ROLE17",
"primaryRecordId": "P2",
"deputyRecordId": "D2"
},
"output": {
"token": "[\"ROLE17\",\"P2\",\"D2\"]"
}
}Limitations and assumptions
- The result records supplied values without granting access or authority. 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 original notices, controlled policy versions and current role records when assessing authorship or ownership. For event ordering, reconcile documented clock offsets and timestamp precision against the original logs; this helper does not authenticate or synchronize them.
References
Similar or alternative tools
- Emergency Contact Response Channel Label
Preserve an explicit emergency-contact response-channel preference.
- Drill Observation Time Precision
Qualify explicit drill observation timestamp text by reported precision.