wayfinderlisted

# Wayfinder A loose idea has arrived—too large for one agent session and wrapped in fog. Wayfinding finds the route to the **destination** before implementation. It charts a shared map of **decision tickets**, then resolves them until nothing material remains to decide. ## Require consent Wayfinder is user-invoked. A direct request or invocation is consent. If Wayfinder was only offered by the Deep workflow, wait for the user's explicit acceptance. Do not create an issue, file, artifact, or map before that consent. Consent to Wayfinder does not by itself authorize GitHub writes. Use GitHub issues only when issue access is available and the user's request or repository workflow authorizes those writes. Otherwise use the local Markdown fallback. ## Plan, don't do Each ticket resolves a decision. The map is complete when the way is clear and someone can implement the result. The pull to build the destination usually means the map has reached its edge and should hand off. The map's **Notes** may explicitly carry execution inside Wayfinder, but otherwise produce decisions, not deliverables. ## Refer by name Give every map and decision ticket a clear name. In narration and **Decisions so far**, wrap its link or local anchor in that name. Never use a bare id, number, or slug as the user-facing identity. ## Choose the map store Use the first available and authorized option: 1. **GitHub issues:** When the repository uses GitHub, issue access is available, and tracker wri