Reading Source Briefings
Use generated source briefings for orientation while keeping the original document and citations authoritative.
Each source can expose an auto-generated briefing panel with document metadata and enrichment results. A briefing is a fast orientation aid for checking whether a source looks like the document you expected and deserves closer review.
In practice, many users can improve answer quality simply by learning to read briefings well.
Current data boundary: A briefing does not authorize a source for upload or use. MARCUS is an institutional non-PHI workspace. Do not upload PHI, patient identifiers, patient-specific clinical facts, credentials, secrets, or other prohibited data.
What The Briefing Shows
Depending on configuration and completed enrichment, the panel may include:
- title and author metadata when available
- document type
- publisher, publication date, version status, and metadata provenance
- summary
- key points
- concepts and tags
- optional expanded briefing text
- footer details such as pages, words, passages, and indexing timestamps
Each of these sections answers a different question about the document.
A Good Reading Order
When you open a briefing, read it in this order:
- Title and document type
- Publication, version, and provenance fields
- Summary
- Key points
- Concepts and tags
- Footer metrics
This sequence moves from "what is this source?" to "what kind of source does MARCUS think it is?" to "does the generated content look like what I expected?"
What To Look For In Each Section
| Section | What it tells you | What to watch for |
|---|---|---|
| Title and metadata | Whether the source is the one you intended to upload | Surprising title, missing author, wrong document identity |
| Document type | What kind of source this is | A document type that does not fit the project |
| Source evidence | Publication, version and metadata origins | Unknown provenance, a superseded document, or inferred information that needs checking |
| Summary | The shortest plain-language description of the source | A summary that clearly does not match the actual document |
| Key points | The facts or rules MARCUS extracted as salient | Missing core rules or oddly generic bullets |
| Concepts and tags | How the document is being classified | Tags that miss the obvious topic or feel unrelated |
| Footer metrics | Whether the file looks complete and fully indexed | Very small passage count, incomplete enrichment, or suspiciously low content volume |
How To Interpret Pending States
Some sections can still be processing after the source is already listed.
- Missing summary means enrichment is incomplete, not necessarily that indexing failed.
- Missing concepts or tags means the document may still be searchable but not richly classified.
- Unknown provenance means the origin is unrecorded; inspect the original document to check the value.
A partial briefing is not automatically a broken source, but it is a reason to be more cautious.
A Fast Reliability Check
Before relying on a source in a conversation:
- Confirm it is indexed.
- Confirm the title matches what you intended to upload.
- Check publication, version, and provenance fields.
- Check that summary and key points roughly match the document you expect.
- Open the source if the answer depends on a narrow threshold, exception, or operational nuance.
This takes less time than debugging a confusing answer later.
When A Briefing Is Telling You To Slow Down
Slow down when you notice:
- the title or type is wrong
- the summary feels vague or obviously off
- key points miss the very point you expected the document to cover
- publication or version status is unknown for a decision that depends on currency
- the footer suggests the file may not have parsed as expected
These are clues that the source may still be searchable, but not safely interpretable at a glance.
How Briefings Improve Daily Work
Briefings are useful for more than source-level curiosity. They help you:
- confirm new uploads quickly
- spot poor-quality files early
- compare documents before asking synthesis questions
- decide whether a project is filling with the right kind of material
- train new users on what "good library quality" looks like
In other words, briefings are part of library management, not just passive reading.
Common Misreadings
| Misreading | Better interpretation |
|---|---|
| "The summary is present, so the source must be fine." | A summary is helpful, but the source can still be weak or misplaced. |
| "The document is labeled a guideline, so I do not need to open it." | Document type is a classification; check the original source and its applicability. |
| "Missing tags means the source is useless." | The source may still support answers even if some enrichment fields lag or fail. |
| "The briefing is the document." | The briefing is a guide to the document, not a replacement for it. |
One Strong Habit
After every important upload, inspect the source and read its briefing when available. If the briefing does not make sense, open the original document and verify the extraction before relying on generated output.
Continue
- Clinician handbook: Sources and the Library
- Knowledge tools: Conversations and Knowledge Tools