closelisted

# close Take one open loop and remove the friction that has kept it open. Tracking a loop is worth little; this is where the system earns its place. ## How to write Neutral, plain, direct — a reference article, not an essay. Follow Orwell's rules: no familiar figures of speech, no long word where a short one works, cut every word that can go, active over passive, everyday English over jargon. Give numbers where you have them. No throat-clearing, no closing remark. ## Procedure **1. Find the loop.** Named by the user, or picked from `loops/open/`. If they are referring to something in the last brief, read `briefs/` to resolve it. Ambiguous → list candidates. **2. Read its provenance.** Every loop cites the source that produced it. Read that source. A draft written without it will be generic, and generic is what makes the user stop using this. **3. Gather context.** `mem/profile.md` for voice and working style, `mem/people.md` if a person is involved, and any `wiki/` pages the loop touches. Cite what you use. **4. Produce the artifact — in full, not described.** | Loop | Produce | |---|---| | owes someone an email or message | the drafted message, subject line included, ready to paste | | a date or deadline | event title, date, time, and the details to paste in | | something unread | a summary of the actual source — what it says, whether it still matters | | an undecided decision | the options, what the vault knows about each, and a recommendation | | a task with no ob