The knowledge layer is a self-reinforcing system. Three always-on agents -- compiler, capture, health -- keep the knowledge base structured, captured from conversations, and structurally sound without constant human curation. Provenance is tracked at five layers so nothing is ever a black box.
The core loop
Every turn of the wheel produces provenance-linked pages from files, messages, and multimodal evidence. The same conversation that answers your question can also deposit reusable knowledge back into the knowledge base.
Design principles
Knowledge is structured, not stored
Raw documents go to S3. The knowledge base is the structured layer on top -- every page is agent-written, linked, and traceable back to its sources.
Conversations are inputs, not outputs
The capture agent treats substantive ask-agent responses as candidate knowledge. The knowledge base absorbs what users learn in chat.
Provenance is non-negotiable
Five layers from page source down to paragraph-level blame. Citation tokens ({{pmid:12345678}}) give every claim a stable key across messages and pages.
Human review for risky content changes
Content-changing suggestions enter a proposal queue for human review. Low-risk structural cleanup, such as link fixes and orphan reparenting, can be written directly with revision history.
Red links are features
A [[link]] without a target is not an error -- it's a queue for the health agent. Unresolved references surface gaps in coverage.
Extraction is guided, not generic
Extraction profiles at org / project level tell the compiler what to prioritize. Surgical teams extract different entities than regulatory teams.
In this guide
Ingestion
Five pathways -- connectors, uploads, capture, manual, health maintenance.
Knowledge base compiler
Sandbox + vision-capable agent turns raw sources into structured pages with [[links]].
The graph
Page links, title aliases, parent hierarchy, backlinks -- maintained on every write.
Provenance
Five layers of attribution, from raw source down to paragraph-level edit blame.
Always-on agents
Compiler / capture / health -- three background agents keep the KB healthy.
Connector sync
OAuth, multi-stage ingestion, continuous auth health monitoring.