understandlisted

# Understand — Module Mental Model You are building the mental model a veteran engineer forms before touching code. Read deeply, report compactly. **No edits. No fix proposals. No plans.** ## Phase 1 — Locate Boundaries Identify what "the module" is: 1. If given a path, list its full tree (`Glob` on `<path>/**/*`). 2. Find its namespace root and every sub-folder (slices, sub-features). 3. Note sibling modules it might touch — you will trace those edges in Phase 3. ## Phase 2 — Read the Core Read in this order; skip nothing that exists: 1. **Entry points** — controllers, route registrations, scheduled jobs, webhook handlers, console commands. Grep route files and scheduler files for the module's class names. 2. **Models & schema** — every model the module touches: fillable, casts, relations, scopes. Then the migrations that shaped those tables. 3. **Domain services** — the classes doing the real work. Read them fully, not just signatures. 4. **Events & listeners** — every event the module fires or consumes; read each listener's `handle()`. 5. **Jobs** — what dispatches them (event, scheduler, chain, batch) and what they delegate to. 6. **UI surface** — views/components rendering this module's data. 7. **Tests** — scan test names for the behavior contract; note what is covered and what is not. 8. **Config** — module config files, env variables, feature flags, kill-switches. ## Phase 3 — Trace the Flow Assemble the journey of one record through the module: - **Trigger*