eli5listed

# eli5 Build understanding at the lowest useful rung, then let the learner test and reconstruct the same mental model. Preserve truth: simplify structure and vocabulary, never the load-bearing mechanism. ## Path and workspace invariant Let `[skill-dir]` mean the directory containing this `SKILL.md`. Resolve every bundled `scripts/...`, `assets/...`, and `references/...` path from `[skill-dir]`. Keep the shell working directory at the user's target workspace so relative page and ledger paths bind to that workspace. Never change into `[skill-dir]` merely to run a bundled helper. ## Choose the deliverable Decide from what the reader must do after the explanation: - **Answer one fact or understand it now** → explain inline. No file and no ledger write. - **Retain, practise, revisit, or interact with one mechanism** → learning page. - **Choose among options under constraints** → decision brief. Read `references/brief.md`; audience role or age is not enough. Do not silently turn a conversational explanation into file creation or publication. When the request is ambiguous, prefer inline. Ask only when the difference changes a named decision, an external action, or the requested deliverable. ## The explanation contract > If a sentence only makes sense to someone who already knows the topic, it is not ELI5. Replace jargon until the mechanism is visible. Reintroduce real names at the next level. If level 1 intentionally bends the truth, level 3 must name the debt and give t