Use case 1 · Case-management automation
An AI agent triages applications for a fictional council's hardship grant. It can prepare everything. It cannot make the decision.
How to run the 2-minute demo
- Pick Case 1 and tap Run. Watch intake, triage, then the block.
- At the block, try signing as Tom Reid or the service account. Denied.
- Sign as Sarah Okafor. Approve, or Decline to watch the agent try workarounds.
- Open Audit (try the tamper test) and Assurance.
- Run Case 2: every rule followed, poor outcome for the citizen.
Pipeline and control gates
Agent activity
newest first- Nothing yet. Tap Run.
Red-team suite
Repeatable attack tests against the same policy engine the workflow uses. Each test is an agent (or a person) trying something it shouldn't. Results are written to the audit log as evidence.
- Not run yet.
Policy set enforced (fictional, v1.0)
Documentation layer
Every decision, action, outcome and workflow step goes into an append-only log. Each entry carries the hash of the one before it, so editing any record breaks the chain from that point on.
Assurance layer
For management: what the controls did in this session, what's been flagged for policy owners, and the risks the controls can't remove.
Policy-level concerns
Cases where the system did everything by the book and the outcome was still poor for the citizen. These go to the policy owner, not the agent or the caseworker.
Residual risk register
Score = likelihood × impact (1–5 each). Acknowledgements are written to the audit log.
Where assurance stops
Controls can show that the system did only what policy allowed and that a named official made each consequential decision. They can't show that:
- the policy is fair in every circumstance (R1)
- the official genuinely engaged with the evidence (R2)
- the facts extracted upstream were right (R3)
- the coded rule matches the written policy (R4)
Those risks have named owners. That's what management signs off.
Governed intake triage · 12 weeks · shadow mode
We run intake, document classification, completeness checks and routing for one case type in one team, alongside your existing process. No live decisions: agents prepare, your officials decide, and we measure the difference.
Plan
Acceptance criteria
Commercials
Fixed price, milestone payments, with the option to stop at any milestone. You keep the evidence pack, the policy definitions and the test suite.
What this demo does and doesn't show
Shows: the control logic in a working page: blocking, delegated approval, bound tokens, rejection locks, cumulative limits, circuit breaker, a tamper-evident log and outcome monitoring.
Doesn't show: integration with live departmental systems, security accreditation, or production performance. Proving those is what a pilot is for.
Synthetic data. The council, people, policy and figures are fictional. This is not a deployed government system.