What ZTR does in one sentence: When you review an AI-generated document before filing or use, ZTR timestamps that review — creating a contemporaneous record proving the human gate was passed.
Courts and regulators are asking a new question: not "did you use AI?" but "can you demonstrate that verification occurred — and when?"
Recent cases show the pattern clearly. In Miller v. Regions Bank (N.D. Alabama, 2026), a US federal court applied a two-track doctrine: the AI error received a public reprimand, but the destruction of the ChatGPT account received adverse inference, contempt, and a six-month suspension. The absence of a contemporaneous record was treated as evidence of fault — more serious than the error itself.
No existing tool produces that proof in advance. ZTR does.
You use Claude to draft or research a legal document. You read it, check the citations, apply your professional judgment.
Before filing or sending, you ask Claude to verify the document with ZTR. Claude calls the verify_document tool.
ZTR hashes the document (SHA-256), records the timestamp, and creates a verification receipt. The document text is immediately discarded — only the 64-character hash is stored.
You receive a receipt like ZTR-20260720143022-a7f3c891. This is your proof. If ever asked "did you verify this before filing?" — you have a dated, immutable record.
What ZTR does NOT do: ZTR does not check whether the document is correct, whether citations exist, or whether AI was used. It certifies only that a verification step occurred at a specific time. The professional judgment remains entirely yours.
You: I've reviewed this brief and I'm ready to file.
Please verify it with ZTR before I do.
Claude: [calls verify_document]
Verification recorded.
Receipt: ZTR-20260720143022-a7f3c891
Hash: 6576176c9194ee14...
Time: 2026-07-20T14:30:22Z
TSA: VERIFIED (eIDAS)
Document was not stored.You: Can you look up receipt ZTR-20260720143022-a7f3c891?
Claude: [calls check_receipt]
Receipt found.
Document hash: 6576176c9194ee14...
Verified: 2026-07-20T14:30:22Z
Context: legal_filing
TSA: VERIFIED (eIDAS)You: Show me all documents I verified this week.
Claude: [calls list_receipts with date_from filter]
7 receipts found between 2026-07-14 and 2026-07-20.| Tool | What it does | When to use |
|---|---|---|
verify_document | Hash + timestamp + receipt | Before filing any AI-assisted document |
check_receipt | Retrieve receipt by ID | Audit trail lookup, due diligence |
list_receipts | List your receipts | Periodic compliance review |
Documents are hashed using SHA-256 (Python hashlib). The hash is a one-way mathematical fingerprint — it cannot be reversed to recover the document. Only the 64-character hexadecimal hash is stored.
Standard receipts include a server timestamp (ISO 8601 UTC). eIDAS-qualified timestamps are provided via Aruba PEC S.p.A., a Qualified Trust Service Provider under eIDAS Regulation (EU) 910/2014. eIDAS timestamps are RFC 3161 compliant and legally presumed accurate across the EU and UK.
Receipts are stored in a secure database on EU servers. The document text is never written to disk, never logged, and never transmitted beyond the hash. See the Privacy Policy for full details.
Each receipt is sealed with an HMAC-SHA256 integrity check to detect tampering.
| Context | Use case |
|---|---|
legal_filing | Court submissions, briefs, motions |
contract_review | Contract drafting and review |
legal_research | Research memos, opinion letters |
client_advice | Client-facing documents |
regulatory_submission | Regulatory filings, compliance documents |
internal_memo | Internal documents |
other | Any other document type |
ZTR is built on the Zorthex™ L₂ research framework — an empirical methodology for measuring the interval between a governing norm and the first documented failure of its application. The framework has been validated across six verified cases in the US and UK legal systems.
ZTR is powered by Claude (Anthropic). Trademark: UIBM N.302026000090628.
For questions, issues, or feedback: zorthex.official@gmail.com