Use Briefing Digests in Cortex
Briefing digests turn scoped feed material into recurring narrative updates with titled sections, summary fields, and a format that is easy for operators to read.
Cortex reads the selected feed scope over the chosen time window and synthesizes the content your feeds have kept into a recurring briefing.
The saved output is a structured briefing payload with titled sections and may also include summary fields such as meta_summary and key_summaries.
- Daily or weekly operator reviews
- Executive summaries and stakeholder updates
- Monitoring workflows where the output should explain what changed and why it matters
- Cases where the consumer wants sections and prose instead of rows
Briefing and dataset digests share the same core settings. The difference is what gets generated. A briefing produces a structured report with titled sections and summaries.
How to Use
Briefing has no type-specific form fields beyond the shared digest settings. Most briefing quality comes from getting the objective, feed scope, and time window right for the reader and how often you plan to run it.
| Name | Description |
|---|---|
| Objective |
State what the briefing should help the reader understand or decide. The best objectives describe the job to be done, not just the topic area.
Example
Give the product team a concise daily briefing on major AI model launches, benchmark results, and safety updates.
|
| Feed Scope |
Use feed scope to limit the briefing to the feeds that actually belong in the same deliverable. A briefing usually degrades when it mixes unrelated feeds into one output.
Example
Model Labs, Research Papers, Safety Updates
|
| Time Window (days) |
Match the time window to the reporting rhythm. Shorter windows help recurring operator briefs stay focused and reduce repeated material.
Example
1
|
For the full config schema, see Create Digest in the API docs.
Examples
These examples show the kind of recurring outputs briefing handles well in practice.
Daily Operator Brief
Use this when one operator needs a top-of-day readout across a few tightly related monitoring feeds.
- Model Labs
- Research Papers
- Safety Updates
Weekly Research Review
Use this when the reader wants a synthesis of the most important developments over a longer reporting window.
- Research Papers
- Lab Blogs
Preflight Launch Summary
Use this when a team needs a recurring summary before a planning or launch meeting.
- Competitor Watch
- Industry News
Troubleshooting & FAQ
The briefing feels generic or repetitive.
Rewrite the objective around the specific reader and decision the briefing should support.
This usually means the objective is too broad or too topic-only. Tighten the feed scope if unrelated material is getting mixed in.
The briefing includes too many unrelated items.
Use a narrower feed scope or separate the work into more than one digest.
A single briefing usually works best when the feeds serve one coherent operator or stakeholder job.
The briefing is too long or stale.
The time window may be too large for the reporting cadence you want.
Reducing the window often improves focus more than asking the model to summarize harder.
The briefing is cleanly written, but the signal is weak.
Check the feeds first — the problem is usually in feed scope or feed quality, not in the briefing.
Fix the feeds, then revisit the digest objective if the output still misses the mark.