chartinglisted

# Charting — find the way, don't charge at the destination An idea arrives too big for one session and wrapped in fog: you can see the **destination**, but not the route. Charting is the work of finding that route. It writes the route down as a **map** on the issue tracker and then walks it, one ticket per session, until nothing is left to decide. > Prior art: the `wayfinder` skill. This is a re-derivation, not a copy. **The stage is charting. The artifact is the map. They never share a name.** ## The destination is an input Charting does not know what you are building. **Whoever invokes it supplies the destination**, every time — a spec to hand off, a decision to lock before planning starts, a change made in place. The map is domain-agnostic. It charts a docs effort as readily as a migration. If no destination was supplied, that is the first thing to settle, and it is settled with the human before a single ticket exists. The destination fixes the scope, so everything downstream depends on it. ## Decide or make — one or the other, never both > Every ticket is a **decision** or a **make**. A decision ticket writes no files. A make > ticket decides nothing new. If it finds a real decision, it **stops and opens one**. They cannot share a ticket because they end differently. A decision ends when the human and the agent agree, which nobody can predict. A make ends when the file is on disk. Put both in one ticket and the unpredictable half eats the context the predictable