3ea01314c1
Following review: the map-body headings a cold reader sees should be self-evident without having read the skill, so drop the metaphor from the headings — `## Not yet specified` (in-scope, unripe) and `## Out of scope` (beyond the destination). Keep **fog of war** as the leading word: it still titles the explanatory section and drives the "clears the fog" / "graduate the fog" behavior in the prose. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
1.2 KiB
| mattpocock-skills |
|---|
| minor |
Split wayfinder's map-body catch-all into two plainly-named sections — ## Not yet specified and ## Out of scope — so a cold reader can tell in-scope-but-unripe work from work ruled beyond the destination.
Previously both lived under one ## Fog heading, where out-of-scope work read as takeable frontier (an unblocked, unclaimed item is indistinguishable from a live ticket). Now: Not yet specified is the in-scope frontier that graduates into tickets as decisions resolve; Out of scope is beyond the destination, closed and never graduating, returning only as a fresh effort if the destination is redrawn. The "Fog or ticket?" test becomes "Ticket, not-yet-specified, or out of scope?", gated on scope as well as sharpness, and both 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 still names the concept and drives the graduate-the-fog behavior in the skill's prose; only the human-facing map headings go to plain language.