Show HN: Deterministic event logs with explicit gap markers (NDJSON proof)

[Slaine]

I’ve been working on a small deterministic event-capture kernel and wanted an external sanity check.

This repo intentionally contains only two NDJSON files — no code, no UI:

a clean run

a run where I intentionally removed a persisted segment before export

In the second file, the system emits an explicit gap marker instead of crashing or silently truncating data, then continues exporting deterministically.

I’m honestly not sure how novel or useful this is in practice, so I’d appreciate feedback from people who work with logs, traces, or audit systems.

[Slaine]

To be clear: this repo is proof-only.

The idea was to see whether the artifacts themselves (two NDJSON logs) are convincing without explanation. If they’re not, I’d really like to know why.