Knowledge Update

Revise one page in a bound knowledge base because knowledge has changed, a contradiction was reported, or a new source refines a claim. This is the manual single-page curation half of the compounding loop — the inverted pipeline adds (ingest → distill → compose → finalize), and knowledge-update refines. Together they keep a Karpathy base live.

This is the standalone analog of cogni-wiki:wiki-update, computed natively against the bound wiki — it resolves the wiki root from .cogni-knowledge/binding.json and edits the page directly with the Edit tool, so a base is curatable with no cogni-wiki plugin installed. It does not dispatch cogni-wiki:wiki-update.

Read ${CLAUDE_PLUGIN_ROOT}/references/delegation-contract.md once at the start of a session so you remember the wiki-engine boundary — cogni-knowledge curates the page natively (the update logic is pure-LLM, Edit-driven; there is no engine script to resolve), it does not delegate to cogni-wiki:wiki-update.

When to run

• User explicitly asks to update, revise, retire, or fix a page in the bound base
• knowledge-ingest-source detected that a single source collides with an existing page and handed control here for diff-before-write (the intended endpoint for that cross-skill handoff)
• knowledge-lint reported a contradiction or claim_drift the user wants reconciled
• User says "the base says X but actually Y — fix it"

Never run when