Metkagram · Pattern Routes · test-a-hypothesis
Turn a hypothesis into a test
Move from competing explanations to predictions, necessary implications, diagnostic checks and explicit revision criteria.
After this pack: Design language that makes a hypothesis inspectable instead of arguing from plausibility alone.
For: B2 · C1 · teacher · researcher · AI tutor
Route
01 · Pattern
One possibility is that [X]; another is that [Y].
Keep two plausible explanations alive before committing to one.
Open canonical object02 · Contrast
If X were true, expect Y vs For X to be true, Y must hold
Distinguish a prediction you expect from a condition the hypothesis must satisfy.
Open canonical object03 · Choice drill
For a retry to explain the duplicate, the duplicate must appear after the first failure. State that required relationship as a viability condition for the hypothesis.
Use event order as a necessary implication rather than a vague sign.
Open canonical object04 · Pattern
This explains [X], but it doesn't explain [Y].
Challenge an explanation by exposing an important observation it still fails to explain.
Open canonical object05 · Contrast
A useful test would be whether X vs I would revise Y if Z
Separate the next useful check from the evidence that would actually change your conclusion.
Open canonical object06 · Choice drill
You currently think the configuration caused the failure. State in advance what would change your mind: seeing the same failure with a clean configuration.
Finish by making the conclusion genuinely revisable.
Open canonical object
Teacher & Tutor Exports
Need to reuse this pack outside Metkagram?
Download a portable bundle with the same stable IDs and canonical links instead of copying cards by hand.