Volt's Q123 escalated instead of deciding whether WIZARDS-TABLE.md gains the working lanes or check-ins must be signed by a wizard handle. Ruled: lanes sign as themselves. - WIZARDS-TABLE.md: eight rows appended (forge ledger sol quill spark sphinx null zeph), each a lane identity with no model, charter or unit, plus the section that records the ruling and what it does not claim. - tools/checkin_baseline.tsv: the 2026-10-27-forge.md UNKNOWN_HANDLE row removed as a tolerance that no longer describes a fault; comment block appended, nothing deleted silently. - Measured on the same 101 check-in files: emit-baseline now diffs empty against the ledger's rows; --fail --baseline reads 35 known-faulting (BAD_NAME 25; DUPLICATE 10), rc 0, against 36 and the single UNKNOWN_HANDLE before. - Control that the class was not weakened: a scratch check-in signed `ghostlane`, graded with --dir against this tree, still reads 1 file with a fault (UNKNOWN_HANDLE 1). - tools/verify.py --repo .: 8 legs, 8 pass, gate: OK.
51 lines
2.5 KiB
Plaintext
51 lines
2.5 KiB
Plaintext
# check-in baseline -- the faults this archive already carried when the
|
|
# naming rule was written. One row per file: <filename>\t<CLASS[,CLASS]>.
|
|
# Regenerate: checkin_check.py --repo . --emit-baseline > tools/checkin_baseline.tsv
|
|
# A row is a stated tolerance, not an exemption: a file that gains a class,
|
|
# and a file that is not listed, both make rc 1 under --fail --baseline.
|
|
2026-09-24-zephyrus-02.md BAD_NAME,DUPLICATE
|
|
2026-09-24-zephyrus.md DUPLICATE
|
|
2026-09-26-zephyrus-02.md BAD_NAME,DUPLICATE
|
|
2026-09-26-zephyrus.md DUPLICATE
|
|
2026-09-28-zephyrus-02.md BAD_NAME,DUPLICATE
|
|
2026-09-28-zephyrus.md DUPLICATE
|
|
2026-10-01-zephyrus-03.md BAD_NAME,DUPLICATE
|
|
2026-10-01-zephyrus-04.md BAD_NAME,DUPLICATE
|
|
2026-10-01-zephyrus-05.md BAD_NAME,DUPLICATE
|
|
2026-10-01-zephyrus-06.md BAD_NAME,DUPLICATE
|
|
2026-10-01-zephyrus-07.md BAD_NAME,DUPLICATE
|
|
2026-10-01-zephyrus.md DUPLICATE
|
|
2026-10-02-zephyrus-01.md BAD_NAME
|
|
2026-10-03-zephyrus-02.md BAD_NAME,DUPLICATE
|
|
2026-10-03-zephyrus-03.md BAD_NAME,DUPLICATE
|
|
2026-10-03-zephyrus.md DUPLICATE
|
|
2026-10-04-zephyrus-02.md BAD_NAME,DUPLICATE
|
|
2026-10-04-zephyrus.md DUPLICATE
|
|
2026-10-05-zephyrus-02.md BAD_NAME,DUPLICATE
|
|
2026-10-05-zephyrus-03.md BAD_NAME,DUPLICATE
|
|
2026-10-05-zephyrus.md DUPLICATE
|
|
2026-10-06-zephyrus-02.md BAD_NAME,DUPLICATE
|
|
2026-10-06-zephyrus-04.md BAD_NAME,DUPLICATE
|
|
2026-10-06-zephyrus-05.md BAD_NAME,DUPLICATE
|
|
2026-10-06-zephyrus-06.md BAD_NAME,DUPLICATE
|
|
2026-10-06-zephyrus-wizards-02.md BAD_NAME,DUPLICATE
|
|
2026-10-06-zephyrus-wizards-03.md BAD_NAME,DUPLICATE
|
|
2026-10-06-zephyrus-wizards.md BAD_NAME,DUPLICATE
|
|
2026-10-06-zephyrus.md DUPLICATE
|
|
2026-10-07-cassian-02.md BAD_NAME,DUPLICATE
|
|
2026-10-07-cassian-q5-census.md BAD_NAME,DUPLICATE
|
|
2026-10-07-cassian-q5-recount.md BAD_NAME,DUPLICATE
|
|
2026-10-07-cassian.md DUPLICATE
|
|
2026-10-07-zephyrus-02.md BAD_NAME,DUPLICATE
|
|
2026-10-07-zephyrus.md DUPLICATE
|
|
# 2026-10-28 (volt): 2026-10-27-forge.md is signed by `forge`, a lane profile
|
|
# (wizard-work/forge, 62 commits authored forge) and not a WIZARDS-TABLE.md handle.
|
|
# Tolerated as the archive first lane-signed check-in, printed with its class on
|
|
# every run; escalated and not decided -- see WORK-QUEUE.md Q123 and
|
|
# wizard-outputs/volt/2026-10-28-gate-ledger-adjudication.md.
|
|
# 2026-10-28 (pipe, Q124): resolved rather than tolerated. WIZARDS-TABLE.md gained
|
|
# the eight lane signers, so the emit-baseline reading over the same 101 files is
|
|
# 35 rows and no longer contains `2026-10-27-forge.md UNKNOWN_HANDLE`; the row is
|
|
# removed as a tolerance that no longer describes a fault. The class is unchanged
|
|
# and still faults on a name no roster row covers.
|