Description
Preserve explicit document/edition/copy identity without determining a controlled-copy status.
Quality records separate measured results, reference values, acceptance rules, and supporting evidence. Arithmetic consistency and record coverage can be checked against supplied criteria without establishing traceability, approving a method, or deciding product conformity.
Preserve explicit document/edition/copy identity without determining a controlled-copy status.
When to use this tool
Use it for document copy edition token when the required inputs and conventions are already available.
How to use the tool and how it works
- Enter documentId, edition, copyId. Use the stated units and boundary conventions.
- Run the calculation. Correct any input error before interpreting a result.
- Read identityKey. Inspect any known, defined, inclusion, or boundary flags before interpreting numeric values.
Require nonempty documentId, edition, and copyId. Serialize their ordered three-element array using JSON.stringify to produce identityKey.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| documentId | Document Id | Required. Text; maximum UTF-16 length 8192. |
| edition | Edition | Required. Text; maximum UTF-16 length 8192. |
| copyId | Copy Id | Required. Text; maximum UTF-16 length 8192. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| identityKey | Identity Key | Required. Text; maximum UTF-16 length 8192. |
{
"input": {
"documentId": "SOP1",
"edition": "v2",
"copyId": "copy3"
},
"output": {
"identityKey": "[\"SOP1\",\"v2\",\"copy3\"]"
}
}Limitations and assumptions
- This is an unambiguous structural tuple representation rather than a hash or a globally unique identifier. It preserves case and supplied text without checking document or copy existence.
- The field tables describe structural bounds; the mechanics also state cross-field requirements. Malformed input shapes, disallowed keys, and invalid domains cause input errors. Results must remain finite and within the declared output contract. A successful false flag or zero placeholder is distinct from an error.
- Numeric arithmetic uses binary floating point. Exact comparisons have no hidden tolerance or decimal rounding; negative zero is exported as zero. Decimal-text integer operations retain the exactness specifically stated above.
Alternative or Complementary methods
For document copy edition token, check the source records and the supplied rule before comparing the result with another method. Use a separate evidence or method review when arithmetic consistency alone cannot establish the required conclusion.
References
Similar or alternative tools
- Document Control Copy Return Balance
Calculate document control copy return balance from explicit caller-supplied inputs.
- Document Training Coverage Share
Audit supplied document-training identifier coverage without certifying personnel qualification.