Reuse one collection across AI projects.
For: AI and platform engineers
Compile document collections into a versioned World before retrieval, assistants or agent workflows consume them.
Teams repeatedly clean, chunk and index the same sources for each model or application. Identity, relationships and provenance drift between projects.
- Input
- A document collection
- Action
- Compile and review once
- Output
- A portable World and retrieval projection
From five filings to one portable World.
- 01
Connect sources
- 02
Read and reconstruct
- 03
Bind identity, hold what is uncertain
- 04
Review evidence
- 05
Publish a portable World
What every project downstream inherits.
- One governed source of knowledge
- Retrieval as a World projection
- Citations back to the exact source location
- Signed portable artifacts
Check the sample
A passage inside the retrieval projection.
PART I Item 1. Business Company Background The Company designs, manufactures and markets smartphones, personal computers, tablets, wearables and accessories, and sells a variety…
One region out of the annual filing, in the shape every project downstream receives it: the passage, the page it was printed on and the box it sat in.
rag/chunks.jsonl
Locator fields from this passage’s emitted chunk
{
"chunkId": "chunk-a511a0ea39e95b6dd5872ac3ef0115f1",
"sourceId": "apple-form-10-k",
"pageNumber1": 4,
"bbox1000": [
30,
291,
971,
380
],
"evidenceId": "evidence-0dffdde3c8def7d25da7d9eb4bd303d3"
}Five public Apple filings, compiled with the TypeScript sample compiler.
WHAT TO PLAN FOR Before your first compile
A compile costs a reading pass and a review. One project over one small corpus is cheaper to do by hand.
Retrieval quality still depends on the questions asked of it; a World makes an answer traceable, not automatically better.
Nothing here replaces a source of record. A World is compiled from documents and is only as current as its last compile.
Planning a first compile? See how a design partnership works.
Next: Build on it in Resources, or the exact product contract in the documentation.