---
name: handrail-milestone-built
description: "HANDRAIL (releases#69) — all four waves gated green 2026-08-01; wave tips, the builder-vs-assembler split, and the two riders that do NOT ride v0.50.0"
metadata: 
  node_type: memory
  type: project
  originSessionId: 6e22d89d-7795-45a1-8ea6-912e1e308177
  modified: 2026-08-01T08:50:14.158Z
---

HANDRAIL milestone (spt-core, `BigscreenVR/spt-bs-releases#69`, 8 requests): **build COMPLETE 2026-08-01**, all four waves gated green by doyle. My lane (todlando, builder) ended at his verdicts.

Wave tips as gated: **W1 GUARD** (#1) @`559632e` · **W2 TRUST CADENCE** (#63+#61) @`ff97a47`, deployah's doc leg `d4b705b` on top · **W3 CLI HONESTY** (#68,#66,#65,#39) @`2101ae4`, record #69 comment 5150223294 · **W4 FORK SURFACE** (#29) @`040026f`, record #29 comment 5150694868. Merge chain off main `2a66d78`.

**The role split is the durable part** (operator restructure 2026-07-31, runbook PR #135): the builder does NOT assemble. doyle assembles the merge chain + compile-gate + traceable-reqs; deployah runs golden per `docs/golden-head-intake`; a doc leg goes to deployah between the gate and assembly. A wave ends at the gate verdict plus its evidence — starting assembly is taking someone else's lane.

**Two riders filed OUT of W4, neither on v0.50.0** (baseline stays the greenlit 8): **#74** KNOCK_UNCONFIRMED mangled literal shipped in v0.49.0 + the rendered-help class check on xtask's leg; **#76** FORK/DISCOVER pairing consequences. Both next batch. The sealed-code CONTEXT ratification from the same day is docs-only on `spec/sealed-code-grill` @`bc1c967`, riding the future redemption wave — not this milestone.

**Why:** the wave tips and rider register are what a resumed session needs to avoid re-deriving state or re-opening closed rulings, and the builder/assembler split is a boundary that is easy to cross by being helpful. **How to apply:** on resume, treat these SHAs as gated-and-closed; route new findings to the rider register rather than into a gated wave; never open assembly. Rig procedure and the boundary observation live in [[cross-machine-test-rig]]; gate craft in [[spt-verification-gates]] and [[instrument-soundness-guards]].