I’ve now updated this with the same two scenarios generated under a newer model (v1.2).
This repo still intentionally contains only NDJSON files — no code, no UI:
• a clean run • a run with intentional missing data
In v1.1, missing data was represented via an explicit export-time gap marker. In v1.2, the same scenario is represented structurally at the segment level, and the verifier reports partial results accordingly.
The guarantees are unchanged (deterministic ordering, tamper-evident chaining, explicit missing-data detection).
I’m still unsure how useful this is in practice compared to existing approaches, but I wanted to share the updated artifacts in case it’s of interest.