The briefing you wish someone had written for you

A teammate takes over a beat, joins a project mid-stream, comes back from leave, or gets handed a new portfolio. They need to catch up on months of activity — meetings, filings, press, internal decisions — and they need it distilled, not a firehose.

This ability writes that briefing.

What it does

Takes a plain-language request: “Catch me up on the Sanjana project since March. What happened, who weighed in, what’s still open.”
Reads across every watched source, every document the team has dropped in, and every standing report the brain has already generated in the named time window.
Writes a structured catch-up brief — what happened, in what order, who said what, what’s unresolved — in the cadence your team reads briefs in.
Delivers it as one document, with links back to the source items so the reader can drill down on whatever matters.

The reveal

A senior writer takes over the city-hall beat on a Monday. Tuesday morning she has a twelve-page catch-up brief in her inbox covering the six months before her start date — agendas, key votes, the reporters who’ve been owning it, the open questions. She walks into the Wednesday editorial meeting already oriented.

What it doesn’t do

No synthesis beyond what’s in the sources. No “here’s what I think you should do.” It tells you what happened, who was involved, and what’s unfinished; the reader brings the judgment.

Configuration

Time window: default to “since X” or “the last Y” — the brain backfills as far as its sources reach.
Scope filters: people, parcels, topics, or named sources to focus on.
Output shape: narrative, bullet summary, or timeline — whatever the reader prefers.

Triggers