SentraMind

Case

A time-boxed exception, from approval to expiry

A synthetic case: approved at 09:30, still blocked at 09:45, in force from 10:00, and gone by 18:05 with no publish, while a second group stays on the rule throughout.

Synthetic run legal-review is blocked (hard-block) at 09:45, logged only (log-only) under the exception at 14:00, and blocked (hard-block) again at 18:05. finance-ops is blocked (hard-block) all three times.
legal-review
09:45Z hard-block 14:00Z log-only 18:05Z hard-block
finance-ops
09:45Z hard-block 14:00Z hard-block 18:05Z hard-block
21 fields, including the rule, the exception and the snapshot hashes

Rule

name
National IDs to unsanctioned AI
action
hard-block

Exception

group
legal-review
reason
Time-boxed legal review of one synthetic matter
action
log-only
evidenceCapture
none
approvedAt
2026-11-03T09:30:00.000Z
expiresAt
2026-11-03T18:00:00.000Z

Policy snapshots

version 7
compiledAt=2026-11-03T09:20:00.000Z
snapshotHash
4a89d11c523201cc590d1963a750ddac10570f220a488a1f17f829d8d26bc763
exceptionIds
[]
version 8
compiledAt=2026-11-03T10:00:00.000Z
snapshotHash
e6ca6b994c0e415db5d50372aa43e1d357d937d9dcd85763db812f6d633a0d6b
exceptionIds
["00000000-0000-4000-8000-000000002101"]
activation
at=2026-11-03T10:00:00.000Z snapshotVersion=8

Decisions

09:45Z legal-review
hard-block winningClause=rule evidenceCapture=full snapshotVersion=7 exceptionInStoredSnapshot=false exceptionApplied=false
09:45Z finance-ops
hard-block winningClause=rule evidenceCapture=full snapshotVersion=7 exceptionInStoredSnapshot=false exceptionApplied=false
14:00Z legal-review
log-only winningClause=exception evidenceCapture=none snapshotVersion=8 exceptionInStoredSnapshot=true exceptionApplied=true
14:00Z finance-ops
hard-block winningClause=rule evidenceCapture=full snapshotVersion=8 exceptionInStoredSnapshot=true exceptionApplied=false
18:05Z legal-review
hard-block winningClause=rule evidenceCapture=full snapshotVersion=8 exceptionInStoredSnapshot=true exceptionApplied=false
18:05Z finance-ops
hard-block winningClause=rule evidenceCapture=full snapshotVersion=8 exceptionInStoredSnapshot=true exceptionApplied=false

09:30: approved, and at 09:45 still blocked

On 3 November 2026 (all times UTC), the rule National IDs to unsanctioned AI has action hard-block. A security admin drafts an exception for one group, legal-review, with the reason “Time-boxed legal review of one synthetic matter”. It sets the action to log-only, evidence capture to none, and expiry to 18:00.

The admin cannot approve their own draft. A second account approves it at 09:30. In this POC those are two local accounts, so the check separates accounts rather than verified people.

At 09:45 a request from legal-review is blocked anyway. The person sending it sees an ordinary block, with nothing to say an exception has been approved. The admin now has an approved exception and a block at the same moment, and the system is working as designed. Enforcement reads a compiled snapshot, and the active one is version 7, compiled at 09:20 with no exceptions in it. Approval adds a row that a later compile will read. It changes nothing that enforcement reads.

10:00: the exception reaches enforcement

At 10:00 version 8 activates, compiled with the exception in it. Its snapshot hash begins e6ca6b99, where version 7’s began 4a89d11c, so an auditor can tell the two versions apart. A publish did this here, and a rollback compiled after the approval would do the same. Either one needs its own maker and checker, so this relaxation passes that check twice: once for the grant and once for the activation.

14:00: two groups on one version

At 14:00 two requests are evaluated against version 8. In each, the decision’s trace shows which clause set the action.

  • legal-review: action log-only, set by the exception clause, evidence capture none. The request goes through and nothing is captured.
  • finance-ops: action hard-block, set by the rule clause, evidence capture full. The request stops, under full capture.

The exception names one group, so the other falls through to the rule. It also changes two things, and a reviewer should weigh both. The action relaxes, and the capture stops. Inside the window, the decision shows that the exception applied, and no sealed content exists to review afterwards.

18:05: closed with no publish

The exception expired at 18:00. At 18:05 a request from legal-review gets hard-block, set by the rule clause, evidence capture full. The active version is still 8 and the exception is still stored in it. Nobody published anything. Before each evaluation the service drops any exception past expiresAt, by its own clock. The evaluator itself has no clock. On a live system the grant chains a policy.exception-granted event and the lapse chains none, so only the later decisions show that it ended.

That clock is also the limit. Whoever controls it controls when the exception ends, so expiry is no defence against that person.

Revoking early works differently. A revocation does not close the exception until a publish or rollback drafted after the revocation activates. The row disappears from /exceptions at once, while the exception goes on applying, up to its expiry.

What it came to, and its limits

The exception for legal-review was in force for eight hours, from 10:00 to 18:00, on an approval given half an hour before that. finance-ops got hard-block at all three times. Each of the run’s six rows, both groups at each of three times, answers three questions an auditor will ask: which version applied, which clause set the action, and what evidence capture applied.

This run called the expiry filter and the policy evaluator directly on built snapshots. The verdict service, the effective-policy viewer, the browser and the database did not run. The maker-checker, publish, revocation and event-chaining behaviour described here comes from the product’s code, and the approval and activation appear in this run only as times. The snapshots use the control plane’s compile computation with a fixed id, so their hashes reproduce, and a unit test holds that computation to the real one.

How to read this

How to read this
Read it asWhich meansDo not read it as
Approved at 09:30 Still hard-block at 09:45, on version 7 In force on approval
10:00 to 18:00 log-only and nothing sealed for legal-review; finance-ops stays on the rule A change for every group
18:05 hard-block again on version 8, with no publish The same path as revoking early

This case is synthetic. The people, inputs and destinations in it are invented for explanation, and the records are what the packages produced from them. None of it is a customer, a deployment or a measured incident.