kiss-readablelisted

# KISS — Readable Code that explains itself keeps humans in the loop — they can debug and trust AI-written code without reverse-engineering it. The same structure that makes code legible makes it modular and mappable. **Write so the next reader (human or AI) never has to guess.** ## Bounded, labeled sections — one technique, three payoffs Separate each cohesive group of code with an **inert banner comment**: ``` // ───────────────────────── Recruitment ───────────────────────── ``` That one cheap line pays off three ways: 1. **Index** — the file can be scanned like a document; the section is a heading. 2. **Seam** — the section is a bounded, liftable unit. You can transplant, prune, or reuse it cleanly, because the boundary is already drawn. 3. **Firewall** — a change stays inside its section; an edit doesn't bleed into neighbors (see `kiss-blast-radius`). These banners are also what `kiss-map`'s generator harvests into `.kiss/inert.md`. Labeling a section makes it readable, liftable, *and* findable at once. ## Synopsis per non-trivial unit Above each non-trivial function/section, one line of **what it does and why** — a synopsis, the way a modular block carries a one-line description. A reader (or the map) should grasp a unit's purpose without reading its body. ``` // Promotes the tournament winner to the canonical id, carrying its persona and vault. ``` ## Why-comments, not what-comments Comment the **non-obvious**: the surprising branch, the workaround an