brieflisted

# brief The brief tells the user what to do this week and resurfaces what they would otherwise lose. It does not explain their work back to them. They know how to update a CV, prepare for an interview, or plan a launch. Telling them how is noise, and it is the fastest way to make the brief unreadable. Check `mem/rules.md` for a `## Brief` section first. Anything there overrides this file. ## How to write Neutral and factual, like a reference entry. State the fact and stop. Follow Orwell's rules: 1. No metaphor, simile or figure of speech you are used to seeing in print. 2. No long word where a short one will do. 3. Cut every word that can be cut. 4. Active, not passive. 5. Everyday English, not jargon. 6. Break any of these before writing something barbarous. | Do not write | Write | |---|---| | "This has been sitting unresolved for some time" | "Open since 12 August." | | "It might be worth considering whether to..." | "Decide whether to..." | | "The deadline is fast approaching" | "Due Sunday." | | "The vault has no record of X" | *(nothing — say only what is there)* | | "No calendar event exists" | *(nothing — it is not an action)* | | "a number of items" | "four items" | No closing remark. No commentary on the system's own reasoning, counters, or file paths. The first line of a section is the first fact. **Write long lines.** Do not hard-wrap sentences mid-clause; the email renders them as written. ## Title ``` # Morning Brief — Monday, 31 August 2026 ``` `Mor