Skip to content

Campaign friction log

Stage Category Earliest actionable evidence Disposition Durable boundary Status
CPU-only image build configuration failure The first managed build could not resolve the local preceding-patch image manifest. No GPU/model contact occurred. The corrected r2 build composed the exact preceding patch and marker trace from the original immutable image and passed source/runtime attestation. Candidate image sha256:789be89fc1f16c28673fad1dbb539974f7d363c6c04ee1372a22fd12b21090d3; actual base sha256:745feb916ee816f5409fd58386114be4f22fbede7f9c0e0a7b8c4fe8dac0fb29; sha256:41c4926b08c7298fb63bc7f1204926c4f95ce9083ff610069ab442141213b1aa is a reference comparison image, not the r2 Docker base. closed before lifecycle
Live trace ambiguous output The native API returned 75 completion tokens while both worker traces reported 76, with trace-only suffix token 1654 after stop token 154827. Frozen analyzer returned unknown; no retry and no gate relaxation. Repeated-reasoning-close ticket requires a separately reviewed post-stop reconciliation contract. open fix-forward
Live trace nonreproduction The one request produced one close at index 64 and no duplicate close. Preserve the first-close store as a narrow observation; leave second-close provenance unknown. One sample does not prove the earlier duplicate-close behavior resolved. closed diagnostic / unresolved behavior
Publication replay projection omission The first sanitized response omitted the synthetic prompt_token_ids, so the analyzer stopped at a missing-field error before sequence reconciliation. Restored the exact synthetic prompt token IDs, retained the failed first replay receipt, and reran once. The permanent README replay command now returns exit 1 with the frozen GPU committed token sequence differs from native response error; native GPU evidence is unchanged. closed
Restoration quality failure Strict JSON failed before and after restoration; baseline raw response was not retained. Accept operational restoration only; do not infer equivalence or regression. Functional acceptance and promotion remain blocked. open
Restoration evidence limitation Router status receipts are byte-identical, but mounted configuration bytes were not separately captured before the trial. Claim same running router custody/readiness and no edits/restarts only. Do not claim router configuration-byte parity. explicit limitation