Decisions · recorded engine output · invented data
What reaches the AI, and what does not.
An approval or a policy does not decide what leaves. The boundary does.
Most controls answer one question: was this request authorized? They do not answer the one that matters when the bytes are about to leave: does this authority still support these exact bytes, right now?
The gate reads the state its profile names for the destination, checks whether the request still has standing, and refuses before the call or records an ALLOW. Each decision is written to a hash-chained log, with the observation that produced it, before anything is sent. The records are unsigned today: an outside reader can recompute each observation hash and re-derive each decision, and cannot yet verify who wrote it.
Engine strix-document-release-gate 0.1.0 · build fd954ae34a4d9394 · log chain intact, 6 records, UNSIGNED
Six decisions, in the order they were made
Every row below is a record the engine wrote to one real run log, which was then re-verified. Open a row to see what was read, recompute its hash in your browser, and see what is signed, what is only recorded, and what no one has reported.
#1RefusedA request carrying a labelled SSN is refused by the text checkPOLICY_BLOCKED_CATEGORY · stopped at the text check; standing was not read
The policy blocks Social Security numbers and this request has one, so the gate refuses before any standing read and before any call. Only counts and a hash of what arrived are recorded.
Decided by the gate
- Verdict
- REFUSE · POLICY_BLOCKED_CATEGORY
- Destination
- https://api.anthropic.com
- Payload hash
- e770dc5d9de954d382a2f345a3c11db58aff517ec79395489b82665e74289301 (what arrived; nothing was sent)
- Handler entered
- false: refused before the call
- Counts
- ssn ×3 (never values)
Handler-reported (not part of the decision, not derived from it)
Not reported. This page records decisions and sends nothing, so there is no handler to report. In the gateway this is a separate record written after the send, labelled as handler-reported.
Verification, shown apart from the decision
- Chain
- INTACT · record 1 · previous GENESIS · this 8b0094c676a7…
- Observation hash
- not applicable: standing was not read
- Decision
- not applicable: refused at the text check
- Signature
- UNSIGNED: nobody has signed this record, so it shows what the gate recorded, not who recorded it
#2AllowedThe same request without the SSN: de-identified, and standing holdsSTANDING_HOLDS · standing read before the call
The identifiers are replaced by tokens, the destination is on the allow-list right now, so the decision is ALLOW. The record holds the observation that was read and its hash.
Decided by the gate
- Verdict
- ALLOW · STANDING_HOLDS
- Destination
- https://api.anthropic.com
- Payload hash
- 6163377f1ce6e3e9d04b964f245ed61b1c717e886b451812f18326acbdd8beb0
- Observation hash
- 3579321379563dfdbc8317f19ca2bab56b9e2217895c5dfdd3357ed760b2193a
- Read at
- 2026-10-23T14:00:00.000Z
- Handler entered
- decided before the call; the outcome is reported separately
The state that was read (published, so it can be recomputed)
{ "schema": "strix-standing-observation/v1", "destination": "https://api.anthropic.com", "observations": [ { "observe": "destination_allowlist", "destination": "https://api.anthropic.com", "listed": true, "fileSha256": "126ae05bc643e38b2dbb6cabf5999af7ca7a2b25f6f40da10ab563b5447de2fe" } ] }The exact text that was about to leave (invented data)
Member Name: [PERSON_1] Member ID: [ID_NUMBER_1] Claim Number: [CLAIM_NUMBER_1] Question: draft an appeal for the denied claim (code CO-50, billed $85.00).
Handler-reported (not part of the decision, not derived from it)
Not reported. This page records decisions and sends nothing, so there is no handler to report. In the gateway this is a separate record written after the send, labelled as handler-reported.
Verification, shown apart from the decision
- Chain
- INTACT · record 2 · previous 8b0094c676a7… · this 1ff635defefb…
- Observation hash
- MATCH when recomputed
- Decision
- MATCH when re-derived from the facts
- Signature
- UNSIGNED: nobody has signed this record, so it shows what the gate recorded, not who recorded it
#3RefusedThe identical payload after the destination left the allow-list: refused before the callSTANDING_DEFEATED · standing read before the call
Nothing about the text changed and it passes the text check. The state it depended on changed, and the gate reads state fresh on every request, so this is a REFUSE with STANDING_DEFEATED and the observation that defeated it.
Decided by the gate
- Verdict
- REFUSE · STANDING_DEFEATED
- Destination
- https://api.anthropic.com
- Payload hash
- 6163377f1ce6e3e9d04b964f245ed61b1c717e886b451812f18326acbdd8beb0
- Observation hash
- d447a9120fb6e98be7dfd4e52258994487644331dad60ff97479cd12288eee12
- Read at
- 2026-10-23T14:01:00.000Z
- Defeated by
- destination_allowlist
- Handler entered
- false: refused before the call
The state that was read (published, so it can be recomputed)
{ "schema": "strix-standing-observation/v1", "destination": "https://api.anthropic.com", "observations": [ { "observe": "destination_allowlist", "destination": "https://api.anthropic.com", "listed": false, "fileSha256": "5f8996f537b33d27fe94c02340d31688e383bc691bf265dd92202181ccf4647f" } ] }The exact text that was about to leave (invented data)
Member Name: [PERSON_1] Member ID: [ID_NUMBER_1] Claim Number: [CLAIM_NUMBER_1] Question: draft an appeal for the denied claim (code CO-50, billed $85.00).
Handler-reported (not part of the decision, not derived from it)
Not reported. This page records decisions and sends nothing, so there is no handler to report. In the gateway this is a separate record written after the send, labelled as handler-reported.
Verification, shown apart from the decision
- Chain
- INTACT · record 3 · previous 1ff635defefb… · this e1f65ef05d40…
- Observation hash
- MATCH when recomputed
- Decision
- MATCH when re-derived from the facts
- Signature
- UNSIGNED: nobody has signed this record, so it shows what the gate recorded, not who recorded it
#4AllowedThe payload is changed after the earlier ALLOW: a new decision, not a reused oneSTANDING_HOLDS · standing read before the call
A sentence was added. The payload hash differs, so this is its own row with its own record. The observation is the same state, and it is still read again.
Decided by the gate
- Verdict
- ALLOW · STANDING_HOLDS
- Destination
- https://api.anthropic.com
- Payload hash
- 9800e14b47916fed97926f5a018c28e254c40d5b6de4fbb9942916dfde95d704
- Observation hash
- 3579321379563dfdbc8317f19ca2bab56b9e2217895c5dfdd3357ed760b2193a
- Read at
- 2026-10-23T14:02:00.000Z
- Handler entered
- decided before the call; the outcome is reported separately
The state that was read (published, so it can be recomputed)
{ "schema": "strix-standing-observation/v1", "destination": "https://api.anthropic.com", "observations": [ { "observe": "destination_allowlist", "destination": "https://api.anthropic.com", "listed": true, "fileSha256": "126ae05bc643e38b2dbb6cabf5999af7ca7a2b25f6f40da10ab563b5447de2fe" } ] }The exact text that was about to leave (invented data)
Member Name: [PERSON_1] Member ID: [ID_NUMBER_1] Claim Number: [CLAIM_NUMBER_1] Question: draft an appeal for the denied claim (code CO-50, billed $85.00). Also include the plan year and the appeal deadline.
Handler-reported (not part of the decision, not derived from it)
Not reported. This page records decisions and sends nothing, so there is no handler to report. In the gateway this is a separate record written after the send, labelled as handler-reported.
Verification, shown apart from the decision
- Chain
- INTACT · record 4 · previous e1f65ef05d40… · this a2bdb47a069b…
- Observation hash
- MATCH when recomputed
- Decision
- MATCH when re-derived from the facts
- Signature
- UNSIGNED: nobody has signed this record, so it shows what the gate recorded, not who recorded it
#5RefusedA second named observation defeats standing: the budget is spentSTANDING_DEFEATED · standing read before the call
This destination's profile names two observations. The allow-list holds, the remaining budget is 0 against a minimum of 1, so the decision is REFUSE and the record names the observation that defeated it.
Decided by the gate
- Verdict
- REFUSE · STANDING_DEFEATED
- Destination
- https://api.anthropic.com
- Payload hash
- 6163377f1ce6e3e9d04b964f245ed61b1c717e886b451812f18326acbdd8beb0
- Observation hash
- e5aeb5ebd8c1ff60f37788bb8e601ede9a0884050f3d1b8e154b4c9447e74970
- Read at
- 2026-10-23T14:03:00.000Z
- Defeated by
- budget_remaining
- Handler entered
- false: refused before the call
The state that was read (published, so it can be recomputed)
{ "schema": "strix-standing-observation/v1", "destination": "https://api.anthropic.com", "observations": [ { "observe": "destination_allowlist", "destination": "https://api.anthropic.com", "listed": true, "fileSha256": "126ae05bc643e38b2dbb6cabf5999af7ca7a2b25f6f40da10ab563b5447de2fe" }, { "observe": "budget_remaining", "remaining": 0, "min": 1, "unit": "usd", "fileSha256": "ee8b3fec60ca2d69c5d58020ba32a363015df4e4e5cf865e9762469c6fa819e7" } ] }The exact text that was about to leave (invented data)
Member Name: [PERSON_1] Member ID: [ID_NUMBER_1] Claim Number: [CLAIM_NUMBER_1] Question: draft an appeal for the denied claim (code CO-50, billed $85.00).
Handler-reported (not part of the decision, not derived from it)
Not reported. This page records decisions and sends nothing, so there is no handler to report. In the gateway this is a separate record written after the send, labelled as handler-reported.
Verification, shown apart from the decision
- Chain
- INTACT · record 5 · previous a2bdb47a069b… · this dbe159a2c7d2…
- Observation hash
- MATCH when recomputed
- Decision
- MATCH when re-derived from the facts
- Signature
- UNSIGNED: nobody has signed this record, so it shows what the gate recorded, not who recorded it
#6RefusedThe state could not be read: refused, because the gate cannot tellSTANDING_UNREADABLE · standing read before the call
The file the profile names for the allow-list is not there. Not knowing is not treated as holding: the record says which observation was unreadable and the decision is REFUSE.
Decided by the gate
- Verdict
- REFUSE · STANDING_UNREADABLE
- Destination
- https://api.anthropic.com
- Payload hash
- 6163377f1ce6e3e9d04b964f245ed61b1c717e886b451812f18326acbdd8beb0
- Observation hash
- 95156bc7a4e089394fef37cc51f032bc4e6bedd6907797e357535b59d6a8cef0
- Read at
- 2026-10-23T14:04:00.000Z
- Defeated by
- destination_allowlist
- Handler entered
- false: refused before the call
The state that was read (published, so it can be recomputed)
{ "schema": "strix-standing-observation/v1", "destination": "https://api.anthropic.com", "observations": [ { "observe": "destination_allowlist", "unreadable": true } ] }The exact text that was about to leave (invented data)
Member Name: [PERSON_1] Member ID: [ID_NUMBER_1] Claim Number: [CLAIM_NUMBER_1] Question: draft an appeal for the denied claim (code CO-50, billed $85.00).
Handler-reported (not part of the decision, not derived from it)
Not reported. This page records decisions and sends nothing, so there is no handler to report. In the gateway this is a separate record written after the send, labelled as handler-reported.
Verification, shown apart from the decision
- Chain
- INTACT · record 6 · previous dbe159a2c7d2… · this c7dad6c5ec65…
- Observation hash
- MATCH when recomputed
- Decision
- MATCH when re-derived from the facts
- Signature
- UNSIGNED: nobody has signed this record, so it shows what the gate recorded, not who recorded it
What a rewritten record looks like
Row 3's decision rewritten from REFUSE to ALLOW, with the log re-chained so the chain still looks intact.
chain INTACT · observation hash MATCH · decision re-derived from the facts MISMATCH · signature UNSIGNED
The chain alone cannot catch this, because whoever rewrites a record can re-chain the log. The facts in the observation still say the destination was not on the list, so the decision no longer follows from them. A signature would also catch it; there is none yet.
What the walkthrough shows
- A request carrying an identifier the policy blocks is refused before it reaches the model.
- The same request without it has its detected identifiers replaced, and is allowed when standing holds.
- The identical payload is refused once the state it depended on changes, before the call.
- A payload changed after an earlier ALLOW is a new record with its own hash.
- The record keeps what the decision derived apart from what a handler would report.
What it claims
Gates the release of the document. Refuses if a declared field is still present in the extracted text. Records the decision. Does not claim that all personal information has been removed.
Standing is read once, immediately before the call, from the observations the profile names for this destination. A change after that read and before the call is not caught, nothing here shows the external state was frozen, and only paths that call this gate are covered. The record is hash-chained and unsigned, and a decision is not single-use.
What it does not show
- Detection of every possible sensitive string.
- That every other route to the same model is closed: only paths that call this gate are covered.
- That the external state was frozen: it is read once, immediately before the call, and a change after that read is not caught.
- Signed records. These are hash-chained and unsigned; signing is planned once the Strix platform lifecycle work is complete.
- Single-use release. An ALLOW does not consume anything.
- That a downstream provider's non-event is inside any record.
- A production deployment or a live customer estate.