These counts describe the finite matrix, not a production rate. Each card opens one exact example below.
Each square is one vector. Columns are policy states; rows are approval-hook behaviors. In each row, squares follow the four claim behaviors, with a returning callback then a throwing callback. Select one to inspect its path.
Colors are supported by text labels and each square has an accessible name. Horizontal scrolling reveals all four policies on narrow screens.
Proposal SHA-256:
The Node runner calls the reference dispatchAction for all 192 local fixtures. A separate project-authored Python oracle checks each row, including receipt, digest, claim consumption, callback target, and marker write. CI rejects four deliberately falsified reports.
Reproduce with node pilots/action-boundary/dispatch-matrix.mjs --check and python3 pilots/action-boundary/verify_dispatch_matrix.py docs/action-dispatch-matrix.json. Read the method and limits ↗
Scope: Finite project-authored callbacks, no human approval, provider call, arbitrary interleavings, real delivery, outside witness, or formal proof of production safety. A browser view of the report does not independently verify its provenance. Never silently retry an unknown result.
We weakened seven guards in the actual reference source, one at a time. The 192-case matrix detected six. The seventh accepted a rule for the wrong resource, yet all 192 rows looked unchanged.
Inspect the source-bound results ↗A proposal for outside@example.test meets a rule for team@example.test. The real boundary blocks before the host callback; the weakened version enters it once. The new probe keeps that distinction under test.
The Node runner calls the reference dispatchAction for all 192 local fixtures. A separate project-authored Python oracle checks each row, including receipt, digest, claim consumption, callback target, and marker write. CI rejects four deliberately falsified reports.
Reproduce with node pilots/action-boundary/dispatch-matrix.mjs --check, python3 pilots/action-boundary/verify_dispatch_matrix.py docs/action-dispatch-matrix.json, and node pilots/action-boundary/dispatch-mutants.mjs --check. Read the method and limits ↗
Scope: Finite project-authored callbacks and selected mutations, no human approval, provider call, arbitrary interleavings, real delivery, outside witness, or formal proof of production safety. A browser view of the report does not independently verify its provenance. Never silently retry an unknown result.