Platform
The Integrity Engine
A conformity assessment certifies a system on one day. Then the system changes. The Integrity Engine closes the gap.
In development · patent pending
The problem
Assurance Is Mostly a Vendor's Word
Assurance today is mostly a vendor's word that a system complies. The Integrity Engine replaces that with evidence anyone outside can check. It records exactly what was certified, watches for the moment the running system differs, and can act when it does.
A worked case
One System, Certified Then Changed
The CV-screening system from the homepage, through the Integrity Engine.
- 01CertificationThe CV-screening system is certified, and the Engine seals its build.Head of AI governanceIn a later release
- 02A model updateEngineering ships a new model version that was never documented.ML engineerIn a later release
- 03The gap opensThe Engine detects the change and moves the certificate to Drifting.The EngineIn a later release
- 04The gateThe system is gated, its audit trail kept, and re-certification opened.Compliance leadIn a later release
- 05The reportPast the Article 73 threshold, the evidence goes into incident reporting.Data protection officerIn a later release
What it does
Four Modules, One Certificate
The Certified Build and Its Six States
At certification, the Engine seals a record of the system's full software stack into a signed certificate. The certificate moves through six states, and each state decides what the system may do.
- Signed record of the stack
- Six states
- Consequences for each state
Continuous Change Detection
Watches continuously for changes in the regulations the system relies on, undocumented changes to models or code, and changes to its environment, without slowing the system down. The gap between certified and running is measured as it opens, before the next audit.
- Regulation change
- Model and code change
- Environment change
- No added delay
Gating and Safe Shutdown
When a deviation is found, the Engine can stop the system safely, keeping its audit trail and work in progress, and open re-certification before it returns to service. The control acts on the system itself.
- Execution gate
- Safe shutdown
- Audit trail kept
- Re-certification
Post-Market Monitoring
This is where post-market monitoring lives. The Engine runs the Article 72 monitoring plan. When a deviation crosses the Article 73 threshold, it carries the signed evidence into serious-incident reporting, with the reporting deadline already running.
- Article 72 plan
- Article 73 reporting
- Market-surveillance notice
- Near-miss trends
Six States, Each With Consequences
- 01
Certified
- 02
Monitored
- 03
Drifting
- 04
Gated
- 05
Halted
- 06
Re-certifying
Illustrative states · patent pending
Status
What Is Live, and What Comes Next
The Integrity Engine lands in phases. Each release adds to its core.
- In a later release
- The Certified Build and Its Six States
- Continuous Change Detection
- Gating and Safe Shutdown
- Post-Market Monitoring
Assurance Anyone Can Check
Underneath sits a tamper-evident chain of custody. Its patent-pending mechanisms let a regulator, an auditor or an end user check the assurance themselves, instead of taking it on trust.
Your next step