Lane Map
A lane is a processing container. In practice, this usually means a coherent thread where a certain kind of capture is processed with enough continuity to stay useful.
Use this page to answer one question:
Which lane should process this capture?
Lanes
| Lane | Purpose | Typical modes | Typical outputs | Boundary note |
|---|---|---|---|---|
| Projects / Ops | Process workflows, systems, pipelines, procedures, debugging, and execution mechanics. | Operational, Re-entry, Strategic | SOP, Runbook, Checklist, Next Pointer, Risk Brief | Use this lane when the capture is mainly about running, fixing, or advancing a system or workflow. Do not use it for broad personal reflection. |
| Strategy / Offers | Process product direction, packaging, positioning, choices, and opportunity framing. | Strategic, Review, Creative | Memo, Decision Note, Risk Brief, Outline, Digest | Use this lane when the capture is mainly about direction, tradeoffs, offers, or opportunity design. Do not use it for detailed step-by-step execution. |
| Reflection / Patterns | Process self-observation, recurring loops, personal friction, and support protocols. | Reflective, Review, Re-entry | Loop Map, Protocol, Closure Memo, Digest | Use this lane when the capture is mainly about your reactions, patterns, blocks, or a charged event. Do not use it for operational procedures unless the main issue is your own behavior. |
| Writing / Content | Process public writing, ideas, essays, outlines, and communication assets. | Creative, Strategic, Review | Idea Card, Outline, Memo, Digest | Use this lane when the capture is trying to become content, expression, or communication material. Do not use it for project operations unless the output is clearly a content artifact. |
| Finance / Admin | Process accounting, bills, reconciliation, and practical administration. | Operational, Strategic, Review | Checklist, Runbook, Memo, Digest | Use this lane when the capture is mainly about financial or administrative process. Do not expand it into a general operational lane. |
| Weekly Review / Governance | Process cross-lane synthesis, review, closure, and priority coordination. | Review, Re-entry, Strategic | Digest, Closure Memo, Decision Note, Next Pointer | Use this lane when the capture is about consolidation across a bounded session or period. Do not use it for first-pass processing of a live issue if another lane is clearly primary. |
Boundary notes
- A lane is a processing container, not a storage bucket.
- Choose the lane based on what the capture is for now, not on every topic it touches.
- If a capture could fit more than one lane, route it to the lane that should do the first useful processing.
- If the capture is mainly about restart or closure, Re-entry or Review may still belong inside a domain lane unless it is truly cross-lane.
- Keep lane use distinct enough that assistants stay coherent and useful.