1. Paper rubric
Fast under pressure. Works when the loop is happening now and app friction would kill usage.
- Printable one-pager.
- Checkbox gates.
- One real problem per sheet.
Mission Control›#9 Thinking & Visualization›Tools Research
A scan of practical tools, frameworks, and Dab/Hermes skill patterns that can force a thought to decompose into assumptions, primitives, evidence, causes, alternatives, and tests — rather than merely capture the same loop in prettier form.
Most thinking tools organize thought. Few enforce first-principles thinking by themselves.
The enforceable version is a gate-based workflow: no conclusion, decision, or recommendation until the thinker has written the claim, classified the thought, stripped assumptions, separated facts from interpretations, derived one level lower, generated alternatives, and picked a smallest test.
The strongest path for #9 is therefore: paper rubric + Dab/Hermes skill + optional visual tool, selected by thought type.
Fast under pressure. Works when the loop is happening now and app friction would kill usage.
Best enforcement layer. Dab can refuse premature conclusions and force the next question.
Use only when the thought benefits from external structure: arguments, causal chains, systems, or decisions.
Best for: belief debugging, controversial decisions, claim/counterclaim maps.
Kialo structures a topic as a thesis with pro/con branches. That forces reasons and objections out of the head and into a visible argument tree.
Use when the thought sounds like: “I believe X,” “Should I do Y?”, “This strategy is obviously right/wrong.”
Limit: better for debate and argument structure than private root-cause work.
Best for: explicit argument maps, writing clarity, support/objection chains.
Rationale is built around argument maps: claims, reasons, objections, and inferential support. It is useful when the question is whether a conclusion actually follows from the reasons given.
Use when: a belief feels persuasive but the reasoning chain is blurry.
Limit: less ideal for quick capture unless templates are pre-made.
Best for: causal chains, systems, constraints, strategy, theory-of-constraints style maps.
Useful when the problem is not a single decision but a system: bottlenecks, dependencies, feedback loops, and “if this changes, what follows?” reasoning.
Use when: the problem involves business systems, project architecture, or repeated operational failure.
Limit: likely too heavy for everyday personal thought loops.
Best for: choosing the right framework quickly.
Untools is a curated library of thinking frameworks. Relevant pages include First Principles, Issue Trees, Ishikawa Diagram, Iceberg Model, Abstraction Laddering, Ladder of Inference, Second-order Thinking, Decision Matrix, Inversion, OODA Loop, and Connection Circles.
Use when: deciding which thinking shape fits the problem.
Limit: framework library, not enforcement engine. Needs a rubric or Dab skill on top.
Best for: cognitive-bias checks, decision training, faulty reasoning exercises.
Clearer Thinking has free tools and mini-courses for better decisions, faulty logic, flexible thinking, and understanding irrationality. Useful as a source of exercises and bias checks.
Use when: the issue is distorted judgment rather than decomposition alone.
Limit: more educational than “force this thought into primitives now.”
Best for: argument strength, fair interpretation, disagreement habits.
Useful where first-principles thinking intersects with discourse: “what exactly is the claim?”, “what reason supports it?”, and “am I interpreting the other side fairly?”
Use when: the thought involves another person’s argument, disagreement, or persuasion.
Limit: education platform, not a personal thought-capture system.
Best for: technical issues where the temptation is to patch symptoms.
Already available in Dab/Hermes. Its core rule — “no fixes without root cause investigation first” — is the strongest existing enforcement pattern.
Use as inspiration: generalize it into “no conclusions before decomposition” for non-code thoughts.
Best for: making the behavior operational in chat, under pressure, across domains.
This would be a reusable Dab/Hermes skill triggered by “help me think through this,” “first-principles view,” “I’m looping,” or “break this down.”
Why it wins: Dab can enforce stop rules and ask the next question before offering advice.
| Thought shape | Recommended tool | Why | Enforcement gate |
|---|---|---|---|
| Belief / argument | Kialo or Rationale | Turns a belief into claims, reasons, objections, and supports. | No conclusion until each major claim has at least one reason and one objection. |
| Root-cause loop | 5 Whys, Ishikawa, Iceberg Model, issue tree via Untools | Forces movement from symptom to cause and then to hidden system conditions. | No action until the root cause is stated separately from the symptom. |
| System / feedback loop | Flying Logic, connection circles | Makes dependencies, constraints, and feedback visible. | No strategy until causal links and second-order effects are drawn. |
| Simple decision | Decision matrix, inversion, second-order thinking | Prevents “I like this” from masquerading as evaluation. | No decision until criteria, alternatives, and downside cases are explicit. |
| Repeated mental rut | Ladder of inference + assumption table | Separates observed facts from interpretations and stories. | No rehashing until assumptions are marked observed / inferred / inherited / emotional / unknown. |
| Disagreement | ThinkerU, argument map | Improves claim/reason clarity and fair interpretation. | No rebuttal until the other side’s claim is restated in a form they would accept. |
Trigger phrases: “think through this,” “first-principles view,” “I’m stuck in a loop,” “what assumptions am I making?”, “break this down,” “help me decide.”
Create a dedicated Hermes skill named first-principles-thinking that encodes the gates above. This gives Dab a repeatable protocol instead of relying on generic advice.
Run the draft rubric on one real recent decision. If it does not change the next action, tighten the gates; if it adds too much friction, reduce to a five-minute version.