Concepts

Sources, Compiled Worlds, candidate and active versions, and evidence.

Sources

A source is an immutable document version. Uploading the same file twice produces two documents with two source records that share one content digest; nothing merges them, each citation names one of the documents carrying those bytes, and editing the file produces a second version without rewriting the first.

Compiled Worlds

A Compiled World is what a set of sources compiles into: semantic objects, relations between them, and the evidence each one rests on. It is addressed by a collection id and a manifest digest, and the digest is computed over the whole artifact, so two Worlds with the same digest are the same World.

Candidate and active versions

A candidate version is a compile result nobody has accepted yet. An active version is the one answers are served from. Activation is an explicit human action in a signed-in session — no API key can activate a candidate, and no compile activates itself.

Evidence

Evidence is a page and a region on that page, bound to a source version by digest. An object with no evidence is not published, and an answer that cannot cite one abstains rather than guessing.

Objects, and what an Object is not

An Object is one thing the compiler found in your sources — a policy, an obligation, a party, a figure — with a stable key derived from its content rather than from where it appeared, and with the evidence it rests on underneath it. The key is what a later compile of the same content resolves to, which is why an object id is worth storing. What the key does not do is reach across separate compiles: two parts of one run compile to two Worlds, and deciding that an entity in one and an entity in the other are the same thing is identity resolution with its own evidence requirements. Nothing here does that on your behalf, and joining them without it would manufacture duplicates.

Activation, and the World Gate

Activation is the act of making a candidate version the active one. It happens in a signed-in browser session, by a person holding the workspace owner or admin role, and there is no scope that grants it — you will not find one in the scope table, because none exists. The World Gate is the filter every retrieved region passes before it can reach an answer: it admits a region only if the region belongs to your tenant, belongs to the active World version, and is bound to evidence. A region that fails any of the three is reported in retrieval.gateRejections with its reason rather than quietly dropped.

Manifest digest, lens, ContextPacket

A manifest digest is the sha256 over the whole compiled artifact, written sha256: followed by 64 hex characters. It is the version identifier: two Worlds with the same digest are the same World, and a digest is what you pass to read a specific version or to ask whether the copy you hold is still current. A lens is one slice of the World read model — objects, relations, evidence, history, files or review — readable on its own so a consumer that needs one does not fetch the whole graph. A ContextPacket is what retrieval returns: the evidence-bound regions it selected, each with its source version, page and region, plus the ranks and the reranker score that put it there. It is the same runtime contract Ask, Search, the MCP server and the CLI all share, which is why an answer and a search result cite the same way.

Ontology output

The Ontology output is the RDF and JSON-LD projection of a compiled World, shipped in the signed package as ontology/knowledge.ttl and ontology/knowledge.jsonld. It is a projection of the objects and relations that were compiled, not a hand-authored schema: a predicate is in it because an engine emitted it, and predicates the vocabulary could express and no engine emits are published as absent, so a query for one returns empty rather than wrong.

The life of a Compiled World

What each identifier changes with