Phase 8: Network Soak and Observability

Plan reference: plan/glamsterdam-2026-09-05/issues/08-phase-8-network-soak-and-observability.md

Goal: make the fork boundary observable (P2-1), soak on the first public network that schedules Gloas with the zero-slashing gate enforced, re-pin SPEC_TAG to that network's shipped spec release, and drive mainnet readiness to evidence complete. release approved is a separate state this phase cannot reach (D16). Issues: 11 · Points: 20 · Duration: ~10 working days single-stream (8.8 additionally waits 14 elapsed days; the wait is not effort).

Entry criteria: Phase 7 complete (devnet metrics met, fork-transition test green in CI; 7.6 landed the PTC counters and 7.2b landed the validator_perf.py SLOT_DURATION_MS read). 8.9a–8.10 additionally require a public network with a real GLOAS_FORK_EPOCH in its config and a published spec release tag for it. 8.1–8.7 need no such network and start as soon as P7 lands.

Exit criteria (D16 — this phase closes on evidence complete, never on release approved):

• evidence complete — objectively closeable by this phase's own issues: every KAT layer (L1–L5) all green against the network's shipped spec tag before the soak starts (8.9a → 8.9b, D26); ≥ 14 consecutive stable days on that network (never a calendar date) on the exact build that passed, 0 slashable events; readiness evidence recorded in docs/gloas-observability.md by 8.10. This is Phase 8's exit gate. A KAT failure with a verdict is a triage result that blocks the soak; it never satisfies this state.
• release approved — an explicit decision by the named accountable role, which is UNASSIGNED (Q1). It is tracked separately, blocked pending assignment, and is the only state that closes the mainnet-readiness milestone. Recording the gap is not approval, and no issue here may self-approve or substitute a recorded gap for a decision.

Summary and execution plan (Day = effort day, single stream)

Sub-issues

• 8.1 Fork-resolution gauges and fork-boundary log lines
• 8.2 PTC duty and submission counters — verification no-op
• 8.3 BN capability-state gauge — consume 6.7's family and pin label hygiene
• 8.4 Signer rejections by sign type and version
• 8.5 SLOT_DURATION_MS read — verification checkpoint
• 8.6 Pre-fork alerting rules and operator dashboard doc
• 8.7 Soak evidence harness and zero-slashing check
• 8.9a Re-pin SPEC_TAG and regenerate vectors from a cold cache
• 8.9b Root-diff triage and the L1–L5 all-green verdict on the build to be soaked
• 8.8 Soak run on the first scheduling public network
• 8.10 Readiness record — evidence complete declared, release approved tracked

Plan ID → GitHub issue

Start with plan/glamsterdam-2026-09-05/issues/08-phase-8-network-soak-and-observability.md and the dependency order for sub-issues #332–#342. Read the listed Rust, shell, test, and documentation paths for the selected sub-issue, then verify its stated checks; Phase 8 is done when the L1–L5 KAT layers are green, the soak has 14 consecutive stable days with zero slashable events, and docs/gloas-observability.md records evidence complete.