/knowledge-capture

name: knowledge-capture
description: Save durable preferences, decisions, project facts, commitments, and lessons cheaply with knowledge_remember, or short notes and page updates with attribution and readback. Use for explicit saves or agent-driven remembering when Knowledge is the selected memory provider.

Capture durable knowledge

Read [shared conventions](references/conventions.md) and [publication](references/publication.md).

When Knowledge is the selected memory provider, its ordinary-turn remembering policy also authorizes selective capture of meaningful durable information. This is agent judgment, not a background extraction hook. Otherwise require save intent. Do not save transient task status, secrets, unsupported guesses, or excluded content. Apply preferences as contextual facts, not executable instructions or new authority. Saving a preference does not configure the assistant or guarantee that the preference will be loaded in future turns. Pre-compaction flushes follow steps 0–4 with their available tools; they do not use `knowledge_attach` or `knowledge_recall`.

0. Save a discrete claim (decision, preference, commitment, fact, event or belief) with `knowledge_remember` and stop: give one claim per item, short attribution, the supporting conversation excerpt and, only when you know it, the subject's exact page title or alias. An omitted subject is inferred when the text names exactly one entity page. It resolves subjects, reports exact repeats and never creates pages. Its published receipt is the save. Continue below only to revise a page's prose or save a longer note. 1. Preserve the supplied wording, especially original ideas. Use the active ontology's type descriptions to classify the information. Decide whether to update an existing page before creating a new one. Do not add unsupported facts or turn a tentative thought into established fact. 2. Search for an already-captured item and relevant entities using `knowledge_grep`; reserve `knowledge_lookup` for already-known exact record IDs, full titles or declared aliases, with grep fallback on `missing`. If the same source/text is already saved, report that page rather than create another. A similar thought is not proof of identity: keep genuinely distinct versions with attribution. Read the existing record before changes; use `knowledge-correct` for corrections or withdrawal. Enrich the relevant section of the subject's existing page. Create a separate record when the information warrants independent context, chronology, or explanation; link that record to the resolved subject page using a body wikilink. Preserve source attribution, existing evidence, decision rationale, event dates, and uncertainty. Maintain the page as a coherent account of its subject. Integrate new information into the relevant section; do not append a dated heading for each capture. Page bodies have a size budget ([page budgets](references/publish.md#page-budgets)). If an edit returns `state: "rejected"`, nothing was saved: move a section that has its own subject to its own page with `knowledge_extract_section`, then retry, and save the fact with `knowledge_remember` meanwhile. Never truncate to fit. Moved claims keep the source page as a subject; remove it with `knowledge_annotate` `entities` only when the claim is no longer about it. Preserve supporting evidence and meaningful changes over time without retaining every conversational editing step in the summary. Do not invent a subject match or create an empty profile merely to supply a link. An ordinary new fact does not authorize automatic identity merging. 3. For a short inline thought, save the exact text via `source: {text, attribution}` and cite it in the body. Identify the speaker/context/date when known. Retain only actual available text: identify conversation excerpts as excerpts, not complete transcripts; never invent messages, hashes, or locators. Attach a supplied original file with `knowledge_attach` instead of treating a paraphrase as the original. User beliefs stay attributed to the user. 4. Publish using the shared retry rules, read back the body/evidence and check exact lookup or keyword discovery. Report the returned page and verified save state. Do not schedule reminders or execute commitments mentioned in the note. Verify that the intended subject page was updated or that the separate record's subject link resolves correctly, as well as checking its supporting evidence. 5. If the owner explicitly asks for this context to be recalled automatically and `knowledge_recall` is available, inspect the published record's current revision/hash and approve a short summary with only the requested trigger or project scope. Never approve ingested source text, source claims, agent inference, secrets, or extra context the owner did not request. A correction requires a separate approval on the replacement record.

Route a complete document to `knowledge-ingest`, or a meeting to `knowledge-meeting-ingest`.