Commit graph

2 commits

Author SHA1 Message Date
trvon
7c1a7fc1c1
Bound finding size and say why a store write is refused
Some checks failed
Build and Test / build (debug, clang) (push) Has been cancelled
Build and Test / build (debug, gcc) (push) Has been cancelled
Build and Test / build (release, clang) (push) Has been cancelled
Build and Test / build (release, gcc) (push) Has been cancelled
Build and Test / docker (push) Has been cancelled
Found by the KPI detect phase (2-3 persist failures per run):
- a finding for one rule across thousands of processes listed every
  related id and outgrew the 256 KiB block limit, so the correlation
  commit was refused; related lists are now capped at 200 (the most
  recent indicators) with the totals in metadata
- a single record up to the 1 MiB record limit may now form a block on
  its own (the decoder bound only loosens)
- a refused append records its reason ("rejected: ...") instead of
  logging an empty error
- the Database no longer logs every indicator, node, edge and finding it
  stores (175k lines in a 4-minute run); failures are still logged

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-26 06:43:46 -06:00
trvon
adb40e5b62
Add compressed event store
zstd block codec (CRC32C, varint tagged records), segment files with
sealed footers and block index, crash-atomic MANIFEST, LogStore
(lock, recovery, rolls, orphaning, heal with backoff), the evidence
view, and the legacy unqlite store kept for import. Property tests
under injected faults and crashes, a differential test against the old
store, and fuzz targets for every decoder.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-25 18:17:17 -06:00