explainmelisted

# Explainme — visual, verifiable code explanation Explain a codebase to a human as a **self-contained, interactive HTML map** compiled from a small typed JSON specification. The deterministic CLI validates every artifact before delivery and refuses to ship one that is not geometrically clean and semantically faithful — so the diagram never invents topology. Static output is the default; enable motion only for a demo or presentation. **This is a vendored + rebranded build of [Archify](https://github.com/tt-a1i/archify) (MIT).** The MIT `LICENSE`, `THIRD_PARTY_NOTICES.md`, and the upstream attribution above are kept as required. The engine (schemas, renderers, viewer, validator) is upstream's; Hydraia adds the codegraph grounding and the onboarding framing below. ## Hydraia grounding — codegraph is the topology source (read first) Do NOT hand-guess the system's structure. In Hydraia the topology comes from **codegraph** (the verified code knowledge graph), and Explainme renders it: 1. Query codegraph for the subsystem in scope — components/modules, call edges, entry points, storage/transports, blast radius (`codegraph_explore`, callers/callees/impact). That is the ground truth. 2. Author the typed IR (below) from those **verified** nodes and edges — not from a guess. When a node maps to real code, set its source-evidence (`SRC` markers) from codegraph's file:line so the diagram is click-through to the actual source. 3. **Frame it as onboarding, not decoration.** Attach up