Read-only diagnostic workflows per 12 cases
The six novel cases still require evidence. All six recurring exact fingerprints reuse a prior green provider receipt.
CONTINUUM · ADAPTIVE DIAGNOSIS
S3 PREREGISTERED · BEDROCK · 84 GITHUB RECEIPTS
The red log is ambiguous.
Verified memory buys information.
Twelve opaque CI incidents share deliberately non-identifying red summaries. The answer key is checksum-addressed and write-once sealed before the first model call. Stateless, raw-RAG, and Continuum receive the same bounded tools; only provider-verified exact-fingerprint memory can skip a real read-only diagnostic workflow.
Public gate—workflow + artifact + S3 seal
Verified recovery—Continuum / stateless
Recurrence probes—Continuum / stateless
Paired exact p—two-sided, preregistered
All diagnostic runs—Continuum / stateless / raw-RAG
Zero-probe recurrences—Continuum / six
False promotions—Continuum
Canonical precision—Continuum
End-to-end p95—Continuum / stateless
Input tokens—Continuum / stateless
Child workflows—18 + 30 + 36
Mutation / residual—across every receipt
Same recovery, half the external diagnostic work
What the result does—and does not—say
Continuum, stateless, and raw-RAG all recovered 12/12 after the server compiled evidence into discriminated proposal schemas. The confirmed result is information value: six of six paired recurrence cases avoided a provider probe, exact p=0.03125.
Token cost did not fall: memory search and fetch used more model input tokens. This is an external-call and recurrence-latency result, not a universal cost or accuracy claim.
Server-owned adaptive contract
01SealChallenge and evaluator labels receive separate SHA-256 identities in private S3.
02SearchThe model sees opaque fingerprint-scoped handles, never evaluator labels.
03AcquireExact green memory is fetched or one real read-only probe runs.
04ConstrainThe server exposes only the evidence-consistent discriminated proposal tool.
05VerifyA separate workflow executes the proposal; only green outcomes become canonical.
Checksum-bound lineage
| Parent workflow | — |
|---|---|
| Source SHA | — |
| Artifact ID / archive SHA-256 | — |
| Challenge SHA-256 | — |
| Labels SHA-256 | — |
| Commitment / seal receipt SHA-256 | — |
| Public result SHA-256 | — |
Claim boundary. This is a preregistered twelve-case synthetic population over six reviewed CI fault families, an exact-fingerprint recurrence contract, and a real GitHub Actions provider. It proves bounded information-value and outcome-gated promotion for this population—not semantic transfer to changed environments or arbitrary repository repair.