knowledgizer

(Opt-in) Read one compiled source page and emit a sidecar JSON of machine-verifiable structured claims, per the claim kinds defined in config. Idempotent. Use only when the project config enables claims and the domain has data- or API-verifiable quantitative assertions. <example> Context: A config with claims.enabled is in use; user wants verifiable claims. user: "Extract checkable claims from source 26901067." assistant: "I'll dispatch claims-extractor for that id." <commentary>Structured, verifiable claim extraction is this agent.</commentary> </example>

Scan an explicit list of wiki pages and rewrite bare mentions of known entities as single-bracket markdown links to their canonical pages. Read-only on raw sources, edit-only on the wiki. Use after new source or entity pages are written. <example> Context: A new source page and several entity pages were just written. user: "Crosslink the pages we just touched." assistant: "I'll dispatch crosslinker over that explicit path list." <commentary>Linking bare mentions across a bounded page set is this agent.</commentary> </example>

Create or update ONE wiki entity page from the source documents that cite it. Idempotent — merges into an existing page rather than overwriting. Use after source-compiler returns entity lists for newly compiled sources. <example> Context: source-compiler returned that sources A and B both mention gene EGFR. user: "Update the EGFR entity page with sources A and B." assistant: "I'll dispatch entity-page-writer for kind=gene id=EGFR." <commentary>One entity, merged from its citing sources — this agent.</commentary> </example>

Compile ONE raw source document into a structured wiki source page and return the entities it found so the orchestrator can fan out to entity-page-writer. Use when ingesting a new document into a knowledgizer knowledge base. <example> Context: A new raw document has been added to the corpus. user: "Compile source 12345678 into the wiki." assistant: "I'll dispatch the source-compiler agent for id 12345678." <commentary>Single-document ingest is exactly this agent's job.</commentary> </example>

Read across source pages for a given theme and write or update a wiki theme page, surfacing agreements and contradictions. Use when the user wants a cross-document synthesis rather than a single-source page. <example> Context: The corpus has many sources touching one topic. user: "Synthesize what the corpus says about EGFR resistance." assistant: "I'll dispatch theme-synthesizer with that theme and a slug." <commentary>Cross-source synthesis with conflict-surfacing is this agent.</commentary> </example>

Stand up a new knowledgizer knowledge base by interactively building its domain config and scaffolding. Use when the user says "set up knowledgizer", "start a new knowledge base", "configure knowledgizer", "create the domain config", or is in a repo that has no knowledgizer.config.yaml yet.

Orchestrate building and maintaining a cited, cross-linked knowledge wiki from source documents. Use when the user wants to "add a source/paper/document", "ingest a batch", "rebuild the wiki", "synthesize a theme", "ask the knowledge base", or "reprocess after a template/ontology change" in a repo that has a knowledgizer.config.yaml. Dispatches the source-compiler, entity-page-writer, crosslinker, theme-synthesizer, wiki-querier, wiki-linter, and claims-extractor agents.