Regulayer Enterprise licensing
Main site The engine By problem What is licensed Deployment Assurance AI audit trail Human authorship and review The record format What it proves Security review Begin with the problem

The record format

What a record contains, and how anyone checks it.

A Regulayer record carries the fact of a decision, a cryptographic fingerprint of the material, and the identity of the person responsible. Never the material. Every record is signed, chained to the record before it, and verifiable by anyone holding the file, with public mathematics, permanently, with no account and no call to us.

The record

The fact of the decision

What was decided, at what moment, in which surface. A review attested, a hold released, a seal applied, a halt taken.

The fingerprint of the material

SHA-256 and SHA3-256 digests of the material the decision is about, computed two different ways where the material lives, so a weakness discovered in either method later does not take the record with it. The record proves these exact bytes were the ones decided about. The bytes themselves never move.

The identity of the person

Who is responsible for the decision, at the assurance level stated on the face of the record: declared by the signer, or bound by Presence, where a named person passed a fingerprint or passkey check on their own device at the moment of sealing.

The format version

An integer field named format sits inside the signed bytes; the current value is 1. A record missing the field verifies as version 0, forever. Newer versions are never rejected by older verifiers.

The fields, exactly as they ship

A record is a single JSON object. The envelope carries four top-level keys: receipt, signing_public_key_b64, record_signature_b64, and alg, which is the string Ed25519. The signature covers the canonical bytes of the receipt object. Inside the receipt object, the fields are these.

record_type

The kind of record, on the face of the record, so one kind can never pass as another.

format

The format version, an integer, currently 1, inside the signed bytes.

receipt_id

The identifier of this record.

file_sha256

SHA-256 digest of the exact bytes the record is about.

file_sha3_256

SHA3-256 digest of the same bytes, computed a second way.

size_bytes

The size of the material, in bytes.

declared_ai_use

What AI was used and for what, in the signer's own words.

ai_role

The part the tool played, from a fixed set of choices.

reviewer_name

The name of the person responsible, as they typed it.

review_attestation

The review statement, verbatim. This is the part the person signs.

review_checks

Which named checks the person carried out, stored in a fixed sorted order so the canonical form is stable on any machine.

evidence_level

The assurance level of the identity claim, stated on the face of the record.

timestamp_utc

The moment of sealing, in UTC.

time_basis

Where the time came from: self-asserted from the device clock, or witnessed by an independent authority under RFC 3161.

tier

The product tier the record was sealed under.

seq

The sequence number of this record in the signer's chain.

prev_receipt_sha256

The fingerprint of the previous record in the chain, so a missing or altered entry shows.

filename_sha256

A digest of the filename, so the name is bound without being disclosed.

// Illustrative values, shortened for the page. A real record carries full digests and signatures.
{
  "receipt": {
    "record_type": "ai_work_receipt",
    "format": 1,
    "receipt_id": "r-000042",
    "file_sha256": "9f2c...41ab",
    "file_sha3_256": "77d0...c93e",
    "size_bytes": 48213,
    "declared_ai_use": "Research summary and a first draft of section II",
    "ai_role": "drafting_assistant",
    "reviewer_name": "A. Sample",
    "review_attestation": "I personally read every case cited and checked each quotation against the source.",
    "review_checks": ["citations_pulled_and_read", "final_text_read_in_full", "quotations_checked"],
    "evidence_level": "declared",
    "timestamp_utc": "2026-08-04T15:11:02Z",
    "time_basis": "self_asserted",
    "tier": "standard",
    "seq": 42,
    "prev_receipt_sha256": "1be8...05f7",
    "filename_sha256": "6a91...d2c4"
  },
  "signing_public_key_b64": "...",
  "record_signature_b64": "...",
  "alg": "Ed25519"
}

How it is signed and chained

Canonical form

Records are serialised in a fixed canonical form, so the same record always produces the same bytes. Verification recomputes those bytes exactly.

Signature

Ed25519, to RFC 8032, over the canonical bytes. The signing key is generated on the machine where the record is made, on first run, and never leaves it.

The chain

Each record carries the fingerprint of the record before it. Remove one, change one, reorder one, and the seam shows. A deletion is visible as a gap, not as an absence nobody noticed.

Two classes of time, stated on the face

Self-asserted time, with no outbound call of any kind. Or witnessed time, where a single digest is timestamped by an independent authority under RFC 3161. The verifier shows which class a record carries. Neither class ever sends the material.

Post-quantum readiness

Hybrid classical and lattice signatures, so records issued today survive the transition and nothing already issued breaks.

How anyone verifies it

Recompute the canonical bytes. Check the signature against the embedded public key. Walk the chain. Where witnessed time is present, check the timestamp token against the same digest. Every step is published mathematics: RFC 8032, SHA-256, RFC 3161. No account, no licence, no service operated by us. Verification is a capability of the record itself, and it is free, permanently.

This page specifies the public profile of the format. Deployment profiles extend it under licence, and the detail of specific surfaces travels under non-disclosure.

Check any record at the verifier. Free, with no account.

Or take the specimen with you: specimen-bundle.zip, a real sealed record made by the actual Sealer, verifiable offline. SHA-256 3914a56559306e844a8249b90c28f056692af9288eb06aaf25d2895de00c9262

The estate

Part of the filed estate: eighteen patent filings and a PCT. Patent pending across the estate.

Licensing begins with the problem, not the product.

Describe the system, what it decides, and what it would cost you to be unable to prove it. A written scope follows before any call.

Ways to begin:

A scoped pilot, inside your estate, on your machines. An architecture briefing, for your security function, one hour. The diligence pack: the record format and the estate, in writing. The problem itself, in your own words.

hello@regulayer.com