Release evidence · RC 2026.08.12
Current ingestion build can ship with two explicit waivers
All 38 executed tests passed. Two chaos scenarios were skipped because the current build has only one queue; they remain release risks rather than invisible passes.
Release verdict
Evidence boundary
Functional and regression behavior passed on the current single-queue build. Release approval does not claim partial-failure isolation.
Objective and scope
Verify producer acceptance, idempotency, lookup, authentication, current overload behavior, consumer drain, and warehouse landing for sha-8132c3. Dispatcher partitioning and one-queue-down recovery are outside this build.
Results with denominators
| Suite | Planned | Executed | Passed | Skipped |
|---|---|---|---|---|
| Gateway contract | 18 | 18 | 18 | 0 |
| Consumer and warehouse | 14 | 14 | 14 | 0 |
| Failure and recovery | 8 | 6 | 4 pass + 2 expected current failures | 2 |
Executed denominator: 38. Pass denominator: 36 tests whose expected result was pass. Two current-overload tests correctly observed 503.
Defects and waivers
503; producer retry guidance must not claim the proposed response.No open functional defect was found in the current release scope.
Exit criteria
- All executed release-blocking tests pass.
- Both waivers are named in release notes.
- Production monitoring has no new alert or dashboard dependency.
- Rollback remains the prior container image.
Residual risk
This build preserves the single shared queue. It can ship because it does not worsen that risk, but it does not mitigate the incident pattern documented in RFC 014.