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 Witness · a Regulayer surface

Something happened. Nobody can prove what.

The Witness is sealed decision memory. Every governed moment is recorded as it happens, chained to the moment before it, and verifiable by anyone holding the record. It records the conduct. It never reads the content.

One refusal

The Witness is built on one refusal: it will not read your words. What it seals is the shape of the moment. That AI ran, in which tool, at what time, and what a person chose to do about it.

Documents, client secrets, patient charts, deal terms: none of it is ever stored or sent. That is why the record can be shown to an outsider without betraying an insider, which is precisely the property application logs do not have.

What it does

Chained, so a deletion shows

Every entry is sealed to the one before it. Remove one, change one, reorder one, and the seam shows, to anyone, with the free verifier. A gap is visible as a gap, not as an absence nobody noticed.

The human moment, sealed

Plenty of tools log AI. The Witness records something rarer: the moment a person looked at what the AI did and chose, keep or remove. That judgement, the who and the when of it, becomes its own signed record.

At the moment, beside the work

The very next message builds on this one. A conversation cannot be un-had, and a record reviewed later is archaeology. The Witness seals it when it happens, because later is too late.

Asked in plain English

No query language, no export project. Ask the memory a question and the answer comes back at true scale, across thousands of sealed moments, with proof that the answer is complete.

The Verdict

The decision itself, recorded as it is made, not reconstructed from an outcome afterwards. Most systems can show you a result. The Verdict shows the decision that produced it: what was decided, under which authority, at what moment, by whom or by what. An outcome is a claim. A verdict is a record.

The compliance frame

This is the audit trail that record-keeping duties describe: Article 12 of the EU AI Act on the automatic recording of events, the logging expectations inside ISO/IEC 42001, and the supervision record your examiners ask for first. The evidence exists because the system ran, not because someone compiled a report for the examination.

Deployment

It runs on your machines, and nothing of the work leaves the building.

The kernel binds the loopback interface and refuses any client that is not local. The signing key is generated on your own machine on first run and never leaves it. In the default mode there is no outbound call of any kind. Where independent time is required, a single cryptographic digest goes to a public timestamp authority, never the file and never its contents. The source ships readable, so your own security function can satisfy itself line by line.

Every answer your security function will ask for, on one page you can forward

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