The frameworks built for research → decisions are the same shape as learning → exams. The mapping was implicit—this makes it explicit.
The Parallel Pipelines
| Research Pipeline | Study Pipeline |
|---|---|
| Question Generation SOP | LO decomposition |
| → Prioritized questions | → Sub-questions to hunt for |
| Research Response SOP | Textbook reading + Claude dialogue |
| → Evidence identified | → Highlights (flagging) |
| → Connection made explicit | → Processing (dialogue) |
| → Formatted output | → Scaffolding note / atomic note |
| Atomic Notes | Graduated insights |
| Confident Decision | Exam readiness |
Step-by-Step Mapping
Question Generation SOP → Pre-Reading
| SOP Step | Studying Equivalent |
|---|---|
| Step 1: State what you’re accomplishing | ”I need to understand [LO] so I can explain it on the exam” |
| Step 2: What could go wrong? | LOs already encode this—“if you can’t explain X, you’ll fail” |
| Step 3: Convert failure modes to questions | Decompose LO using Decomposing LOs with Structural Parsing |
| Step 5: Prioritize | Which sub-questions are “must answer” vs “nice to answer”? |
| Step 7: Final question list | The “Questions I’m Reading For” section of scaffolding note |
Research Response SOP → Reading + Processing
| SOP Step | Studying Equivalent |
|---|---|
| Step 1: Question understood | I know what I’m hunting for while reading |
| Step 3: Evidence identified | This is what highlighting does—flagging where answers live |
| Step 5: Connection made explicit | Claude dialogue: “I highlighted X, help me understand why it matters” |
| Step 6: Alternative perspectives | ”What would make this break? What are the edge cases?” |
| Step 7: Formatted output | Scaffolding note updated with understanding, or graduated atomic note |
Why I Didn’t See the Mapping
The SOPs captured what each framework does. They didn’t capture when to use them—the trigger conditions stayed implicit.
Question Generation SOP never said “Use this when: studying from textbooks (LOs = pre-generated questions).”
Research Response SOP never said “Highlighting on phone IS Step 3 of this.”
The Fix
When creating a framework, add a “Use When” section:
## Use When
- Researching a purchase decision
- Studying a textbook chapter (LOs = questions already generated)
- Debugging a problem at work
- Preparing for a difficult conversationThis enables pattern-matching across contexts. The framework becomes context-aware, not just process-defined.
The Deeper Issue
Having frameworks ≠ being able to apply them.
The gap between “knowledge about” and “fluency with” is the same gap as reading about opportunity cost vs. explaining it cold. Frameworks require practice—deliberately applying them to new contexts until the pattern-match becomes automatic.
This note itself is an example: making the implicit mapping explicit so it can be practiced.
North: Where this comes from
- Question Generation SOP (the research version)
- Research Response SOP (the evidence-gathering version)
- Pattern Recognition (seeing same shape in different contexts)
East: What opposes this?
- Context-Specific Tools (different tool for every situation)
- Framework Hoarding (collect frameworks, never apply)
South: Where this leads
- Five-Phase Study Workflow (the applied version)
- Framework Fluency (automatic application)
West: What’s similar?
- Transfer Learning (applying skills across domains)
- Abstraction (seeing the general pattern behind specific cases)
- Design Patterns (same solution, different contexts)