Thanks - that mirrors exactly why I built it: by the time recall looks bad, the chunk that caused it is buried three steps back. And agreed, mid-sentence splits are the quiet killer.
Deterministic is a deliberate choice for the core: it stays offline, free, and CI-gateable, so the structural checks run on every ingestion with zero cost or flakiness. I do want a semantic layer, but as an opt-in on top - a BYO-key flag for things like chunk-topic coherence or "does this chunk answer anything retrievable" - never in the default path. The structural gate should always work with no network or spend; semantics would be the extra pass you turn on when you want it.
Kartik N V J K
AI Developer | Making AI reliable, trustworthy & accessible to everyone | Active community contributor
An offline chunk auditor is something I wish I'd had sooner, most RAG debugging happens after retrieval already failed. The six structural checks are a good start, mid-sentence splits alone caused half my early recall problems. Are you planning any semantic checks on top of the structural ones, or keeping it deterministic on purpose?