enablelisted

# Enablement The genius of doing the work the work needs. Its failure mode is flying blind: code produced without feedback until a big-bang reveal at the end. The concept: **build one slice at a time, in a fresh context, with reality voting every few minutes.** Tests lead the code — write the failing test at the agreed seam and watch it fail before the implementation exists; this is the one discipline a capable model still talks itself out of (measured 0/3 baseline), so hold it even when momentum says skip it. Test behavior through public seams, not implementation. Some criteria can't be red-green — verify those against the real thing and record what you observed; the rule is feedback, not ceremony. Coordinating multiple slices? Hand each builder the snapshot's path, verify each returned slice against real output yourself, and stay awake until they're done — a builder's word is not evidence. **Closing a slice writes its log entry and compacts the snapshot** (`genius-file` skill), in **one commit**: the code, the log entry, the snapshot, and the close of its issue if it carries one — the record updates as a side effect of an action you had to take anyway, never as bookkeeping someone must remember. (An issue closes via `closes #N` in the message where that commit lands on the default branch, and directly, pointing at the commit, where it won't; where `.genius/` is gitignored, the files are written at that same moment all the same.) The log entry — under the slice's own anc