---
title: "Comment by Kartik N V J K on \"Your RAG isn't broken - your chunks are\" | Hashnode"
description: "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 sta"
url: "https://hashnode.com/posts/chunkvet-offline-rag-chunk-auditor/6a8b20612b589582c0ede147/comment/6a8c8915942fec7d35dc25ff"
---

[Discussion](https://hashnode.com/posts/chunkvet-offline-rag-chunk-auditor/6a8b20612b589582c0ede147)

Comment [Your RAG isn't broken - your chunks are](https://hashnode.com/posts/chunkvet-offline-rag-chunk-auditor/6a8b20612b589582c0ede147)

[Kartik N V J K](https://hashnode.com/@kartik-nvj)

[Aug 24](https://hashnode.com/posts/chunkvet-offline-rag-chunk-auditor/6a8b20612b589582c0ede147/comment/6a8c8915942fec7d35dc25ff)

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?

[JAY TANK](https://hashnode.com/@jaytank)

[Aug 30](https://hashnode.com/posts/chunkvet-offline-rag-chunk-auditor/6a8b20612b589582c0ede147/comment/6a8c8915942fec7d35dc25ff#reply-6a94332f5b6a8b64aaf52ac5)

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.
