Most AI summaries die the day after you read them.
You ask an AI assistant to summarise your notes, it returns a wall of text, and that is the end of the thinking. You cannot edit the structure. You cannot click a claim to see what it is based on. Tomorrow, when a new meeting transcript or document lands in your brain, the summary does not know about it. The summary was a photograph; what you needed was a document.
How a briefing gets built
Describe what the briefing is about.
Write a description in plain English. The brain parses it into a typed retrieval brief: anchors (the entities and topics the briefing centres on), intent axes (what angle of those topics matters), exclusions (what is off-limits), temporal window, and voice. Sparse descriptions still work, they just produce thinner briefs. The brief is the contract.
Pick which brains feed the briefing.
Each briefing can pull from multiple brains at once. The pipeline fans out across the selected brains in a single retrieval pass, then aggregates the candidates while preserving brain attribution across dedup. One briefing can draw on Personal plus Marketing plus one client brain, and every fact in the report still knows which brain surfaced it.
Edit the document, accept the proposed additions.
The brain proposes three to six sections from your description, routes candidates into them with a confidence score and a reason, and writes the body as a Notion-style block document with citations inline. As you add new material to your brains, the pipeline re-runs on the new content alone and drops proposals into a pending tray on the right rail. You accept what should land, you reject what should not.
Notion-style block editor, citations inline
The briefing is a real document. Edit any block, drag to reorder, insert your own paragraphs between the brain's blocks, restructure sections. Citations live as inline pills you can click to see the source fact. The brain writes the first version; the editor makes it yours.
New evidence waits for your call
As new material lands in your selected brains, the pipeline re-runs on the new content alone and proposes additions to the right rail. Each proposal carries a confidence score, the section the brain wants it under, the routing reason, and the source facts. Accept moves it into the document as a block. Reject teaches the brain to never propose that source to this briefing again.
Confidence on every card
Green at 0.85+, amber at 0.7+, red below. Below the threshold (default 0.6) the proposal never reaches you at all, dropped server-side.
Routing reason
Every proposal explains why the brain picked this section. Hover to see the model's reasoning, decide if it holds up.
Source facts attached
Each proposal carries the underlying facts from your brain, with the brain attribution. Click through to the original before accepting.
Reject is permanent
Rejected sources land in this briefing's exclusion list. The pipeline reads exclusions before routing, so the same fact never gets proposed again.
What keeps a briefing accurate
The description is the contract
Parses into a typed retrieval brief (anchors, intent axes, exclusions, time window, voice). The rest of the pipeline runs against that brief. Sparse description, thin brief. Specific description, sharp brief. The model cannot improvise around what you wrote.
Multi-brain by design
Retrieval fans out across the brains you selected in one pass. Dedup preserves brain attribution across namespaces, so a fact found in Personal and Marketing still surfaces both brains. No "everything looks like Personal" mis-attribution.
You stay the editor
The brain proposes. You accept or reject what enters. The block editor lets you rewrite, reorder, and insert your own thinking next to the brain's. Reject feeds exclusions, so what you said no to does not come back.
What you walk away with
Pairs well with
Multiple brains
The richest briefings pull from several brains. Read how multi-brain routes facts and preserves attribution across dedup, so one briefing can mix client, personal, and marketing knowledge.
Voice notes
Briefings are only as good as the brains they read. Voice notes are the fastest way to capture the thinking that does not make it into a document, so it shows up as a pending-tray proposal next time the pipeline runs.
Frequently asked questions
How is this different from asking an AI assistant to summarise my docs?
What does the Notion-style editor let me actually do?
What is the pending tray and how does it stay accurate?
Can a briefing pull from multiple brains?
How does the description affect what ends up in the briefing?
Can the model invent sources or sections?
Can I tell the briefing what NOT to include?
Will my brains' data leak across briefings?
Two ways to keep the briefing fed
Capture from Claude chat
The MCP connector saves notes, files, web pages, YouTube videos, and voice memos to your brain straight from Claude. Each new document is a candidate for the next pending-tray proposal.
Auto-fill via Zapier
Point a Zap at Krisp, tl;dv, Google Drive, or a YouTube channel. Each new recording or document flows into your brain, the pipeline re-runs, and proposals land in your tray without you lifting a finger.
A document, not a screenshot.
Start free with 40 documents. Build a brain. Write a description. Watch the briefing grow as your brain grows.