1. Why this piece exists
Three pieces in, the series has been adding: a second cognitive mode, then a knowledge graph, an institutional pathway, an evidence layer, a rarity-weighting scheme, an EBM verification burden that scales with complexity. Each addition was justified on its own terms. Taken together, they describe a system that could, in principle, out-think most single-pass answers.
Almost nobody needs all of it, most of the time. The honest failure mode of a growing framework isn't that it's wrong — it's that it becomes something people admire from a distance and never actually open. This piece is the opposite instinct: not what could the stack become, but what is the smallest, most repeatable way to actually use it, this week, on a real case, to check your own thinking rather than replace it.
2. The shift: from building the tool to using it
Where the series has been
- Which layer should I add next
- How do I weight graph vs. pathway vs. evidence
- How do I formally measure calibration across a case series
- What is the complete, validated pipeline
Where this piece starts
- What's the one question I should ask about this case, right now
- Which single module actually earns its five minutes today
- How do I know, afterward, whether the exercise changed my thinking
- How do I keep doing this often enough that it becomes a habit, not a project
Nothing below contradicts the earlier pieces. It's a different lens on the same stack: usability and habit-formation rather than architecture and validation. A tool used inconsistently at full complexity teaches less than a smaller tool used every week.
3. The minimum viable loop
Most study sessions don't need the graph, the pathway, and the evidence layer at once. They need one pass through two questions, applied to one case, in about ten minutes.
The ten-minute self-audit
- Write the one-line problem representation from memory, before looking anything up
- Name the single finding you're leaning on hardest to support your working diagnosis
- Ask: what would have to be true for that finding to point somewhere else entirely
- Check exactly one fact against a source you trust — not everything, one thing
- Write one sentence on what you'd do differently next time you see something like this
That's Promption's first module, one Provocation question, and a single spot-check — not the full pipeline, not the graph, not a rarity tier assignment. It's deliberately small enough to survive a busy week.
4. When it's actually worth reaching for more
The earlier pieces are right that heavier tooling pays off unevenly. In practice, that means most cases don't need it, and a few clearly do. A simple gut-check, not a formal tier assignment:
| Signal | What to reach for |
|---|---|
| Common presentation, textbook workup, nothing nags at you | Just the ten-minute loop above. Move on. |
| Something about the case doesn't sit right, or a number seems to fight the story | Add one Provocation pass and one fact-check against a graph or reference source — the specific thing that's bugging you, not a full audit. |
| You genuinely haven't seen a presentation like this before | Slow all the way down. This is worth the pathway, the evidence layer, and writing down your reasoning so you can revisit it later. |
The tell that you've reached for too much: you spent longer assembling ground truth than you did thinking about the patient. The tell that you've reached for too little: you can't say, out loud, what would have changed your mind.
5. Three habits that matter more than more tooling
5.1 Keep a one-line ledger, not a database
The earlier pieces propose a formal calibration ledger tracked across a matched case series. That's a research design. The usable version is a single running note: case, your initial call, what changed your mind if anything did, and whether you were right. A few dozen entries in a plain document tell you more about your own blind spots than a well-designed study you never run.
5.2 Pick one recurring question, not five new ones
Don't rotate through the whole Provocation module list every time. Pick one question that keeps catching you out — anchoring on the first diagnosis that fits, or under-weighting a lab value that doesn't match the story — and ask it on purpose, every case, until it stops being useful. Then pick a different one.
5.3 Let disagreement be the point, not the failure
If your gut read and a quick fact-check land in different places, that's the exercise working, not a sign you did something wrong. Write down both, and why they diverged, instead of quietly picking the one that sounds more confident.
6. What this piece is not saying
This isn't an argument against the graph, the pathway, the evidence layer, or the rarity-weighted deployment logic described earlier in the series — those remain the right answer for the cases that need them, and for anyone building or validating the system itself. It's a reminder that the entry point to the whole stack should be small, repeatable, and honest about what a single ten-minute pass can and can't tell you. The uncertainty that no layer can close — how the patient actually looked, what was tried and failed at the bedside — isn't solved by more tooling either. It's solved by staying close to the case, which a heavy pipeline can just as easily distract from as support.