legal-wayfinder

# Legal Wayfinder — Decision Maps for Big Legal Matters A big legal matter arrives wrapped in fog: the route from intake to deliverable is not visible yet. Wayfinding finds that route by resolving **decisions** — not by executing work slices. The map is the plan; execution happens only after handoff. **Plan, don't do.** Every ticket resolves a decision. Supporting memos and prototypes are linked as assets, but no client deliverable is drafted inside the map. A matter may override this in the map's **Notes** (carrying execution into the map); absent that, produce decisions, not deliverables. **Refer by name.** In everything the attorney reads, refer to a ticket by its title, never a bare id. Ids ride inside the linked name: `[Limitation period open?](tickets/t01-limitation-period-open.md)`. ## Storage Everything lives inside the matter folder — never in memory keys, never synced anywhere: ``` bcc-output/YYYY-MM-DD-<slug>/wayfinder/ map.md tickets/ t01-limitation-period-open.md t02-forum-choice-zh-or-federal.md assets/ ← research memos, prototype outlines linked from tickets ``` ## The Map (`map.md`) ```markdown --- matter: <slug> status: charting | working | ready-for-handoff | handed-off privacy-mode: strict | balanced | cloud classifier: ollama | none jurisdiction: federal | <canton> language: DE | FR | IT | EN --- ## Destination <1–2 lines: the deliverable this matter is finding its way to. Fixes scope; every session orients to it before choo...