Current V2 Series geometry capture — 2026-09-09

A fresh local-validator bank running exact native source a3dd6962f6fd366e90e512ffbf15c21d89cd6541 completed the canonical two-occurrence Series shadow diagnostic. This is unpublishable diagnostic geometry, not selected-runtime execution, parent founding, Prepare, or a completed recurrence. No V1 manifest was reused.

The bank remains at /tank/dregg-build/series-a3dd-v2-runtime-20260909, RPC 31100, validator PID 751542. The checked all-eight gate is SHA-256 051aad59506c18b7140e417cea3818a0ff835ec47aae0fcec69a68b4761bc638. The owned host-only descendant bc2691253db08563d2f343fd9a12c189dc331a32 adds the canonical native System observation correction to exact C. The sealed candidate was not changed.

geometry-system-fixed.status is zero. geometry-system-fixed.source.json binds the host/native revisions, binary digest and exact arguments; geometry-system-fixed.stdout and .stderr retain the transcript. The original failed geometry.* evidence is preserved. Because the interrupted producer had no serialized immutable-prefix continuation, its canonical publisher ran again on the same retained bank with fresh scenario identities; no onchain account was seeded or overwritten to fabricate a poststate.

Files under shadow-diagnostic-system-fixed/:

Certificate identity: c187d600870a9667ae2bd70e4b285cdb08df9a54bf44bc604a23dd25e490ccb8. The directory also contains UNPUBLISHABLE_DIAGNOSTIC_ONLY and the explicit Accelerator semantic preimage. A future selected all-eight build must consume and reauthenticate these inputs through its canonical generator and checked gate; the diagnostic directory itself grants no release authority.

The explicit diagnostic inputs were lead 600, retry 256 and period 320 slots. Template authoring observed finalized slot 12040; occurrence starts were 12640 and 12960. Schedule publication completed at 12521 and Claims prepay at 12553, 513 slots after authoring. These are measured scenario values, not protocol bounds or full-lifecycle defaults. No clock warp or recurrence wait was used. The outstanding runtime deliverable is accepted Prepare, Consume/Expire for two occurrences, their retirement, and root closure on a checked selected cohort.