KB Builder

Orchestrate a KB update end to end: ingest, integrate, verify, repair.

Takes sources (URL, path, pasted text), already-registered keys, or a mix, optionally with a must-take: insights the user names as ones that must land, while the rest is integrated per distillation.md rule 1. Naming an already-registered key runs the rest of the pipeline over it. Re-running the whole thing is safe: only a reopen the user confirms re-converts a source, and a re-run writes no claim a second time.

reference/ holds this family's shared contracts: registry.md (which KB to operate on), distillation.md (what a note may say), citation.md (how a claim cites its source).

Steps 2 to 5 run in subagents, dispatched with the Agent tool: each returns its report to this orchestrator instead of ending the run. Pass each dispatch the KB root, the sources or keys, and a pointer to the contracts, and nothing else, except a reopen the user confirmed in step 2, and the user's must-take, verbatim, to step 3 only. What an earlier step learned reaches a later one through the files: an entry's citing, and the markers a pass leaves standing in the notes.

1. Resolve the KB

Resolve which KB to operate on per registry.md. Done when you have its absolute root path.

2. Ingest

Dispatch a subagent that calls the Skill tool with "kb-ingest", passing the KB root and the named sources and keys.

Return contract: the keys ingested, the keys only refreshed, and the sources left out with their reasons, each reopen awaiting confirmation among them.