consolidate

consolidate — promote raw captures into the durable wiki ("compile the notes")

A second brain accretes raw capture fast (meetings, daily logs, transcripts) but the higher-order pages — the person, the topic, the project — lag behind: a name gets mentioned ten times and still has no page, a topic page goes stale while fresher notes discuss it. This skill is the "compile" half of the Karpathy LLM-Wiki discipline (see ADR 0033): on demand, it promotes the substance of raw captures into the entity/topic pages and weaves the backlinks, so the wiki (and the RAG's neighbourhood signal) stays current.

Principle

One promise: turn what raw captures already say into durable, well-linked pages — proposed first, written only on yes.

• 🔴 Nearly every gesture here is a genuine question, and that is the right tier (ADR 0043). Creating a page decides how the vault will name a person or a subject from then on, and every later resolution resolves against it; a contradiction between a note and a page is never settled by the brain. A 🔴 is not a failure of the doctrine. What this skill changes is not whether it asks but how often: one message for the whole batch, and each question saying what is at stake before it lists the options. The one 🟡 here is saying what was left for later — a fact, not a request.
• Detection is deterministic (ADR 0009): a pure scanner lists exactly what needs consolidating.
• The merge is judgment (LLM): parallel read-only sub-agents draft each page, never the main context (the sync-sources fan-out/fan-in shape, to avoid context rot).
• The write is deterministic and confirmed (reuse Track B / /file-back): a new page goes through the builder (conformant by construction, refuses to overwrite); a living page gets a confirmed dated append. So consolidation never re-introduces the defects /lint reports.
• Contradictions are flagged, never adjudicated silently (Track D): when a fresher capture CONFLICTS with a fact the page already states (not merely adds to it), the draft surfaces it as a ### contradictions entry and the human decides which truth stands. Consolidation folds in additively; it never overwrites a stated fact to resolve a conflict on its own.
• Bounded, resumable (stateless), honest: a capture is a candidate purely because it is fresher than the page it feeds (or that page doesn't exist). Refresh a page and its updated: moves past the capture, so the candidate drops off on its own — no state file, nothing to seed or corrupt.