Respecify the out-of-scope dimension as a scope-boundary row

[Carr1005]

The upstream fix for #15 and #16. Those patch two existing specs; this one makes future specs come out right.

The problem

Every spec this guide generates inherits the same defect:

• The exclusion list lives in §1. The §0 gate presents Ledger rows. Nothing connects them, so the list is never rendered to the learner.
• The out-of-scope row's default is a pointer at §1 — and since the gate presents rows one at a time, the learner is asked to amend a list they have never seen.
• The dimension is near-empty as specified. Subtraction belongs to integration mode, which this guide explicitly defers. In standalone-takeaway mode the deliverable is fixed and pinned by the acceptance criteria, and every subtraction a learner would plausibly want is already an Options pick on another row.

The agent-memory spec shows where that lands: an Options cell reading Add exclusions freely — one entry, so the row can't even be asked through a structured question tool.

The change

Respecifies the dimension as a scope-boundary row (§5.5), with four requirements:

1. The Decision cell instructs the gate to present the §1 list inside the question.
2. The Default is keep-as-is.
3. The Options offer restoration without pre-naming what the learner should want back — and must hold at least two entries.
4. Each excluded item carries a handling rule: restorable / buildable-but-unsupported / defer to the owning row / unavailable in this build mode.

Plus a §14 pre-handoff checklist line, so the generating agent catches a non-compliant row before you ever see the file, and a note on the §1 template that its bullets get read aloud in a question.

What is deliberately not changed

The §6.0 gate template. It would be natural to add a clause there licensing the follow-up that captures which items to restore. I left it alone: that template is copied verbatim into every generated spec, and edits near the one-question-per-row and hard-stop rules risk re-opening the exact failures §12.10 and §12.11 document. The row spec carries the requirement instead.

Diff shape

+17 / -5, all in §3, §5.5, §6, and §14. Four are the dimension rename (out-of-scope → scope-boundary) at its naming sites; the rest is the new §5.5 paragraph, the §1 template note, and the checklist line. Verified the §6.0 template has zero changed lines.

Review order

#15 and #16 are independent of this and can merge in any order — they hand-apply what this guide would now generate. If you'd rather see the generated output first, merge those two and re-run /generate-spec on a course after this one lands to confirm a fresh spec produces the same row.

🤖 Generated with Claude Code