node_sync_harvest.jsonl ended with 12 rows that are not capture data:
appended ~21 hours before the record preceding them, the only rows in the
file carrying a UTC offset, and holding two distinct
(power_w, gpu_temp_c) pairs between them -- (0.0, 80.0) and (400.0, 40.0).
They survived the 2026-08-03 rebuild because that release restored all 20
rows the old pipeline's tail-trim heuristic had removed. The heuristic
fired for the wrong reason -- on its own corrupted all-zero output -- but
it was not wrong that some tail rows are synthetic. Restoring all 20
over-corrected. beads sv-l43 flagged these in July as placeholders that
teach the SNN an idle pattern that never occurred.
No gate caught it. The fabrication check looks for uniform spacing, and
12 rows in 120,334 move no distribution-based test. The pipeline now
quarantines a short out-of-order run at the end of a file and fails the
build on any time reversal it did not quarantine. The trigger is the
ordering break, not the constant …
Restores the 934,287 records that prior revisions advertised but did not
contain, and adds chain attribution the old pipeline had discarded.
neuromorphic_data.jsonl 813,973 identical {"telemetry":{}} -> 813,973 rows, 12 sensor columns
node_sync_harvest.jsonl 120,314 rows, every numeric 0.0 -> 120,334 rows, real values
Both were rebuilt from the pre-cleaning originals (395 MB / 57 MB) through
rmems/spikenaut-telemetry-etl, which gates every release on: no constant
or all-null columns, a minimum distinct-row ratio, bounded row-count
drift, non-fabricated timestamps, and an exact schema match. Round-trip
verified against the originals, zero mismatches.
Also in this release:
- Real timestamps restored. The prior script overwrote 114,250 of them
with a generated 10s ramp because its ISO-8601 check tested for a
literal "T" while the source used a space separator. The mining window
is 2026-03-19 11:55 -> 03-20 14:05, not the advertised span through
April 2, which never …
Flatten nested JSONL objects for HF Dataset Viewer compatibility
