fix: report truthful compatibility outcomes and verify audit coverage
Assistant: codex Assistant-Model: gpt-6-astra Assistant-Session: 01a0e747-8f27-7242-8df8-8bc44f88c929
This commit is contained in:
parent
c0383c9c2b
commit
72f3513954
7 changed files with 246 additions and 16 deletions
|
|
@ -46,8 +46,8 @@ at three seconds, uses TLS, and never follows redirects.
|
|||
Allow is blocked until the archive accepts the authorization record. A lost
|
||||
receipt blocks the business operation even if the attempt reached storage. This
|
||||
is a pre-execution authorization journal, not proof that an operation committed.
|
||||
Authorization cannot use a local success buffer or silent redaction. Native
|
||||
transaction outcomes now use a separate [durable outbox](operation-outcome-audit.md);
|
||||
Authorization cannot use a local success buffer or silent redaction. Native and
|
||||
implemented SQL compatibility transaction outcomes use a separate [durable outbox](operation-outcome-audit.md);
|
||||
its production delivery and broader mutation coverage remain T03/T04 gates.
|
||||
|
||||
The exact verified signed decision is retained under `data.signed_decision` as
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue