Quick Routing
Routing table
| Raw capture is mainly... | Use mode | Route to lane | Likely artifact |
|---|---|---|---|
| explaining how a task or process works | Operational | Projects / Ops or Finance / Admin | SOP / Runbook / Checklist |
| deciding what to do or how to frame a situation | Strategic | Strategy / Offers or Projects / Ops | Memo / Decision Note / Risk Brief |
| processing a painful interaction or recurring loop | Reflective | Reflection / Patterns | Loop Map / Protocol / Closure Memo |
| preserving an idea with publishing or conceptual energy | Creative | Writing / Content | Idea Card / Outline |
| helping future-you restart later | Re-entry | relevant lane | Next Pointer / Closure Memo |
| summarizing what happened in a session or week | Review | Weekly Review / Governance | Digest / Closure Memo |
Ambiguity rule
When uncertain, choose by intended artifact rather than abstract mode.
Examples:
- if it wants to become a Runbook, use Operational
- if it wants to become a Loop Map, use Reflective
- if it wants to become a Next Pointer, use Re-entry
- if it wants to become a Memo or Decision Note, use Strategic
Fast examples
- A rough explanation of how a pipeline works -> Operational -> Projects / Ops -> Runbook
- A note about whether to pursue an offer direction -> Strategic -> Strategy / Offers -> Memo
- A recurring late-night drift pattern -> Reflective -> Reflection / Patterns -> Loop Map
- A post idea with strong energy -> Creative -> Writing / Content -> Idea Card
- End-of-session restart note -> Re-entry -> relevant lane -> Next Pointer
- Weekly closure across several threads -> Review -> Weekly Review / Governance -> Digest