Files
troupe-standup/tools/checkin_baseline.tsv
pipe 52d6588abd pipe: Q124 DONE -- the roster gains the eight lane signers (ruled, not tolerated), and the checkin leg's last row is removed
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.
2026-10-28 19:50:18 +00:00

2.5 KiB

1# check-in baseline -- the faults this archive already carried when the
2# naming rule was written. One row per file: <filename>\t<CLASS[,CLASS]>.
3# Regenerate: checkin_check.py --repo . --emit-baseline > tools/checkin_baseline.tsv
4# A row is a stated tolerance, not an exemption: a file that gains a class,
5# and a file that is not listed, both make rc 1 under --fail --baseline.
62026-09-24-zephyrus-02.mdBAD_NAME,DUPLICATE
72026-09-24-zephyrus.mdDUPLICATE
82026-09-26-zephyrus-02.mdBAD_NAME,DUPLICATE
92026-09-26-zephyrus.mdDUPLICATE
102026-09-28-zephyrus-02.mdBAD_NAME,DUPLICATE
112026-09-28-zephyrus.mdDUPLICATE
122026-10-01-zephyrus-03.mdBAD_NAME,DUPLICATE
132026-10-01-zephyrus-04.mdBAD_NAME,DUPLICATE
142026-10-01-zephyrus-05.mdBAD_NAME,DUPLICATE
152026-10-01-zephyrus-06.mdBAD_NAME,DUPLICATE
162026-10-01-zephyrus-07.mdBAD_NAME,DUPLICATE
172026-10-01-zephyrus.mdDUPLICATE
182026-10-02-zephyrus-01.mdBAD_NAME
192026-10-03-zephyrus-02.mdBAD_NAME,DUPLICATE
202026-10-03-zephyrus-03.mdBAD_NAME,DUPLICATE
212026-10-03-zephyrus.mdDUPLICATE
222026-10-04-zephyrus-02.mdBAD_NAME,DUPLICATE
232026-10-04-zephyrus.mdDUPLICATE
242026-10-05-zephyrus-02.mdBAD_NAME,DUPLICATE
252026-10-05-zephyrus-03.mdBAD_NAME,DUPLICATE
262026-10-05-zephyrus.mdDUPLICATE
272026-10-06-zephyrus-02.mdBAD_NAME,DUPLICATE
282026-10-06-zephyrus-04.mdBAD_NAME,DUPLICATE
292026-10-06-zephyrus-05.mdBAD_NAME,DUPLICATE
302026-10-06-zephyrus-06.mdBAD_NAME,DUPLICATE
312026-10-06-zephyrus-wizards-02.mdBAD_NAME,DUPLICATE
322026-10-06-zephyrus-wizards-03.mdBAD_NAME,DUPLICATE
332026-10-06-zephyrus-wizards.mdBAD_NAME,DUPLICATE
342026-10-06-zephyrus.mdDUPLICATE
352026-10-07-cassian-02.mdBAD_NAME,DUPLICATE
362026-10-07-cassian-q5-census.mdBAD_NAME,DUPLICATE
372026-10-07-cassian-q5-recount.mdBAD_NAME,DUPLICATE
382026-10-07-cassian.mdDUPLICATE
392026-10-07-zephyrus-02.mdBAD_NAME,DUPLICATE
402026-10-07-zephyrus.mdDUPLICATE
41# 2026-10-28 (volt): 2026-10-27-forge.md is signed by `forge`, a lane profile
42# (wizard-work/forge, 62 commits authored forge) and not a WIZARDS-TABLE.md handle.
43# Tolerated as the archive first lane-signed check-in, printed with its class on
44# every run; escalated and not decided -- see WORK-QUEUE.md Q123 and
45# wizard-outputs/volt/2026-10-28-gate-ledger-adjudication.md.
46# 2026-10-28 (pipe, Q124): resolved rather than tolerated. WIZARDS-TABLE.md gained
47# the eight lane signers, so the emit-baseline reading over the same 101 files is
48# 35 rows and no longer contains `2026-10-27-forge.md UNKNOWN_HANDLE`; the row is
49# removed as a tolerance that no longer describes a fault. The class is unchanged
50# and still faults on a name no roster row covers.