02 · The fields
Three fields most systems collapse into one.
Every consequential delegated action resolves into three separate states. Select a field to cycle through its possible values — each is a different fact, and each must be provable on its own.
A human can be present without being authorised.
Evidence created after scrutiny begins is reconstruction. Evidence created at the point of action is proof.
The timing principle — Veridom canonical language
04 · The boundary
Test one action boundary. This one is live.
Move the proposed amount across the autonomous limit. Bind or unbind the accountable officer. Watch the decision states resolve — then seal the record.
Below the limit, no authority is required. Above it, the action routes to a human — and the officer must be bound, not merely present.
The action does not execute. Authority was required and never bound — and that absence is now a provable fact, not a gap in the logs.
Interactive illustration of OMP decision states — not a production evidence record. In ACE, seals are tamper-evident and independently verifiable.
05 · The examination
Seven questions scrutiny will ask. The record answers each one.
Logs answer the first question. Audit, model risk, and insurers ask the other six.
06 · The architecture
How ACE stands at the boundary.
ACE sits between an AI agent and the action it is about to take, in regulated financial services workflows: credit, claims, payments, compliance.
Define
Boundary Studio
Autonomy thresholds, authority rules, and Watchtower gates — the boundary, made explicit and machine-enforceable.
Enforce
ACE Gateway
Every proposed action is evaluated before execution — then permitted or blocked. Nothing executes unexamined.
Prove
Evidence Console
Sealed decision-time records, retrievable and verifiable when scrutiny arrives — months or years later.
ACE is built on the Operating Model Protocol — Veridom's decision-enforcement and evidence architecture for consequential delegated actions.
Live IETF Internet-Drafts07 · The sprint
Prove one boundary in four weeks.
The ACE Boundary Proof Sprint is a bounded proof exercise — not an advisory engagement, not a platform rollout. One workflow, one autonomy boundary, one authority model, one verifiable evidence readout.
Week 1
Boundary Map
Your workflow's action boundary, made explicit.
Week 2
Watchtower Set
The gates your boundary needs, plus the scenario matrix.
Week 3
Evidence Pack
Live scenarios — permitted and blocked — sealed at decision time.
Week 4
Pilot Readiness Memo
What production enforcement would take.
Exploratory
£7,500–£10,000
Standard
£15,000–£25,000
Strategic design-partner pilot
£35,000–£75,000
One condition: you can name the boundary.
No named workflow means nothing to test. Name it, and ACE will stand at it.