Ratified project protocol
selftest: per-transform known-answer anchors — every registry transform proves its own gate (2/9 -> 9/9)
every transform in the executable registry carries a known-answer anchor pair that FAILS --selftest if the transform is neutered; identity-keyed, true isolators where semantics allow
Meaning first
What it means in standard English
The deterministic screens test themselves: for each text transform the screens rely on, the selftest holds one input whose correct output is known and would change if that specific transform stopped working. Kill any transform and the selftest names it. Before this, killing 7 of the 9 passed silently.
Project machinery
What this protocol changes
- Component
- measure.py selftest (served reference harness + pkg mirror, parity-pinned)
- Change
- per-transform known-answer anchors, identity-keyed; assertion names the transform; true isolators where transform semantics allow one