briefing

Briefing Skill

Compile a daily briefing from brain context.

Filing rule: When the briefing creates or updates brain pages, follow skills/_brain-filing-rules.md (via get_skill _brain-filing-rules).

Contract

• Every fact in the briefing includes an inline [Source: slug, updated DATE] citation.
• Meeting participants are resolved against the brain; gaps are explicitly flagged.
• Active deals and action items include deadlines and recency context.
• The briefing is read-only: no brain pages are created or modified unless the user explicitly requests it.
• Stale alerts surface pages relevant to today's context, not just all stale pages.

Phases

1. Hot memory pulse. Before composing anything else, pull the since-last-briefing window and its deltas:

   chronicle_last_seen            → when the operator was last briefed
   recall { since: <last_seen> }  → new facts in the window
   fact_supersessions             → contradictions resolved in the window
   get_recent_salience            → top entities by recent activity
   chronicle_since <last_seen>    → the narrative of what happened
   

   Fold the result into the briefing under a "Brain pulse" section at the top:

   1. Contradictions resolved overnight — the fact_supersessions output. Lead with these because they're new corrections to your model of the world.
   2. Top mentions — from get_recent_salience (top 5 entity slugs by recent-activity weight in the window).
   3. New facts since last briefing — group the recall facts under each entity from the salience list; include kind, notability, and confidence.
   4. Consolidation footer — the brain's background cycle handles fact consolidation on its own schedule; if run_doctor reports the cycle in a warn state, note it so the operator can run memex cycle before reading further.

   chronicle_last_seen advances the cursor so the next briefing picks up exactly where this one left off — no local cursor file to manage; the brain tracks it server-side, which also makes timer-driven runs safe.