KB Compile

Incrementally turn immutable raw captures into reviewable draft knowledge.

Read before compiling

Read these files first:

• local AGENTS.md
• local CLAUDE.md if present
• ../obsidian-notes-karpathy/scripts/skill-contract-registry.json
• ../obsidian-notes-karpathy/references/file-model.md
• ../obsidian-notes-karpathy/references/lifecycle-matrix.md
• ../obsidian-notes-karpathy/references/schema-template.md
• ../obsidian-notes-karpathy/references/summary-template.md
• ../obsidian-notes-karpathy/references/activity-log-template.md

Treat skill-contract-registry.json as the canonical source for required references, baseline script, and allowed write surfaces.

If ../obsidian-notes-karpathy/scripts/scan_compile_delta.py exists, run it first.

Non-negotiable rules

• do not rewrite raw/
• write only to wiki/drafts/ and draft indices
• never promote directly into wiki/live/
• keep human captures and agent captures distinguishable in provenance
• keep PDF paper handling strict: raw/**/papers/*.pdf still routes through paper-workbench

Source discovery

Accept:

• markdown captures under raw/human/**
• markdown captures under raw/agents/{role}/**
• markdown captures directly under raw/ in bootstrap vaults
• legacy-layout markdown captures under older paths only during migration
• paper PDFs under any papers/ subtree inside raw

Main outputs

• wiki/drafts/summaries/**
• wiki/drafts/concepts/**
• wiki/drafts/entities/** when needed
• wiki/drafts/indices/*
• batch ingest entry in wiki/log.md

The compile pass exists to hand clean draft packages to kb-review, which then writes outputs/reviews/**, promotes approved pages into wiki/live/**, and rebuilds wiki/briefings/**.

Draft requirements

Every draft should include:

• explicit evidence
• clear separation between source claims and compiler inferences
• draft_id
• compiled_from
• capture_sources
• review_state
• review_score
• blocking_flags
• evidence_coverage
• uncertainty_level

Drafts should be shaped for review, not for final polish.

Output to the user

Always report:

1. how many captures were new, changed, or unchanged
2. how many draft summaries were created or updated
3. how many draft concepts or entities were touched
4. whether any PDFs were skipped because paper-workbench was unavailable
5. whether the next step is kb-review