refactor(wayfinder): loosen fog length, dedup fog guidance
Drop the "one-liner" constraint — fog entries can be as loose or full as the view allows. Point the map template's Fog comment at the Fog-of-war section instead of restating it, and remove the duplicated "not a ticket" now that the keep-out clause covers it. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This commit is contained in:
parent
d49cd08a11
commit
039820a47d
1 changed files with 2 additions and 2 deletions
|
|
@ -25,7 +25,7 @@ The whole map at low resolution, loaded once per session. Open tickets are **not
|
|||
- [<closed ticket title>](<link>) — <one-line gist of the answer>
|
||||
|
||||
## Fog
|
||||
<!-- terse prose: what's dimly visible beyond the frontier, not yet tickets -->
|
||||
<!-- see "Fog of war" for what belongs here -->
|
||||
```
|
||||
|
||||
### Tickets
|
||||
|
|
@ -57,7 +57,7 @@ The answer isn't part of the body — it's recorded on resolution (see [Work thr
|
|||
|
||||
The map is _deliberately_ incomplete beyond the frontier — don't chart what you can't yet see. Only the frontier becomes real tickets; everything dimmer stays fog until it comes into focus. Resolving a frontier ticket pushes the frontier forward, graduating fog into fresh tickets — one ticket at a time, until the way to the goal is clear and no tickets remain.
|
||||
|
||||
The map's **Fog** section is where that dim view is written down: decisions and investigations you can already tell are coming but can't specify yet, because they hang on questions the frontier hasn't answered. Write each as a rough one-liner — the suspected question, the area to revisit later, the risk you're deferring — not a ticket. It doubles as a signpost for collaborators reading where the effort is headed. Keep out what's already decided (that belongs in Decisions so far) and what's actionable now (that becomes a ticket).
|
||||
The map's **Fog** section is where that dim view is written down: decisions and investigations you can already tell are coming but can't specify yet, because they hang on questions the frontier hasn't answered — the suspected question, the area to revisit later, the risk you're deferring. Write as loosely or as fully as the view allows; it doubles as a signpost for collaborators reading where the effort is headed. Keep out what's already decided (that belongs in Decisions so far) and what's actionable now (that becomes a ticket).
|
||||
|
||||
## Invocation
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue