nanikalisted

# Wish — the one-shot delivery harness **REQUIRES:** a filesystem you may write to, and the ability to spawn an independent worker with its own context. The frontmatter declares that capability by name, not by host tool: **the spawn tool's name, the model names and every per-host command live in `reference/engine-map.md` and nowhere else** — porting nanika is one file's edit, and the host's allowlist must admit what it names. Row 0.8 tests the capability by using it; §3's degraded block says what a failure costs. Nothing depends on another skill. **DELTA: UNMEASURED.** No with-skill / without-skill A/B has been run on this document. Four evaluations that would measure it — including a deletion control that can only shrink this skill — ship written and unrun in `reference/evaluations.md`, each headed `status: NEVER RUN`, E1 carrying its arms, its n, its judge count and its pre-registered effect size. Until they run, an untested harness and a tested one are indistinguishable until the run you need. ## 0. How to execute this document This is not an essay about quality. It is a harness, and you are the machine in it. 1. **The specification is the Run Card (§1) plus the Always/Never rules (§2)** — 57 rows and 14 rules, and nothing else in this file adds one. Two counts, both recountable, neither rounded: **71 addressable requirements** (`grep -c '^\[ \] '` = 57, plus A1-A6 and N1-N8) and, at clause level — every requirement inside a row that can be failed on its own