briefinglisted

# briefing Produces a **one-page briefing**: a terse status or standup update for a recurring audience — a standup, a sync, a regular stakeholder update — who already hold the backdrop and need the delta and the next action, fast. It is harness-native: no named external body (ISO/NISO/ANSI/APA/etc.) prescribes a "briefing" format, so there is no domain standard to conform to here. ## Pattern (one-page briefing / standup update) 1. **Headline** — one line: the single most important thing to know right now. 2. **What's New** — 2 to 4 bullets of the latest developments since the last briefing. Favor the delta (changed or new items) over restating what's already known. 3. **Why It Matters** — one line per item: the implication or so-what. Every "What's New" bullet is paired with one of these — there is no orphan update. 4. **What's Next / Asks** — the next actions, owners, and any decisions or inputs needed. Name something concrete; "continue monitoring" is not an ask. Front matter carries a title, a date, and the period the briefing covers (since the last update). No figures are required — this is a one-pager; add a single status indicator only if it replaces a sentence, and render it as a Mermaid `xychart-beta`, never ASCII art or an image. A footnote/source list is the only back matter, and only when citation markers are used. ## Rules - Hard ceiling: one page. If it spills over, cut to the delta — the freshest, most decision-relevant items win over restate