---
name: howto-subnet-w5-scope
description: "M11-W5 must add a `how-to subnet` topic (REQ-DOCS-6) — perri found spt how-to subnet dead-ends"
metadata: 
  node_type: memory
  type: project
  originSessionId: 7f5a5890-9c8c-4043-bcb6-647b6f7a36d7
---

perri (2026-06-15, parity audit) found `spt how-to subnet` → `NO_SUCH_TOPIC` (exit 2). Verified: `HOW_TO_TOPICS` (crates/spt/src/cli.rs:4692) is locked to exactly `["ready","send"]` — "v1 topics per M7 plan decision 12", test-enforced. Genuine spt-core CONTENT gap under existing **REQ-DOCS-6** (in-binary agent guidance, single-source; docs-site points here). Not a docs-read miss, not a published-docs gap.

**Disposition (doyle):** ACCEPTED, scheduled into **M11-W5** (the rig + docs wave) — NOT a mid-flight interrupt. todlando logging it in M11-PLAN T5.x. No new REQ (REQ-DOCS-6 owns it).

**W5 build = ** HOW_TO_SUBNET text (the create / show-code / join pairing flow + 6-digit code) + registry entry + bump the v1-lock test (the `names == vec!["ready","send"]` assertion + topic-content asserts). Subnet/pairing is the highest-value first-run flow; closes the ready/send asymmetry.

**At the W5 gate I must confirm** this rung landed (topic present, `spt how-to subnet` exits 0, test updated). Relates to [[m11-w2-progress]] (W2 done, W3→W4→W5 ahead), [[perri-question-triage-protocol]] (verified-before-disposition).