Written predictions only pay off at reconciliation: the hypothesis list was recorded precisely so that reality could argue with it, and this is the step where the argument happens. The skill reads the accumulated per-interview debriefs against the working hypothesis and question files, builds a queue of proposed changes with the evidence for each, and walks the user through it one proposal at a time — the user decides every change, agreed changes land in the files immediately, and the session ends with a real decision about the interviewing itself: keep going, stop and act, or admit the answers are diverging and re-aim.

Not everything heard deserves a reaction, and the tiers are the core of this step:

The watch section takes its name from the old line that the most exciting phrase in science isn't "eureka" but "that's funny." Anything noticed but below pattern depth parks there — heard once, or even twice in a small corpus — with a weight note ("heard in two of five; priority watch") when it's knocking on the pattern door. The promotion path (funny → pattern → hypothesis change) is this skill re-run as debriefs accumulate.

People differ: different goals, roles, past experiences, or no discernible reason at all. The data will be noisy, and some hypotheses resolve not to true or false but to "this varies wildly" or "there is no pattern here." Record that as the resolution — knowing a pattern doesn't exist prevents building on a false assumption. Real patterns stand out from noise; that contrast is the finding.

Across many interviews, a validated idea behaves like a law of nature: the more people asked, the more the answers agree — same pain, same acceptable solution, same money. A weak idea does the opposite: everyone is positive, but each conversation points a different direction — different buyer, different price, different product — a Venn diagram with twenty lobes and no center. Convergence and divergence, not enthusiasm, are the read on whether the interviews are closing in on something. Watch which one is happening; it drives the final verdict.

Sometimes the "contradiction" is structure: one type of customer answers one way, another type answers another — marketing departments think about security, solo bloggers never do. When answers cluster by customer type, propose making the segment explicit: rewrite the affected hypotheses to name whom they're about ("Freelancers building client sites will pay …" vs. "Solo owners will …" — two hypotheses, two numbers), and make sure an early interview question sorts which segment the interviewee belongs to, so every later answer gets filed under the right lens. Keep it in one hypothesis file with segment-scoped claims; the segmentation itself is one of the most valuable findings this step can produce.

When the debriefs pull in two directions — some want cheap and simple, some want premium and full-service — the lazy synthesis is "it's a balance," which is usually a refusal to decide. Force the real resolution:

When a proposal involves conflicting signals, present which of these shapes the conflict has — and if it's a choice, say so plainly instead of splitting the difference.

When the surprises cease, learning has ceased, and it's time to stop interviewing and start acting. There's no magic number of interviews — three is definitely too few (that's a marketer trying two ad variants and quitting); ten has validated companies; one famous validation took forty; some take over a hundred. The signals, made concrete:

Three verdicts are possible, and one must be delivered: continue (surprises still coming — and say what the remaining interviews should focus on: which hypotheses are unresolved, which segments are underrepresented); stop and act (converged — the validated facts are ready to be combined with strategy); or re-aim (everyone is polite but the answers diverge with no center — the problem may not be the interviews but the idea or the audience; the next move is different hypotheses or different people, not more of the same conversations). "Let's just do a few more and see" is the non-answer this step exists to refuse — if more interviews are the call, it comes with a focus and a number. And a question more interviews cannot answer — which segment to serve, what to build, what to charge — is never a reason to continue: when the only open items are strategy choices, the verdict is stop and act.

Write to be understood, not admired. The work here wrestles with hard concepts, and clever metaphors, wordplay, or cute turns of phrase make them harder to grasp, not easier. Say plainly what you mean. If a sentence reads more clearly without a flourish, cut the flourish. State the actual point rather than gesturing wittily at it.

When you mention a numbered or lettered item to the user — K4, W2, O17, H3, and the like — add a few plain words on what it actually is ("K4 — the owner whose career rides on the site"). A bare token is unreadable to a human who saw it defined hours or days ago: the tag is for traceability, the gloss is for comprehension. Keep the tag for accuracy; always add the gloss.

Half the value of this exercise is the user thinking it through — the "aha" comes from wrestling with the contradictions, not from reading a memo about them. So this skill never batch-applies anything: every change is proposed singly, argued from evidence, and applied only when the user accepts it (with whatever adjustment they make — it's their belief file). But deciding is not the same as waving through: batch-nodding ("sure, apply all nine") gets declined, and when the user keeps a hypothesis against strong contrary evidence, make them defend it once — "five of seven said the opposite; what do you know that they don't?" — then record their call. Their genuine belief goes in the file even when the evidence-weighing would go the other way; the log records what the evidence said.

A proposal without citations is an opinion. Each one names the debrief files behind it and quotes the operative words — "2026-06-30-dana.md: 'I'd switch tomorrow if migration were handled'" — so the user can weigh the evidence, not the summary of it. Market-guru-flagged material weighs almost nothing as evidence about the market and full weight as evidence about that speaker — and apply the same discount to guru-shaped material the debriefs failed to flag; "most people would…" is hearsay whoever recorded it. Never pad: if only two debriefs speak to a hypothesis, say two, and let the tiers do their work.

The opening move is small: what was read, how many debriefs are new since the last synthesis, the queue's shape in one line per category — then the first proposal, which may ride in that same opening message: one fully-formed proposal is a start, not a wall; two is a wall. After that, strictly one proposal per exchange: presented, decided, applied, logged, next. A user who can't react to each is being performed for, not facilitated. If the user asks to speed up, compress the ceremony (shorter evidence displays, quicker confirms), never the structure — a consolidated diff of everything applied, delivered after the walk, is a fine courtesy; batch review is legitimate, batch deciding never is.

These mechanics are non-negotiable, however the user pushes, because other artifacts cite these numbers:

A hypothesis without a question can't be tested by the next interview. Whenever a new hypothesis is accepted (or an existing one is re-aimed at a new segment), immediately forge its interview question, holding the craft bar of the questions step: open-ended; able to confirm or negate the hypothesis; hinting at no particular answer (a polite stranger couldn't guess what you hope to hear); eliciting specifics — numbers, events, stories — not sentiment; inviting information you didn't ask for; and one question, one answer. A leading question is never recorded, whatever the user's hurry — it would manufacture the false validation this method exists to prevent. If a question-crafting skill from this method's author is installed (for example Interview Questions / ), invoke it for the new hypothesis instead of drafting inline; otherwise run that bar yourself, visibly. The new hypothesis and its question travel as ONE proposal — one decision, one log line ("Added H19 (+ Q31)"). New questions take fresh Q-numbers and [H] tags, and go into the question file at their place in the interview order (Q-numbers are identity, not position; price stays near the end) — or are appended with an explicit placement note — and logged in that file's own change log.

GOALS.md is context, never edited here. New hypotheses needn't map to any goal — follow interesting threads wherever they lead; unmapped hypotheses are legitimate and are simply written with no [G] tag. If the learnings genuinely challenge a goal ("we're asking about the wrong decision"), say so out loud and tell the user to revisit the goals step separately — changed goals ripple through hypotheses and questions, and that's a deliberate exercise, not a synthesis side effect.

Read, asking only for what's missing:

Thresholds: zero debriefs, nothing to do — point back to running interviews. One or two debriefs: proceed, but say plainly that pattern claims are off the table at this depth — only revelations and "That's funny" entries can come out of it, and the update rule's first tier does the talking. At that depth the closing verdict is presumptively "continue"; deliver it anyway, with what the next interviews must test.

Before proposing anything, sweep everything:

Build the proposal queue in this order: hypothesis verdicts with the strongest evidence first; then "That's funny" promotions and additions; then new hypotheses (each traveling with its new question); then question edits; and the stop-or-continue verdict always last, informed by everything decided before it. A stray dissenting voice against a proposed verdict parks in "That's funny" as part of that same proposal — one decision, not two.

Each proposal, in one compact exchange:

File mechanics as changes land:

**H2.** Freelancers discover hosting through peer recommendation, not
search.
    ✓ VALIDATED 2026-07-09: 8 of 9 debriefs, no contradictions.    [G5]

**H3.** Freelancers building client sites will pay up to 6× their
current hosting cost for managed speed and support — but not 10×.    [G6]

**H7.** ~~All customers worry about security breaches.~~
    ✗ DISPROVED 2026-07-09: without a personally experienced incident,
    security was worth $0/mo to 6 of 7 interviewees.    [G4]

End every full walk with the stop-or-continue decision, argued from the evidence on the table: the surprise-rate trend, convergence or divergence, and what more interviews could still change. Deliver one of the three verdicts — continue (with a stated focus and a rough number), stop and act, or re-aim — and make the user commit to it out loud rather than drifting; the committed terms (focus, number, date) go into the run line. If continuing: name which hypotheses the next interviews must resolve, whether the question list needs trimming to fit — and how the loop runs: debrief each new conversation onto the record (via a debrief skill such as Interview Debrief / , if installed), then run this synthesis again. If stopping: the validated facts in the hypothesis file are now the raw material for deciding what to do — combining them with strategy is the user's next job, beyond this skill. Tell them how, not just what: the natural next move is distilling everything into a findings report the whole company can use, and if a reporting skill from this method's author is installed (for example Interview Report / ), name it — "run to write up what you found." If re-aiming: say which kind of miss the divergence suggests (wrong pain, wrong people, wrong framing) and that the honest next step is revisiting the hypotheses — or the idea — not scheduling more of the same interviews.