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

Drift · a Regulayer surface

The model was correct this morning. It is not correct now.

Drift measures behavioural change in a running system, in context and per person, and puts it in front of a person while there is still time to decide. The measurement, the hold and the decision are recorded as they happen, including a decision to accept the drift.

The situation

People name the loudest symptom: hallucination. Drift is the disease. It is the slow slide away from the rules a system was verified against, sometimes talked into it over a long session, sometimes with no outside help at all.

Nothing breaks. Nothing alerts. The behaviour moves, and the first to notice is a customer, a regulator or a court. Application logs are written by the system under question, so the one record you would need to trust is the one record an adversarial reader will not accept.

The people you answer to are already asking for this record. Forty-two attorneys general jointly demanded records of model behaviour over time. Behaviour over time is drift. Carriers now see AI claims and cannot see conduct. And post-market monitoring duties, including Article 72 of the EU AI Act, describe exactly the evidence this surface produces.

What it does

Measured in the path

Behaviour is assessed as output is produced, not sampled afterwards. Output that crosses the line is held in flight and shown to a person. It never reaches the reader unreviewed: not deleted, not rewritten in secret, held.

Measured per person

A behavioural pattern belonging to one operator is visible as theirs rather than averaged into the system. Conduct becomes attributable to the person whose conduct it is.

The person decides, and the decision is recorded

Release, remove, or accept the drift knowingly. Each outcome is sealed at the moment it is made, so a later question has an answer that already exists.

What it records

Every measurement, every hold, every decision, signed and chained to the record before it. A deletion shows as a gap. Anyone holding the records can verify them with public mathematics, free and permanently, with no account and no call to us. This is the audit trail that record-keeping duties, including Article 12 of the EU AI Act, describe. The evidence is a byproduct of running the system, not a report assembled afterwards.

Where it belongs

Customer-facing assistants

Behaviour that shipped unreviewed becomes a public event. Held in flight, it becomes a decision instead.

Clinical, underwriting and credit support

A drifted model in a regulated decision is an exam finding. The record of who saw it and decided is the answer.

Agents with write access

The system can act. Drift tells you whether it still acts within the rules it was given.

Any system under monitoring duties

Post-market monitoring and incident reporting obligations assume you can show behaviour over time. This is that record.

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