Module 4 · Lesson 4.4

Synthesis: from findings to a usable output.

Synthesis turns a triangulated set of claims into a document a reader can use. You will write the synthesis plan, hand the prose-craft to the agent, and learn to catch the three failure modes — false voice, fact-free connector, single-source-as-consensus — that decide whether a brief is honest or merely smooth.

Stage 1 of 3

Read & Understand

5 concept blocks

What synthesis is, and what it is not CORE

By this point in Module 4 you have a scoping brief, a set of triangulated claims, and a list of opened-and-confirmed sources. You have the raw material of a research output. What you do not yet have is a research output.

Synthesis is the move that turns a set of triangulated claims into a single document a human reader can use. It has three jobs:

Shape. Decide what order the reader needs the information in. Research is not consumed in the order you found it. The shape of a good brief reflects the reader’s path through the question, not the researcher’s path through the sources.

Selection. Decide what goes in and what stays out. A triangulated set of claims is almost always too much material for the brief. Synthesis picks the load-bearing claims and discards or compresses the rest. A brief that includes every claim you found is a brief that has skipped selection.

Connection. Write the sentences between the claims. This is the prose-craft part of synthesis — the connector sentences, the transitions, the topic sentences, the conclusion. This is also where the most honesty-at-risk happens, because connector prose is exactly where a model’s pull toward confident-sounding writing can smuggle in claims that no source supports.

Synthesis is not summarization. A summary says: “Here are the things I found.” Synthesis says: “Here is the answer to your question, supported by what I found, shaped for the reader you named, with the uncertainty left where it actually lives.” The difference is whether the output is organized around the sources or around the question.

Students routinely ask a research agent to “write up the findings.” The output looks like a research brief and is usually a summary in brief’s clothing — ordered by what the agent retrieved, not by what the reader needs. Synthesis starts from the other direction: from the reader’s question, down into the claims, with the sources as footnote rather than structure.

The three failure modes of synthesis CORE

Before you write a synthesis plan, know what the three common failures look like. You will see all three in your own work and in agent output. Catching them is part of the craft.

1. The false-voice problem. The agent smooths disagreement into confident prose. A set of sources where two studies find an effect and one finds no effect becomes: “Research suggests the effect is modest but real.” That sentence contains a judgment the sources did not collectively make. It sounds authoritative, it is comfortable to read, and it is lying a little bit. The fix: in the synthesis, name the disagreement (“Two recent studies report a modest effect; a third, controlling for district size, does not”). Let the reader feel the real state of knowledge.

2. The fact-free connector. The agent writes a paragraph that is mostly transitional sentences — “This is important because…”, “In light of these findings…”, “It is worth noting that…” — and almost no sourced claims. These paragraphs read smoothly. They say nothing. The fix: every paragraph must carry at least one sourced claim. Connector prose earns its keep by moving between claims, not by filling space.

3. The single-source paragraph passed off as consensus. A paragraph is built on one source, but its phrasing suggests broad agreement. “Experts agree that X,” when the “experts” are one person in one paper. The fix: where a claim rests on one source, name the source inline (“Thompson (2024) argues that X”) rather than using anonymous plural voice.

Each of these is fixable once you see it. The skill is seeing it. Read your own drafts and the agent’s drafts with these three failure modes in mind.

The synthesis plan CORE

You do not hand the agent a pile of source notes and ask for a brief. You hand the agent a synthesis plan, and ask it to draft the brief against the plan.

A synthesis plan is a one-page outline with six parts.

1. The question, copied from your scoping brief.

2. The thesis sentence. One sentence that gives the answer. Not the topic sentence — the answer. “Beast Academy fits our family better than Singapore Math at the 4th-grade level, but the case flips at 7th grade; we should use different curricula for the two students.” Write this before you write the brief. If you cannot write it, your triangulation did not produce a verdict, and you need either more evidence or a narrower question.

3. The structure, as a list of section headings (or paragraph-topic sentences). For a 1,000–2,000 word synthesis brief, this is usually three to six sections, each tied to a sub-question of your main question.

4. The evidence map. Under each section, list the two to four sourced claims that will appear there, with a source tag for each. “Section 2 — Scope and Sequence. Claim 2a: Beast Academy’s published scope-and-sequence covers the 4th-grade CCSS topics but leaves gaps at 7th grade [source: Beast Academy publisher page, primary]. Claim 2b: parent reviews corroborate…” This is where the brief’s integrity is built. If a section has no sourced claims under it, that section will become fact-free connector prose.

5. The uncertainty ledger. A short list of things we are not confident about — disagreements between sources, single-source claims, areas the triangulation left open. These do not get papered over. They get named in the brief, usually near where the relevant claim appears. Most briefs need at least one; none should have more than three or four before the author asks whether the question can actually be answered.

6. What the reader does next. One to three sentences naming the decision or action the brief enables. If the brief is for a term paper, this is the role this material plays in the paper. If the brief is for a decision, it is the decision being made and the recommended direction.

The synthesis plan is what you hand the agent. The brief is what the agent drafts against the plan. You write the plan; the agent writes the prose; you read the prose line by line.

Holding uncertainty in the text CORE

A real research brief has uncertainty in it. The question is where the uncertainty lives.

Hedged postscript (wrong): a brief that states claims confidently throughout, then adds a paragraph at the end: “Of course, there are limitations to this analysis, including…” This is a fig leaf. Readers remember the confident prose, not the postscript.

In the text, near the claim (right): the uncertainty appears where the claim appears. “Thompson (2024) reports a modest negative effect; Garcia & Lee (2024) report no effect. The methodological difference is that Thompson controlled for household income and Garcia & Lee did not. For our purposes, we should treat the evidence as suggestive but contested.” A reader who reads only that paragraph still gets the honest picture.

The confidence-tier vocabulary from Lesson 4.3 helps. Low / medium / high confidence is a short, honest way to mark claims without sounding stilted. A synthesis brief with three or four claims marked with explicit confidence is more trustworthy than one that pretends to uniform certainty, and it is easier to read than one that sounds anxious throughout.

One useful move: write the brief twice if you are on the borderline. First, write it as if every claim were certain — to see what your most confident possible brief looks like. Then, revise to insert the uncertainty exactly where it lives. The gap between those two drafts is what your synthesis plan’s uncertainty ledger was for.

What research agents do well in synthesis, and what they do not CORE

An honest map, because a student who misunderstands this wastes effort.

Well: drafting prose from a synthesis plan. Given a good plan with source tags, the agent produces a readable first draft of a brief faster than a human would, and usually with better paragraph-level structure. Use the agent for this. Do not draft prose from scratch — it is not where your time should go.

Well: catching inconsistencies between your plan and your draft. “You said the thesis is X; paragraph 4 argues toward Y.” A good prompt to run on a draft: “Compare the thesis sentence of this brief to the actual argumentative direction of the body. Flag any paragraphs that drift from the thesis.” The agent is good at this.

Well: generating alternative phrasings, titles, and section headings. Low-stakes, easy to reject, useful when you are stuck on how to name something.

Poorly: holding uncertainty. Agents pull toward confident prose. You will have to re-insert the uncertainty in every draft, in multiple places. This is the single biggest synthesis workload that stays with you.

Poorly: the thesis. The thesis is the verdict you reached from your triangulation. The agent does not have the verdict — you do. If you ask the agent to “write the thesis,” you get a bland thesis that is technically supported by the sources and does not actually say anything. Write your own thesis.

Poorly: the uncertainty ledger. The agent will under-report uncertainty by default. You must push back explicitly — “list every claim in this brief that rests on a single source” — and re-insert.

The pattern: the agent is strong on prose-craft and weak on what is being said. That is most of the reason you still write the plan.

Stage 2 of 3

Try & Build

1 recipe + activity

Running a plan-based synthesis session RECIPE

Tool Claude desktop app — Cowork tab (primary). Optional advanced: Claude Code CLI.
Last verified 2026-04-17
Next review 2026-07-17
OSes macOS, Windows

The recipe shape is the same across both interfaces; only the surface differs.

In the Cowork tab

  1. Open a fresh Cowork task (not the scoping session, not the retrieval session). Title it: “Synthesis draft — [topic].”
  2. Paste your synthesis plan as the first message. Add one sentence at the top: “This is the synthesis plan. Draft the brief against it. Do not add claims that are not in the plan's evidence map.”
  3. Read the draft. Run two check prompts:
    List every claim in this draft that rests on a single source.
    Flag any claim that is not tagged to a specific source from the evidence map.
    Compare the thesis sentence to the argumentative direction of
    each paragraph. Flag any drift.
  4. Apply the fixes yourself. Do not ask the agent to “clean up” in one pass — you want to see each edit.
  5. Save the revised brief as capstone-entry-3-draft.md in your topic folder.
Optional advanced — In the Claude Code CLI. Same shape, terminal interface. Click to expand if you set up the CLI in Lesson 2.4.
  1. From your topic folder, launch the CLI. Confirm web tools still available.
  2. Paste the synthesis plan or reference the file:
    Read synthesis-plan.md. Draft the brief against it into
    capstone-entry-3-draft.md. Do not add claims not in the plan's evidence map.
  3. Open the draft. Run the two check prompts above against the file.
  4. Apply the fixes in the editor. Commit to git if you are using version control — the commit log is useful later when you freeze the capstone.

Safe default

The draft is not done when it sounds right. It is done when every paragraph has at least one sourced claim, the thesis and the body argue toward the same place, and the uncertainty from your plan’s uncertainty ledger appears in the brief near the relevant claims, not only at the end.

Try it — Synthesis plan + first draft CORE

worksheet deliverable · open the printable worksheet →

  1. Write the synthesis plan for your own Module 4 topic. Six parts. One page. Yourself — no agent drafting.
  2. Run the plan past the agent as a critic, the same way you ran the scoping brief past a critic in Lesson 4.2. Ask the agent to flag missing source tags, weak thesis, or implicit drift between the thesis and the evidence map. Apply the edits you agree with.
  3. Run the plan-based synthesis recipe above. Generate a first draft of the brief against the plan. Target length: 1,000–1,500 words.
  4. Read the first draft with the three synthesis failure modes in mind. For each failure you find, note the sentence and the fix.
  5. Apply the fixes. Save the revised brief as capstone-entry-3-draft.md in your topic folder.

Deliverable. A first draft of your synthesis brief — capstone entry 3 — with your fixes applied, saved in your topic folder. Not yet frozen; Lesson 4.5 will polish it before the capstone freeze.

Done with the hands-on?

When the recipe steps and any activity above are complete, mark this stage to unlock the assessment, reflection, and project checkpoint.

Stage 3 of 3

Check & Reflect

key concepts, quiz, reflection, checkpoint, instructor note

Quick check

Five questions. Tap a question to reveal the answer and the reasoning.

Q1. Which of the following best distinguishes synthesis from summarization?
  • A Synthesis is longer.
  • B Synthesis is organized around the reader’s question; summarization is organized around the sources.
  • C Synthesis uses footnotes; summarization does not.
  • D Synthesis is AI-generated; summarization is human-written.
Show explanation

Answer: B. The key difference is organizing principle. Summarization walks the reader through what was found, roughly in the order it was found. Synthesis reorganizes the same raw material around the reader’s question, with the sources supporting rather than structuring. A is incidental. C and D are not the defining lines.

Q2. A student drafts a brief whose thesis is “Beast Academy is better for our 4th-grader.” Paragraph 3 of the brief argues mainly about 7th-grade content. What is the issue, in synthesis terms?
  • A Off-topic content; delete paragraph 3.
  • B Thesis drift — the paragraph argues toward a different conclusion than the thesis claims. Either revise the thesis to acknowledge both grade levels or move the 7th-grade content out.
  • C The paragraph is too long.
  • D The brief needs more paragraphs.
Show explanation

Answer: B. This is the drift failure. The thesis defines the argumentative direction of the brief, and every paragraph should move toward it. Paragraph 3 is not off-topic in the sense of being about something unrelated — it is on-topic but arguing toward a thesis the brief has not stated. The fix is to widen the thesis (if both grade levels are actually being covered) or to drop the paragraph (if the brief is really only about 4th grade). A is a possible fix but hides what is happening. C and D are unrelated.

Q3. “Of course, there are limitations to this analysis, including X, Y, and Z.” This sentence appears at the end of the brief, after the body argues confidently throughout. What is the issue?
  • A The hedged postscript. Uncertainty belongs near the claim it qualifies, not in a footer; readers remember the confident body.
  • B The sentence is too short.
  • C The sentence should be in italics.
  • D There is no issue; this is good practice.
Show explanation

Answer: A. This is the most common synthesis-integrity failure and the one that hurts readers most, because confident prose in the body is what readers take away while the postscript vanishes. The fix is to move each piece of uncertainty to the paragraph it qualifies, even if that costs some smoothness. D is the easy but wrong answer — hedged postscripts are common but are not good practice.

Q4. Which of the following is the agent’s strongest contribution in synthesis?
  • A Choosing the thesis.
  • B Holding uncertainty.
  • C Drafting prose from a synthesis plan the student has written.
  • D Deciding what is out of scope.
Show explanation

Answer: C. Given a good plan with source tags, the agent produces a readable first draft of prose faster than the student would and usually with better paragraph-level structure. This is where the leverage is. A, B, and D are all moves the agent does poorly — it generates bland theses, under-reports uncertainty, and does not know what is out of scope because that lives in the scoping brief, not the source pile.

Q5. A student’s synthesis plan has an uncertainty ledger with no entries. What is the most likely explanation?
  • A The research is complete and no uncertainty remains.
  • B The student has skipped naming the uncertainty their triangulation actually surfaced — the brief will almost certainly show false voice.
  • C The topic has no uncertainty, which is rare but possible.
  • D The student has more sources than needed.
Show explanation

Answer: B. In real research an empty uncertainty ledger is a warning sign, not a sign of thoroughness. Almost every non-trivial research question surfaces at least one place where sources disagree, one load-bearing claim on a single source, or one area the triangulation could not resolve. A plan with no uncertainties has usually elided them, and the brief written against that plan will carry the false-voice failure mode into the text. A and C are possible in tightly-bounded questions but uncommon. D is unrelated.

Reflection prompt

Where does the real uncertainty live in your draft — and is it visible?

In 6–8 sentences: Read your own first draft of the synthesis brief with a reader’s eye. Where in the brief does the real uncertainty in your topic live — and is it visible in the text, or has it been smoothed into confident-sounding prose? If you had a reader who was going to act on this brief — the parent, the teacher, the client from your scoping brief — would they know what you are most sure of and what is still unresolved? What would have to change in the brief for them to know?

The question is not whether the brief is polished. It is whether the brief is honest about what you know and do not know. Synthesis is where that honesty most often slips, and this reflection is where you catch the slip before Lesson 4.5.

Project checkpoint

Five files in your Module 4 topic folder.

You now have:

  1. capstone-entry-1-draft.md — scoping brief.
  2. capstone-entry-2-draft.md — fact-check memo.
  3. capstone-entry-3-draft.md — synthesis brief, first draft with your fixes applied.
  4. source-list.md — every source that appears in entries 2 and 3 marked opened-and-confirmed.
  5. synthesis-plan.md — the plan you wrote and the agent drafted against.

Bring all five into Lesson 4.5. That lesson is the polish-and-freeze session — not new writing, but the final pass before the capstone artifact is fixed for the course.

Next in Module 4

Lesson 4.5 — Shipping research outputs (capstone freeze).

The polish pass and the freeze pass. You will run the final open-before-cite audit on every source, ship the capstone artifact research-brief-log-v1.md, and learn how the Recipe Book’s quarterly refresh keeps your work alive.

Continue to Lesson 4.5 →