published synthetic receipts

oops a650f489.

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.

recovered

http response200 ok

expected amount$12.99

amount returned$1,299.00

public checks5/5 passed

published recovery receipt

the rollback trap, resolved.

oops a650f489

legacy rollbackrejectedguard pattern absent; failed executable checks

prior rollbackrejectedamount and current schema, positive access for b

akash forward repairshippedakash proposal

verified 2026-10-09 19:43:07 UTCartifact sha256 ffe7940e279f078ca0b4621cb6c01a83d20f8e4baf57be906db4447a6ee19654

the unchanged recovery floor.

the same five watchpoints were run for each candidate. blank cells mean the candidate was stopped before execution.

candidate check details were not included in this earlier publication.

swipe across the table to see all five checks →

listen to the recovery.

an evidence-backed briefing generated after the verified gateway switch.

check the receipt chain.

recompute the hash over redacted incident events recorded before publication. save this head independently to notice later server-side changes.

published head 8a7ffc3b06559a57667524604b706b49a9c38c7d8b8174e6717d5b74b34a7487

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.