supplier-payments
ActivePays approved supplier invoices from the finance mailbox.
Northwind Robotics (demonstration)
Agents
support-triage
ActiveAnswers tickets and escalates the ones it should not answer.
release-bot
ContainedFrozen after a burst of repository merges outside its window.
Encrypted evidence
Action ledger
| Agent | Action | Effect | Risk | Why | Subject digest |
|---|---|---|---|---|---|
| support-triage | email.send | ALLOW | 12 | POLICY_ALLOW, RISK_BELOW_THRESHOLD | sha256-jcs:kCJ…JHUpFvCw |
| supplier-payments | payment.transfer | REQUIRE_APPROVAL | 71 | AMOUNT_ABOVE_AUTONOMOUS_LIMIT | sha256-jcs:0m9…bbF3jkYw |
| supplier-payments | payment.transfer | DENY | 88 | RECIPIENT_NOT_ON_ALLOWLIST | sha256-jcs:9dR…SvVVLZ4o |
| release-bot | repository.merge | REQUIRE_APPROVAL | 64 | AGENT_CONTAINED, AUTHORIZATION_FACTS_STALE | sha256-jcs:tGz…NjXkA3Zs |
The last row is the one worth reading: an execution refused because the agent was contained and its authorization facts were stale. Nothing was sent, and the refusal is a record rather than an absence.
Human oversight
The vote
A £48,500 supplier transfer went above the autonomous limit, so the decision was REQUIRE_APPROVAL and the transfer waited. One named approver voted, and the vote carries the reason they gave and the digest of the exact effect they were shown.
- Approver role
- FINANCE_APPROVER
- Decision
- APPROVE
- Decided at
- 2026-07-11T02:00:02.000Z
- Subject digest
sha256-jcs:0m9…bbF3jkYw
“Invoice INV-20416 matches the purchase order and the supplier is on file.”
That digest is the same one on the action above (sha256-jcs:0m9…bbF3jkYw). The approver agreed to that exact transfer, not to a category of transfer.
Tamper-evident ledger
Check it yourself
Export the chain and verify it somewhere that has never heard of this page. The bundle below is the frozen vector the control plane and the forensics CLI are both tested against, and the verifier recomputes every hash in your own browser.
Head 08MEyKYJigH01Z…ddHO7j_8. The verifier has no idea this page exists; it recomputes the file it is given and nothing else.
Boundaries
What this demonstration leaves out
- Every mutating control is absent rather than disabled: nothing here writes, so there is nothing to fail.
- Billing, members and integrations are omitted — they are about an account, and this demonstration has none.
- The chain below is a four-event excerpt, not a tenant's history. It is the frozen vector the control plane and the forensics CLI are both tested against.