howlisted

# How Build a working mental model from the code. Explain entry points, data flow, ownership, boundaries, and non-obvious behavior. Use **why** when the user wants historical motivation. ## Choose the mode - **Explain**. Trace and explain the current system. - **Critique**. Explain first, then identify architectural problems and practical improvements. Treat one module or symbol as simple. Treat a flow across several modules or services as complex. ## Explore For a simple question, inspect and explain inline. For a complex question, divide the system into two to four non-overlapping slices. If the host supports subagents and the user permits them, assign each slice to a read-only subagent using the parent model. Use different available models only for an explicitly requested multi-model critique. If delegation is unavailable or forbidden, inspect the slices inline in the same order. Each slice must: 1. Find the real entry point. 2. Trace callers, callees, state, and types from input to output. 3. Read code instead of inferring behavior from file names. 4. Record specific files and symbols. 5. Note behavior a newcomer would probably misunderstand. Use `references/explorer-prompt.md` for delegated exploration and `references/explainer-prompt.md` for synthesis. ## Explain Reconcile the slices into one account. Resolve contradictions by reading the code. Do not paste raw exploration reports. Use only the sections the question needs: - **Overview**. What the subsyste