7d34a8dc38
QA follow-up: the Fog of war section was teaching both concepts, which muddies the leading word — fog should point only *toward* the destination. Now Fog of war teaches only the not-yet-specified bucket (with the two-way fog-or-ticket sharpness test restored), and a new Out of scope section owns the scope axis: beyond the destination, closed not graduating, kept out of Decisions so far. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
11 lines
1.3 KiB
Markdown
11 lines
1.3 KiB
Markdown
---
|
|
"mattpocock-skills": minor
|
|
---
|
|
|
|
Give **`wayfinder`** a first-class notion of **out of scope**, separate from fog.
|
|
|
|
Fog and out-of-scope were conflated under one `## Fog` map section, gated by different things: fog by *knowledge* (can't specify it yet — in scope, unripe, graduates as the frontier advances), out-of-scope by *scope* (beyond the destination — never graduates). Cramming both under "Fog" made out-of-scope work read as takeable frontier (an unblocked, unclaimed item is indistinguishable from a live ticket).
|
|
|
|
Now the map body has two plainly-named sections — **`## Not yet specified`** and **`## Out of scope`** — and the skill's prose splits to match: the **Fog of war** section teaches only the not-yet-specified bucket and keeps the two-way *fog-or-ticket* sharpness test, while a new **Out of scope** section owns the scope axis (beyond the destination, closed not graduating, returns only as a fresh effort if the destination is redrawn). Charting and working-the-map now rule a beyond-destination ticket out of scope — close it, one line in *Out of scope* — rather than leaving it on the frontier or logging it in *Decisions so far*.
|
|
|
|
The **fog of war** leading word is retained: it names the concept and drives the graduate-the-fog behavior in the prose; only the human-facing map headings go to plain language.
|