Use lessons 01–04 or equivalent skills before this exercise. You can revisit them from the lesson list.
A browser and text editor. Live source discovery needs browsing; all supplied exercises also work offline.
Start with the idea
Keep exceptions when summarizing long documents.
Find the rule and its exceptions before combining summaries. Preserve section references. A short summary must not turn a qualified rule into an absolute one.
Provenance: The record connecting a statement to its source and version.
See the example and check your understanding
A made-up teaching example
Section two says standard review takes five days. Section eight requires supervisor review for urgent requests without a timing guarantee. “All reviews finish in five days” loses that exception.
Ask yourself
Does the standard-review timing also establish urgent-review timing?
Show the explanation
No. Keep urgent timing unknown and cite both sections. Check the applicable version’s conditions.
Start with these checks
- Look for exceptions in distant sections.
- Keep source and version references.
- Preserve exclusions and unresolved timing.
Use the different practice case below and check every requirement in its full instructions.
Full learning objectives
- Preserve source and section IDs.
- Check cross-document dependencies.
- Detect missing or stale context.
Captions appear here during playback.
Research across long documents without losing provenance
Keep exceptions when summarizing long documents.
Video playback is unavailable. Read the descriptive transcript below, go directly to practice, or open the video file.
Source-based teaching example · Fictional data · Reviewed 2026-10-03. Microsoft Mark · locally synthesized. On a small screen, use fullscreen for diagram details or read the transcript.
Read the descriptive transcript
0:00 · What you will learn
Keep exceptions when summarizing long documents.
What appears on screen
Keep exceptions when summarizing long documents.
0:06 · The idea
Find the rule and its exceptions before combining summaries. Preserve section references. A short summary must not turn a qualified rule into an absolute one.
What appears on screen
Find the rule and its exceptions before combining summaries. Preserve section references. A short summary must not turn a qualified rule into an absolute one.
0:19 · One useful term
Provenance. The record connecting a statement to its source and version.
What appears on screen
The record connecting a statement to its source and version.
0:27 · A worked example
Section two says standard review takes five days. Section eight requires supervisor review for urgent requests without a timing guarantee. “All reviews finish in five days” loses that exception.
What appears on screen
Section two says standard review takes five days. Section eight requires supervisor review for urgent requests without a timing guarantee. “All reviews finish in five days” loses that exception.
0:43 · Your turn to think
Does the standard-review timing also establish urgent-review timing? Pause and decide before continuing.
What appears on screen
Does the standard-review timing also establish urgent-review timing? Pause the video if you need more time.
1:00 · Why this answer works
No. Keep urgent timing unknown and cite both sections. Check the applicable version’s conditions.
What appears on screen
No. Keep urgent timing unknown and cite both sections. Check the applicable version’s conditions.
1:10 · Check 1
Look for exceptions in distant sections.
What appears on screen
Look for exceptions in distant sections.
1:16 · Check 2
Keep source and version references.
What appears on screen
Keep source and version references.
1:21 · Check 3
Preserve exclusions and unresolved timing.
What appears on screen
Preserve exclusions and unresolved timing.
1:27 · Now try a different case
Open the lesson and try its different practice case. Use every check in the full task. Watching alone does not mark the lesson complete.
What appears on screen
Open the lesson Try the new case Check and revise The full task and its requirements are in the linked lesson.
Watching explains the example. Complete the lesson practice to check what you can do. Explore all visual lessons →
The method
For long material, establish a document map before summarizing: version, section, subject, exceptions and cross-references. Split at meaningful boundaries and attach source IDs to excerpts. A short summary is an index to evidence, not a replacement for the original. Check critical claims against the source before combining summaries.
Use direct context for a small corpus that fits and remains inspectable. Retrieval may help larger collections, but a missing result does not prove a fact is absent. Test answerable, unanswerable and conflicting questions. Preserve permissions during retrieval. When a source changes, revisit dependent claims; updating one summary without its cross-reference can create an internally inconsistent report.
Choose your model, harness and offline route
Text-only assistant
Use supplied text. Ask for a plan or draft; do not claim browsing, code execution or file access that was unavailable.
Tool-enabled application or harness
Record which tools actually run, allowed files and actions, approval boundaries and observable results. Tools are optional unless the task needs them.
Local or cloud deployment
Inspect inference, retrieval, connectors, logs and storage separately. Use only authorized environments for real data; training fixtures are fictional.
Higher-capability or frontier model
Evaluate the exact task and configuration. Capability does not supply missing evidence or grant permission. No provider ranking or guarantee is implied.
Offline alternative
Use the supplied inputs and inspect the worked example manually. Builder exercises use local deterministic Python. No paid account or live model call is required.
Record the exact product/model label when available, tools actually used, inputs, permitted actions, observed output and checks. Live accounts or APIs may have external costs; they are optional and are not used by this page.
Read the general workflow guide →Worked example
Supplied input
Fictional manual M1 §2: standard review takes five days. M1 §8: urgent requests require supervisor review; no timing guarantee. Summary A: “All reviews finish within five days.”
A checked result
Map standard timing to §2 and urgent exceptions to §8. Repair “all” to “standard review.” Urgent timing remains unknown. Preserve both references in the combined synthesis.
Why this works
An exception in a distant section changes the claim. Summarizing sections independently can hide that dependency.
Try a different case
Independent corpus: C1 §1 permits public summaries; C1 §6 excludes personal records; C2 v2 requires owner review before release. Draft a release checklist with source IDs, then explain what changes if C2 v3 removes that review requirement in the fictional case.
Download this task and checklist →Interactive practice / Fictional fixture
Update the evidence-linked checklist
Use the supplied independent case above. Check the bounded decisions, then review your written artifact against the full acceptance criteria.
Everything runs in this browser. No AI model is called and no work is uploaded. Bounded checks cover specific facts and rules. Your writing is not graded: you review it yourself. Practice never marks a lesson complete automatically.
Use source/section IDs, retain the exclusion, and distinguish the fictional versions.
Try the task, run the checks, then revise. Checks are teaching feedback, not an instructor grade.
Observed browser simulation
This trace comes from the bounded local checker. It is not a Python run, model result or production tool execution.
Keep or restore your work
Drafts are not saved automatically. Save only fictional practice data. A browser draft may be lost if storage is cleared; download a copy to keep it.
Your steps
- Build the document map and claim ledger.
- Check the public-summary rule against its exception.
- Record the version change and which checklist item it affects.
Check your work
- Keep the personal-record exclusion.
- Apply only the supplied version’s release condition.
- Do not claim a real organization permits disclosure.
After your attempt: review notes and a common mistake
The owner-review item changes with C2’s version; C1’s exclusion does not. “Public summaries are always releasable” ignores the exception and version-specific conditions.
Different wording or a different justified decision can pass. Check your work against every requirement; these notes are not an automated grade.
Explain your approach
How would you test a retrieval workflow for an omitted exception?
Keep your artifact, one correction or decision, its evidence and one remaining limitation. Nothing on this page sends or uploads your work.
Check your understanding
Choose an answer to see feedback. This is a knowledge check, not instructor assessment.
Review your independent practice
Complete the supplied task before recording progress. Use the acceptance criteria and reveal the review notes after your attempt. Keep your artifact yourself; nothing is uploaded.
Not yet self-reviewed. Completion stays in this browser and does not issue a badge.
Optional deeper study
Explore the related general-course lesson → This opens the existing canonical lesson; it is optional depth, not another copy of this focused task.
Primary references
Revision 2026-10-03. Fictional examples, not observed provider results. Knowledge checks and completion records are self-study aids.