Curiosity Rule
The discipline of never accepting AI output without asking why it was built that way — treating AI as a mentor that pushes back rather than a vending machine that delivers. One of the three mindset pillars in the Three Ms Of AI framework.
Key points
- Accept → understand → improve: every AI output is a learning opportunity, not just a deliverable [src-013]
- "Vending machines take a coin and give you something. But mentors ask you questions. They push you back. They make you sharper." [src-013]
- Applied to skill building: after a skill runs, ask why it made the choices it did — then update the skill's guardrails [src-013]
- Applied to context: regularly audit what the AIOS knows and correct its assumptions [src-013]
Related concepts
- Three Ms Of AI — parent framework
- Default Shift Habit — first habit
- Function Breakdown Habit — second habit
- Skill Feedback Cycle — the operational application of the curiosity rule to skill improvement
Source references
- [src-013] Nate Herk — "Build & Sell Claude Code Operating Systems (2+ Hour Course)" (2026-05-01)
Recommended next
Keep reading from this thread
From 500 indexed pages and articles.
- Wiki concept Three M’s of AI Three M's of AI Nate Herk's philosophical framework for adopting AI productively — Mindset, Method, and Machine — presented as the prerequisite to building a technical Related by curiosity
- Wiki concept Default Shift Habit The practice of reflexively asking "how could AI do 30%+ of this?" before starting any task — replacing the human default of doing Related by 013
- Wiki concept Function Breakdown Habit The practice of decomposing any role, project, or workflow into its smallest atomic tasks before evaluating automation potential. Related by 013