capturelisted

# Capture A find that is not the work in flight costs you twice: once when you chase it, and again when you drop it and lose it. Capture is the third option. One write, no reading, no investigation, back to the task in the same turn. ## When this applies - An unrelated bug noticed while reading or changing something else. - An idea for later that has no home in the current diff. - A chore worth doing that is not worth doing now. - A direct `/capture <thing>`. ## When it does not - The find blocks the current work. Fix it, or the current work is not done. - The find is inside the current scope. Do it. - The find is a lesson about how to work rather than a thing to build. A generalization is one `insight` row now, routed later by the **debrief** skill's ladder pass; a failure occurrence is one `failure` entry now, tallied when the cause repeats; routing it into a skill in this session is the **reflect** skill. - Autonomous run and Orchestrate already fix adjacent damage themselves. Capture what they leave, not what they own. ## 1. Read the binding `.ramstack/inbox.md` in the repo root names the backend and binds three verbs: capture to the inbox, list the inbox, close an inbox item. Read it and follow it. It is the only place that knows whether a capture is a `gh issue create`, an MCP call, or a line in a file. **No binding, and you are mid-task:** write one for a local file from [`../setup-ramstack/references/inbox-local.md`](../setup-ramstack/references/inbox-local.md