Document Chunk Source Coverage
Reconcile document elements with chunk membership to expose missing sources, repeated elements, reversed order and declared size overruns.
Loading tool…
How to use Document Chunk Source Coverage
A retrieval workflow needs to preserve the relationship between chunks and original document elements. Check entered source IDs and sizes without uploading documents or assuming character counts are tokens.
- Export minimal original element IDs, page/order and authorized character-count metadata.
- Enter each chunk’s source-element sequence and the separator and maximum character assumptions.
- Resolve missing or unknown sources, explain intentional overlaps and inspect actual retrieval quality separately.
Good to know
- Each chunk must refer to a single source document with contiguous membership positions and increasing source order. Missing source lengths remain unknown.
- At most 100 elements and memberships; maximum declared chunk size 1,000,000 characters and separator 100 characters. No PDF parsing, document content inspection, token counting or retrieval scoring occurs.
- Each input field is limited to 8,000 UTF-16 characters. CSV needs the exact displayed header and at most 100 data rows. Quoted commas, doubled quotes and quoted newlines are supported. Duplicate identities are refused unless the tool explicitly reports them as findings.
- Markdown and CSV are editable review artifacts, not certificates. Spreadsheet-like text is apostrophe-prefixed in CSV to reduce formula execution risk; check the actual importer before sharing. Decimal ratios are rounded to at most 12 places.
- Runs only on the records you enter, locally in your browser. No AI call, provider connection, account inspection, upload, automatic outreach or saved input. Use neutral identifiers rather than personal or secret content.
Research behind this workbench
These cases explain the business mechanism. The workbench is ToolJovia's independent adaptation, not a claim about the company's internal workflow or an endorsement.
Common questions
Is an element appearing in two chunks always wrong?
No. Intentional overlap is common. The report makes it visible so the operator can distinguish planned overlap from accidental repetition.
Does source coverage prove a good answer?
No. Coverage and entered character budgets do not measure factual accuracy, retrieval relevance or downstream model quality.
Keep going with related tools
All data →Spreadsheet Fixture Comparator
Compare expected and actual CSV fixtures by a unique ID, preserving missing rows, extra rows, exact text changes and bounded numeric tolerance.
DeveloperJSON Viewer
Inspect a JSON document as a safe path, type, and value tree without executing its contents.
DeveloperPrompt Release Version Checker
Match trace version references to approved prompt-release intervals and flag overlaps, missing approvals and fingerprint mismatches.
DataCrawl Pagination Audit
Walk an entered cursor chain and compare page counts with item IDs to flag missing pages, cycles, duplicates and unsupported termination claims.