---
name: w5-monic-wave
description: "W5 (monic store + trust warning) GATE PASSED 2026-07-31 @5224e8c — milestone releases#53 build scope W4+W5 COMPLETE; register + standing debt + the doc-leg lessons"
metadata: 
  node_type: memory
  type: project
  originSessionId: e28594ae-d005-4f54-998f-306a9986a631
  modified: 2026-07-31T18:13:09.054Z
---

**W5 WAVE GATE PASSED 2026-07-31** (doyle, full record on releases#53 comment
5146044735) at **@5224e8c**, branch `build/monic-w5`. Milestone **releases#53's
build scope (W4 + W5) is COMPLETE**. Register for the next golden assembly:
`build/monic-w5` **plus hertz's two lanes** (@cfecc77 + @b6fbe40, the
uniform-table sweep — see [[uniform-table-blindness-sweep]]).

Task SHAs: T1 @c254a65 · T2 @e3412f3 · T5 @a7884b8 · T3 @7f652f2 · T4 @0e1a074 ·
T6 @e8e81d2 · T7 @062b158 (+rulings @3079455) · T8 @c90c1e6 + @d173375 ·
T9 @5224e8c. Post-gate prose fixup @3c60819 (register decision referred to
doyle, not assumed — see below).

**STANDING DEBT, carried honestly into the release wave's FIELD-VERIFY
CHECKLIST:** the elevated `endpoint trust-warning set/reset` write was never run
live — it needs a UAC prompt this host cannot raise unattended. Proven instead
by planting the bytes an elevated write produces. Doyle accepted it as a stated
limit at T7 and again at the wave gate.

**Doyle's closing assessment, worth keeping as the bar:** the discipline
compounding across tasks — *replacement corrections, census-before-build,
evidence-or-no-stage* — is now "the documented standard this project gates
against."

## Doc-leg lessons (T9), reusable

- **Tagging a doc means auditing it.** Activating a `doc` stage forced reading
  CONTEXT §trust warning against what shipped, and **two claims were false**:
  it described the trigger condition as posture-closed-∧-passed (the shipped one
  is the *verdict* saying an ENTRY admitted the sender — not a paraphrase, since
  same-node and Reply both pass a closed posture and never warn), and it
  documented an override surface `trust-warning [--id] [--overwrite]` that
  **never shipped**. Both replaced. The doc stage is the audit trigger, not a
  formality.
- **Destination-as-shipped is the recurring class here** (caught ×3 at W4, twice
  more at W5). A design sentence sitting next to shipped text reads as shipped.
  Treatment that doyle rewards: **mark, don't strike** — CONTEXT is authoritative
  for meaning and legitimately leads implementation, so the destination stays and
  gains the limit. See [[correct-by-replacement-not-annotation]].
- **An internal symbol belongs in the REQ text, not a public guide.** Doyle asked
  the restamp limit be recorded "naming `restamp_wan_user_msg` exactly". Put it
  in `REQ-MONIC-DELIVERY-TRIGGER`'s text (durable, where a future wave looks) and
  stated the same limit in user language in the docs-site guide. Accepted.
- **Verify rendered docs, don't assume.** `mdbook build` then grep the emitted
  HTML for the anchor id and each cross-link. Caught nothing this time but costs
  seconds; a broken anchor is invisible in markdown review.
- **`xtask gen` genuinely is a no-op** when the CLI reference is regenerated
  per-task — confirmed by gen-then-`git status`. Run it anyway; it is CI-gated.

## Referring a register decision instead of taking it

A post-gate commit **moves the register sha**, which is the gater's to decide.
The W4 precedent (comment-only fixup over a gated sha, delta verified, becoming
the register) is a *precedent*, not standing permission. Pattern used: push the
fix (do not sit on a false-reading sentence you spotted), verify and state the
delta scope, then explicitly hand the keep-or-move choice back with both options
named. Do not move a gater's register silently.