capturelisted

# Wherefore: capture Turn a raw or AI-generated discussion into one compact, retrievable wherefore entry. Preserve the useful residue (what was decided, why, and what was rejected), not a transcript. Months later, someone asking "why did we build it this way?" should get the answer in a few sentences. ## Writing style The record must read well as a raw markdown file, not just in the dashboard. Editors and the GitHub blob view are where most people read it. - No em dashes anywhere. Use periods, commas, colons, semicolons, or parentheses. Firm project rule. - Decisions are verdict-led. Open each bullet with the ruling as a short standalone clause; put elaboration after it or in Why. Someone reading only the first clause of every bullet should still get the full outcome. - One decision per bullet. Split compound bullets. - Do not use inline bold to fake structure. The lead clause carries the scan. Bold scattered mid-sentence is the main cause of wall-of-text records. Reserve emphasis for a rare load-bearing term. - Keep sentences short and concrete. - Why is the single home for rationale. State the outcome in Decisions, the reasoning in Why. Do not scatter reasoning across decision bullets. - Unresolved threads are not decisions. They go to Open questions and become a numbered question (`Q-NNN` id, in a `Q-NNN-short-slug.md` file), never a Decisions bullet dressed as certainty. Verdict-led, in practice: - Weak: "There are two fulfillment paths, direct and via inventory, and