Pinky MMMM: the rig vault + the §0 byte-exactness fold #131
Loading…
Reference in a new issue
No description provided.
Delete branch "oss-oo/pinky-mmmm-rigvault"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
M1 — the rig vault:
tests/rigs/is the committed home for the lane's empirical rigs — the law (rounds commit their rigs, validators re-run before rebuilding, a rig never touches the live station or owner apps), the inherited rig laws (hermetic env pins, port distance, cockpit rule, CDP discipline), and the first specimen: the LLLL idle-fleet CDP rig (16 legs, firing and non-firing with equal discipline) ported from the validator's run-5 official rig as a self-locating runnable driver (make rig-llll-idlefleet; suite opt-inZDO_RIG_VAULT_E2E=1, skips gracefully). Suite shape legs intests/test_round_mmmm.py(22 legs).M2 — the §0 byte-exactness fold (LLLL validator F-1): every §0 SHARED PREDICATE citation surface (
observatory.py,dashboard.html, the test pin) now carries A⁵'s frozen German Koord-Schluss form byte-exact (6 lines); the English explanation lives beside, never inside, the citation; two independent frozen copies in the test guard against silent citation drift.Evidence: direct rig run 16/16 (fire 65.6 s, re-arm 84.1 s); opt-in E2E suite leg OK (296.5 s); canonical suite 1687 tests with only the expected pre-tag version-guard tie.