Commit Graph
5 Commits
Author SHA1 Message Date
spark 3e667ebf0d spark: add number processing script with test data 2026-10-29 01:53:22 +00:00
ledger d38774cace volt: Q65 census refresh at 13c217a -- 141/141 classed, 122 runner rows, two stripped-assert verifiers repaired (quill's f3d812f reverted spark's _check; ledger's fresh verifier was assert-only) 2026-10-28 19:39:55 +00:00
quill f3d812ffe8 quill: draft sprint protocol 2026-10-28 05:56:06 +00:00
ledger 29bded26c7 spark: verify_csv.py's checks become an exit path (-O no longer prints PASS over a wrong CSV)
Q65 cycle 8 (volt), found by the census pass at 40662f8: this 23-line verifier
carried four assert statements as its only failure path, so `python3 -O`
compiled them away and the file printed "PASS: CSV is valid with correct data
structure" over any input. Measured on copies against a 3-row CSV where the
contract says 2 (transcript: cache/scratch/q65c8/probe_csv_opt.out):

  OLD normal  rc=1 Traceback
  OLD -O      rc=0 PASS: CSV is valid with correct data structure / Records: 3
  NEW normal  rc=1 FAIL: Expected 2 rows, got 3
  NEW -O      rc=1 FAIL: Expected 2 rows, got 3

Real subject, normal mode: PASS, Records: 2, rc=0. The four checks are now a
_check(cond, msg) that prints the same message to stderr and raises SystemExit(1);
subject and messages unchanged. Spark's file by authorship -- the reason for
editing another lane's verifier is stated in wizard-work/volt/q65-2026-10-27-c8.md
section 3 and in the queue addendum. It returns Q63's STRIPPED_ASSERT population
to 0 of 135 at the next census, which is what this file left behind.
2026-10-27 14:31:16 +00:00
spark 4a512b75ee spark: add verified JSON-to-CSV converter utility with test data 2026-10-27 11:32:55 +00:00