A Regulayer Receipt is a signed, tamper-evident record of what AI tools were used in a piece of work, for what, and what a named person personally checked. It is sealed at the moment of creation on the signer's own machine, and anyone can verify it free, forever, without an account, without contacting us, and without ever seeing the work itself.
Field descriptions below are from the record format itself; see what a record contains for the canonical list.
The anatomy of a receipt
A receipt is a small JSON document. The work is never inside it. What is inside:
| Field | What it carries |
|---|---|
| record_type | The word ai_work_receipt, on the face of the record. The verifier refuses to read one kind of record as another: a file seal can never pass as a certification of review. |
| fingerprints | Two mathematical summaries of the exact file delivered, computed two different ways (SHA-256 and SHA3-256). Not the file; you cannot read the document back out of them. Two, so a weakness discovered in either method later does not take the record with it. |
| declared use | What AI you used and for what, in your own words. Your statement, not our finding. |
| role | The part the tool played, one of six fixed choices. There is no “other,” so the declaration stays worth reading. |
| reviewer | Your name, as you typed it. Nobody outside verified it, and the record says so. |
| attestation | Your review statement, verbatim, exactly as you wrote it. This is the part you sign. |
| checks | Which of the seven named checks you carried out, reported, never scored, stored in a fixed sorted order so the canonical form of the record is stable on any machine. |
| evidence level | The word “declared.” Nothing anyone sends can raise it. The record announces its own weight. |
| time basis | Where the time came from: your device clock, marked self-asserted, or an independent time authority's countersignature (RFC 3161), marked witnessed. The verifier says which, in plain words. |
| tier | The assurance level the record was sealed under, stated on its face. Where a Presence check (a passkey or fingerprint at the moment of sealing) was used, the record says so. |
| ledger chain | A sequence number and the fingerprint of your previous record. Each receipt links to the one before it on your machine, so a missing or altered entry shows. |
| signature | An Ed25519 signature over the canonical record, with the public key inside the file. Anyone can check it without contacting us. |
// Illustrative specimen with sample data. Not a customer record.
{
"receipt": {
"record_type": "ai_work_receipt",
"file_sha256": "9f2c…specimen…41ab",
"file_sha3_256": "77d0…specimen…c93e",
"declared_use": "Research summary and a first draft of section II; every citation pulled and read",
"role": "drafting_assistant",
"reviewer": "A. Sample",
"attestation": "I personally read every case cited in this filing and checked each quotation against the source.",
"checks": ["citations_pulled_and_read", "final_text_read_in_full", "quotations_checked"],
"evidence_level": "declared",
"time_basis": "self_asserted",
"timestamp_utc": "2026-08-04T15:11:02Z",
"seq": 42,
"prev_receipt_sha256": "1be8…specimen…05f7",
"watermark": "Specimen published on this page. Sample data, not a customer record."
},
"signing_public_key_b64": "…specimen…",
"record_signature_b64": "…specimen…",
"alg": "Ed25519"
}Field names shortened for readability; the live record carries the full format. Make a real one in your browser at the demos, then try to alter it and watch the seal break.
What it is not
Three categories get confused with a receipt. The distinctions matter, because each answers a different question.
Not an AI detector
A detector examines finished text after the fact and returns a statistical guess about its origin, and it needs the text itself to do it. A receipt is made at the moment of work by the person who did it; it records what they declared and checked, and it never contains the work. One is a judgment about a document. The other is a record made by a person. The full comparison
Not only a hash seal
A hash sealer, including our own free Sealer, establishes integrity: this exact file existed, unchanged, at this time. It says nothing about what any person did. The receipt carries the seal and adds the attestation: the declared use, the named reviewer, the checks, the signature over all of it.
Not a typed declaration
A typed declaration is your word in a Word document, and in most courts today it is legally sufficient. But it is undated beyond the filing, unverifiable by the person reading it, and editable after the fact without a trace. The receipt is the same statement made into a record: signed, sealed at the time, and checkable by anyone you send it to.
The honest limits
Tamper-evident, not tamper-proof. Nothing is unalterable. The guarantee is narrower and stronger: any change after sealing breaks the signature, and the break shows on verification.
It records evidence. It does not certify compliance. The receipt certifies nothing by itself. It carries your certification, sealed. What weight a court gives it is the court's decision; the format is built to support self-authentication under FRE 902(13) and 902(14), and the evidence-law analysis is on a page of its own.
Attested, not proved. The signature makes your declaration permanent and attributable. It does not make it true. A receipt says a named person declared this review, at this time, and the record has not changed since. That is what it shows, and it is all it shows.
Self-asserted time by default. A receipt sealed on your own clock asserts its own time and says so. Witnessed mode, where an independent time authority countersigns, carries third-party time and says that instead. The verifier states which one it is looking at, in plain words.
Questions people ask
Does the receipt contain my filing or my prompts?
No. The record carries fingerprints of the file, not the file, and nothing of the prompts. That is what lets you send it to a judge, a client, or an auditor without handing over privileged work. The desktop app works offline; nothing leaves the machine.
What does verification cost, and what does it need?
Nothing, forever. The verifier runs free in any browser with no account, checks the Ed25519 signature over the canonical record and the file fingerprints, and contacts no server. It needs only the receipt file, never the underlying work.
Can a receipt be backdated or edited after sealing?
Editing any field after sealing breaks the signature, and verification reports the record as tampered. A private seal asserts its own time; if the time itself may be questioned, witnessed mode carries an independent authority's countersignature, and the record says which it carries.
Who is it for?
Anyone who delivers AI-assisted work under a disclosure clause or a court order, and wants the answer to “what did you use and what did you check” to already exist. The first vertical is solo and small-firm litigators answering AI standing orders.
See one break, then make one.
The live demos sign a real record in your browser and let you alter it: change one character and the verification flips to tampered. Then generate your own. Seven days free, then $349 a month: unlimited receipts, the Sealer, HumanMark creation facts, and the free verifier. Cancel anytime; receipts stay valid forever.
Product description as of 4 August 2026. The seal is tamper-evident, not tamper-proof. A receipt attests what the signer declared; it does not certify the work, and admissibility is decided by the court.