published synthetic receipts
the api returned 200 with the wrong invoice amount. old releases failed current checks; a tested repair was shipped and verified on the public endpoint.
edbb1a2a91d45ab8bacefdacb714df47870786c9b1b125b58f271ddb3c9f9449the same five watchpoints were run for each candidate. blank cells mean the candidate was stopped before execution.
| candidate | amount and current schema | tenant boundary | positive access for b | unauthenticated denial | unknown invoice denial |
|---|---|---|---|---|---|
| legacy rollbackrejected | |||||
| prior rollbackrejected | |||||
| openai forward repaireligible |
swipe across the table to see all five checks →
an evidence-backed briefing generated after the verified gateway switch.
recompute the hash over redacted incident events recorded before publication. save this head independently to notice later server-side changes.
published head 0c00e544c346ecece4e84225a7408fbf9c8ff6013c4931115db62e545e8738c0
detects edits relative to the published head. it is not a signature and does not prove the events were true.
this report uses synthetic data. the vulnerable release was a synthetic fixture, not recorded model output. it contains no customer identities, access tokens, or source code.