Deep Understanding (Orchestrator)

Depth-first mastery of a single object the user already half-knows. The goal: they can re-derive it from memory, name every assumption it leans on, and say precisely where and why it fails. This skill routes between singletons — it does not produce the teaching, the audit, or the counterexamples itself.

Contrast with siblings:

• flow-learn-new-topic — breadth-first onboarding into an unfamiliar area. Use it when the user lacks the surrounding map.
• flow-idea-to-proof — formalizing the user's own idea. Here the object already exists and is fixed.

Before You Start: Pin the Object

Ask only what you can't infer. You need:

• The exact object — which paper / method / theorem / derivation. One thing, not a family.
• Current grasp — what they already understand vs where it goes fuzzy. Mastery is depth-first, so start at the fuzzy edge.
• The purpose — implement it, build on it, review it, or defend it in a meeting/exam. This sets how far into critique to push.

If the user names a whole area rather than one object, route to flow-learn-new-topic first.

The Pipeline