We use a few strictly-necessary cookies, no marketing trackers, and cookieless analytics. Read our cookie policy, or pick a preference.
A conformity assessment certifies a system at a point in time. Then it changes: the model updates, the data drifts, the environment moves, and the system in production is no longer the one that was certified. The Integrity Engine treats that gap as the central governance problem of deployed AI, and closes it, as a tamper-evident chain of custody.
Assurance today is mostly assertion: a vendor says the system is compliant and you take it on trust. The Integrity Engine replaces the assertion with something an outside party can verify. At certification it binds the system's full software-stack manifest into a signed certificate, then watches continuously for the moment the running system diverges from the certified one, and it can act when it does.
The Engine binds the system's full software-stack manifest into a signed certificate that carries a six-state lifecycle, where each state has direct execution consequences. The certificate is the anchor everything else is measured against.
It monitors continuously, detecting corpus drift, undocumented model or code change, and environment change, without adding latency to the system it watches. The gap between certified and running is measured in real time, not at the next audit.
A deviation activates an execution gate and a graceful shutdown that preserves audit data and in-flight work, then opens a re-certification workflow that governs the return to service. The control is real, not advisory.
This is where post-market monitoring lives. The Engine operationalises the Article 72 monitoring plan, and when a deviation crosses the Article 73 threshold it carries the cryptographic evidence straight into serious-incident reporting, with the reporting clock already running.
Every certified system sits in one of six states, and the state it is in decides whether, and how, it is allowed to run.
Illustrative lifecycle states · the state model and its execution consequences are covered by patent GB2604505.4
Assurance rests on the Cryptographic Spine, the tamper-evident chain of custody beneath the platform. Its patented mechanisms make the assurance something a regulator, an auditor, or an end user can check for themselves, rather than a claim they have to accept.
The Intelligence Centre defines what is true; the Integrity Engine keeps it true in production; engagement turns it into work, and capability proves the people can run it.