Document Context case study

DOCUMENT CONTEXT / OWNED SOFTWARE DEMO

Document Context artifact inspector.

Replay a fixed conversion response, then inspect generated chunks with source hash, section path, page context, and token budget. The artifact came from a real local CLI run on a fictional source; this site is not a live converter or upload service.

Go to the demo

Generated artifact / reviewed snapshot

Follow the source into each chunk.

LOCAL CLI ARTIFACT
Explore the conversion flow

From source file to traceable context.

Walk through a reviewed local CLI result, then inspect how its manifest and chunks retain source identity.

DOCUMENT CONTEXT · SAMPLE WORKSPACECLI ARTIFACT
  1. 01Inspect sourceWAITING
  2. 02Normalize textWAITING
  3. 03Build chunksWAITING

Ready to inspect the sample output.

01 / FICTIONAL SOURCEfictional-expense-review-standard.md

Newly written Markdown fixture. The local conversion CLI used the passthrough backend with the rag profile and a 150-token estimated body budget.

SHA-25622611878d9669c399c9f64f76514448c959e947bd7a1410dc70cc874ca13f642
Inspect the sample conversion response
Request shape
POST /demo/convert · fictional-expense-review-standard.md
Response
11 chunks · passthrough backend · source hash retained
Execution
Reviewed snapshot from a local CLI run; the browser makes no conversion or API call
02 / CHUNK MANIFEST

11 generated chunks; select one of three reviewed examples.

03 / CHUNK 0002

Purpose and scope

Section path
Fictional Expense Review Standard / Purpose and scope
Source reference
page:1
Estimated body tokens
109 / 150

“Automated checks identify gaps; they do not approve or reject a claim. A reviewer may request evidence, escalate the case, or approve it after considering the complete record and writing a rationale.”

Excerpt from a generated chunk; local file paths and timestamps are intentionally omitted from this public-facing snapshot.
WHAT IS REAL

The underlying software runs locally; this inspector uses a static subset of output generated from a fictional Markdown file. PDF and Office conversion, arbitrary-document citation quality, and production security are not demonstrated here. Read the design decisions