From source files
to a versioned World.
Follow what happens to a document, and what your AI receives at the other end.
- Source fileVersioned input
Bring your sources
Choose files or connect a supported system. Every accepted source receives a version and a rights boundary.
Supported sources - Accepted sourceText + page + region
Read the document
Sanitize to PDF and read text with page coordinates. Reading uncertainty stays with the result; the supported-format manifest defines what is recovered.
Document reading - Extracted passageSource-bound record
Bind the evidence
A passage keeps the exact source version, excerpt, page and region. You can open the place it came from.
Inspect the evidence - Compiled candidateReviewed version
Review a World
The compile produces a candidate. Review state and unresolved material remain visible; a candidate and the active version are separate.
The World artifact - Active WorldAPI · MCP · export
Connect your AI
Read the active World through API or MCP, or request a signed portable package. Retrieval keeps the same evidence references.
Connect your stack - Changed sourcesNext candidate + change record
Compile the next version
New sources create a new snapshot to compare and review. The public example uses full-corpus compiles; the selective-rebuild contract states its current implementation boundary.
Recompilation contract
Own-source processing follows the current access, rights and release conditions. This process diagram describes the product path; it is not a customer run receipt.
See the product and its outputsRead the version contractRead the Knowledge Compiler category guide