explain_codebaselisted

# explain_codebase A codebase explanation is different from a concept explanation — you're mapping a specific system, not explaining an idea. The goal is to give the listener a mental map: where things live, how they connect, and what each part is responsible for. ## Step 1: Read Before You Explain Don't explain from memory or guesswork. Before producing an explanation: 1. Read the top-level directory structure. 2. Read the `README`, `CLAUDE.md`, or `docs/` folder if present. 3. Read the entry point(s): `main.py`, `main.rs`, `index.ts`, `App.tsx`, `manage.py`, etc. 4. Identify the major modules/packages and read at least the top of each. 5. Find the data models — they're the skeleton around which everything else is organized. Only after this reading should you start explaining. ## Step 2: Start with the 10,000-Foot View Begin with what the system does and what its major components are — before getting into any detail: > "This is a Django application for managing e-commerce orders. It follows Clean Architecture, so the code is split into four layers: domain (business logic), application (use cases), infrastructure (database/external services), and interfaces (HTTP API). The Rust binary in `src-tauri/` is a Tauri desktop wrapper around the web frontend." This gives the listener a frame. Everything else hangs off this frame. ## Step 3: Map the Directory Structure Walk through the top-level structure, explaining the purpose of each major folder. Be specific — don't jus