knowledge-claim-consolidation skill

Claim consolidation review

Claims pile up faster than pages are curated: knowledge_remember saves claims that name no page, and hubs collect snapshots, duplicates and claims about more specific subjects. This review files claims on their pages, retires duplicated and replaced claims, and keeps pages current.

Rules card

These hold for the whole run; keep them after compaction.

text, retiring a cited claim or dropping a page from a claim's entities, make sure the page still reaches every record it cites, and that each citation points at a current record.

1. Never lose a citation or reachable evidence. Before deleting or moving

from a complete, fresh read, and reread before each edit.

1. Read before writing. Read a record before changing it; edit a body only

record's revision and hash, and the latest expectedOntologyFingerprint from your last receipt. A row's 16-character hash prefix fences an annotate, withdraw or supersede; a body edit needs the full read.

1. Fences: every write carries a fresh requestId, expectedVaultId, the

fit its type gets fixes only: broken citations, a stale fact a newer claim contradicts. Restructuring or splitting needs a named reason in the report.

1. Leave alone by default. A page with a current State and sections that

untouched and report them. Unattended, never ask.

1. Never guess. Leave uncertain identities, duplicates and outcomes

retry under a new request ID.

1. Uncertain write: read recovery first; never

Tasks

Read setup, then call knowledgestatus and knowledgeontology. Read only the reference for the task at hand, and follow its links only when you reach that step. You don't need to reread a reference after compaction unless you are about to use it again.

linking.

• Enumerate a scope, link claims, create missing pages:

retiring.

• Retire duplicates, replaced claims and snapshot series:

to subject pages and the one layout for the page's type.

• Review a page: page review, which sends you

Scopes

Name the scope in the report and run its tasks in this order:

its subject): enumerate, move claims about a more specific subject, retire, then review the page. Move before retiring: a superseded or withdrawn claim can no longer be relinked.

• Unlinked residue (default; scribe runs): link, then retire.
• One page (a hub, an over-budget page, or a body that no longer explains

review its page if the new claims change its picture.

• One subject, optionally since a date: enumerate, link, retire, then

Verify and report

Run knowledge_verify with expectedEntities for linked claims and expectedLinks for new or edited pages (verify), then enumerate the scope again and handle or report new arrivals.

Report: scope; claims examined, linked, superseded (with the superseding claim) and withdrawn (with the survivor); pages created and why; pages reviewed with their result (no change, fixed, or restructured with its reason); dated sections and Timeline entries retired and kept; and each claim or line you left and why.

Scribe runs

The Knowledge Consolidation scribe runs unattended; its prompt handles access and the automation. Do not ask questions. Each step names its task:

empty, report zero claims examined and go on.

1. Link the unlinked residue (linking). If it is

(retiring), then check the residue again.

1. Retire duplicates and replaced claims in it

(retire a written Timeline). Find them with knowledge_grep for Timeline and confirm the heading.

1. Retire written Timelines: up to 10, largest first

(scribe page choice), whatever the residue's size.

1. Review pages: up to 5, one at a time

withdrawn and left; Timelines retired and left; pages reviewed, changed and left unchanged.

1. Report. The status line counts claims examined, linked, superseded,