Description
Compare exhibit seals and supplied custody-transfer metadata.
Case and statute records use identifiers, stages, time coordinates and supplied procedural assumptions. A literal comparison, count or charge calculation can help reconcile records, while actual rights, deadlines, evidence and duties depend on the applicable jurisdiction and authoritative documents.
Compare exhibit seals and supplied custody-transfer metadata.
When to use this tool
Use Exhibit Seal Custody Token when checking the stated legal-record, timing or fee convention.
How to use the tool and how it works
- Enter recordedSeal, expectedSeal, sender, receiver, handedOver. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read sealMatches, attributedTransfer. Inspect sealMatches, attributedTransfer before interpreting the associated values.
Compare exhibit seals and supplied custody-transfer metadata. sealMatches uses literal equality; attributedTransfer requires handedOver and nonempty sender and receiver labels.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| recordedSeal | Recorded Seal | Required. Text; maximum UTF-16 length 8192. |
| expectedSeal | Expected Seal | Required. Text; maximum UTF-16 length 8192. |
| sender | Sender | Required. Text; maximum UTF-16 length 8192. |
| receiver | Receiver | Required. Text; maximum UTF-16 length 8192. |
| handedOver | Handed Over | Required. Boolean. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| sealMatches | Seal Matches | Required. Boolean. |
| attributedTransfer | handedOver and nonempty sender/receiver labels; no identity verification. | Required. Boolean. |
{
"input": {
"recordedSeal": "S1",
"expectedSeal": "S1",
"sender": "A",
"receiver": "B",
"handedOver": true
},
"output": {
"sealMatches": true,
"attributedTransfer": true
}
}Limitations and assumptions
- Matching labels and assertions do not verify physical integrity, identity, authenticity or an admissible chain of custody.
- 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
Consult the actual case records, governing rules and qualified legal advice for legal conclusions; use an appropriate calendar and complete document workflow for real deadlines.
References
Similar or alternative tools
- Public Case Stage Transition Gap
Audit recorded case stages against a supplied unique order.
- Public Case Suffix Sequence Gap
Find missing and duplicate public-case suffix numbers.