Record overlap-then-drop bearer revocation for T09 and T11
T1 accepted 202 then 401 after drop; production T0 still 202 for approval-engine and informed-decision. No live factory token replaced. Assistant: grok Assistant-Session: 01a0a182-bab7-7f11-b32b-d06f3af52082
This commit is contained in:
parent
ff74dbce63
commit
41e119d295
2 changed files with 26 additions and 1 deletions
|
|
@ -284,11 +284,17 @@ is worth asserting in `tests/`.
|
|||
|
||||
```task
|
||||
id: AUDIT-WP-0009-T09
|
||||
status: progress
|
||||
status: done
|
||||
priority: high
|
||||
state_hub_task_id: "fd4a4ac3-e525-57c1-9179-e0fcd0226913"
|
||||
```
|
||||
|
||||
Done 2026-09-15 for the remaining audit-core gate: overlap-then-drop
|
||||
bearer revocation. T1 accepted 202, then 401 after drop; production T0
|
||||
still 202. Production tokens were not replaced. Service / domain-
|
||||
transaction / human operation stays a separate surface. Receipt:
|
||||
`docs/evidence/2026-09-15-sender-bearer-revocation.json`.
|
||||
|
||||
**Current native return, 2026-09-11 13:11 UTC:** custody/ESO delivery,
|
||||
source-adapter accepted write, duplicate-after-process-restart, exact scope/read
|
||||
refusals and own reconciliation count one passed. Independent archive readback
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue