# Turn scattered context into an inspectable pack Published and revised: October 13, 2026 · Version 1.0.0 Make a small task brief and knowledge pack that preserve uncertainty, source conditions, and conflicting findings. ## Goal and proposed time Create a source-backed starting point that another reader can inspect without relying on your conversation history. Allow 85–115 minutes, including selected reading, making the outputs, and review. This is a proposed study budget, not measured completion time. Split the path across sessions if needed; stop at a checkpoint rather than rushing an evidence check. ## Prerequisites and inputs - One narrow question you can explain in a sentence - Use the linked synthetic examples or up to three public sources whose permitted use you can establish Use only the linked guides and their public or synthetic fixtures. A text editor, calculator, and timer are enough. No provider connection, account change, publication, or outside communication is required. ## Work through the path ### 1. Organize context before you ask Read [the guide](/workspace-development/organize-context-task-briefs/). Write the reader’s decision and three observable acceptance checks. Register the permitted sources before asking for more context. Carry forward: A one-page brief and source register with authority and reuse limits. ### 2. Synthesize research without hiding disagreement Read [the guide](/workspace-development/synthesize-research-disagreement-map/). Use the three synthetic pilot records to compare measures, settings, and populations. Explain what the records do and do not establish. Carry forward: A disagreement map that separates observations from recommendations. ### 3. Build a knowledge pack you can inspect Read [the guide](/workspace-development/author-knowledge-pack-source-ledger/). Use the Paperlight fixture to create atomic claim IDs and derived values. Add answerability tests that expose tempting unsupported conclusions. Carry forward: A narrow versioned pack with readable source pointers and unknowns. ## Worked checkpoint The pilot records yield 12/20 = 60% and 18/24 = 75% arrival proportions; the volunteer poll’s 9/15 = 60% measures a different question. Separately, the Paperlight pack can establish 30 usable chairs and a 30-person per-session limit, but cannot establish 60 distinct visitors. Keep the two fixtures separate rather than merging their facts. ## Output A bounded task brief, three-source register, disagreement map, and versioned knowledge pack with answerability tests. ## Exit checks - Every important claim has a source location or a labelled derivation - Approved, proposed, and unknown information remain distinct - Different populations and denominators are not averaged into false agreement - At least three answerable and two unanswerable questions have expectations - The pack states its audience, exclusions, and review trigger ## Decide what happens next Keep the result when the checks pass. Revise a specific failed check in a new draft, preserving the first attempt. Hold any part that needs missing evidence or authority; an honest hold can complete this learning path even though the wider real-world task remains unfinished. Do not call an authored answer key an observed result. IIEN means infer intent and extrapolate needs here: use it to notice a useful next question and label assumptions. It does not authorize new actions, expand access, or tune model weights. ## Sources and scope This is an editorial sequence of the linked existing guides. Their source sections support the individual methods; the sequence, checkpoints, and study budget are original teaching choices. This path does not claim certification, deployed capability, or measured performance improvement.