# Explain

Explain the requested code, behavior, architecture, or concept using the actual project as context.

## Instructions

- Inspect the relevant code before explaining it.
- Start with the highest-level purpose.
- Trace the relevant flow or relationships.
- Reference concrete files, functions, classes, modules, or commands where useful.
- Explain important design decisions and dependencies.
- Distinguish clearly between observed behavior and inference.
- Do not propose changes unless explicitly asked.
- Prefer a concise explanation first, followed by deeper detail when useful.