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

Trust and scope

Read this like a threat model, not marketing.

A Regulayer deployment exists because the company does not overstate. This page is the exact scope of the evidence: what a record proves, and what no record can prove.

What a record proves

Integrity

The record reads exactly as it was signed. Any edit to any field, made at any later time, breaks the signature, and the verifier says so plainly.

Chain completeness

Each record carries the fingerprint of the one before it. A removed, changed or reordered record shows as a visible seam. The span of records you hold is the span that was written, or the gap shows.

Time, in its stated class

A witnessed record carries a timestamp from an independent authority under RFC 3161, bound to the record's digest. A self-asserted record says so on its face. The verifier shows which class you are holding; a self-asserted time never wears a witnessed badge.

Key custody at sealing

A valid signature proves the signer held the corresponding private key at sealing time, on the machine where the record was made.

A person, at the Presence band

Where a record carries Presence, a named, enrolled person passed a fingerprint or passkey check on their own device at the moment of sealing, and the seal binds that person, that material and that moment.

Material identity, without the material

The digest proves these exact bytes are the bytes the decision was about. It does so without the bytes ever leaving the estate.

What it does not prove

That an attestation is true

The record proves what was attested, sealed and witnessed, and by whom. It cannot make a false attestation true. What it does is make the attestation attributable, dated and unchangeable, which is what gives a false one consequences.

What an AI system did inside itself

No external record can see inside a model. The record carries the decision about the work and the person responsible for it, not the model's internals.

Compliance

A record evidences process. It does not certify compliance with any law, rule or standing order, and nothing issued by us can.

Admissibility

Admissibility is decided by a court, never by a vendor. The format is built to support self-authentication under FRE 902(13) and 902(14); the decision belongs to the bench.

Identity without Presence

Below the Presence band, a record shows key custody, not personhood. The assurance level is stated on the face of every record precisely so that a declaration never reads as an observation.

That an unchecked decision was safe

A record of a decision does not redeem the decision. It makes the decision provable, which is the part that was missing.

Why the limits are the pitch

Every record states its own scope, and this page states the scope of every record. A company whose product is evidence integrity survives on one rule: it does not overstate. If you ever find this site doing otherwise, the record format gives you the means to prove that too.

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