knowledge-base-enrichment

Knowledge Base Enrichment

Turn raw Markdown notes into a traceable knowledge base without silently rewriting the source layer.

Use When

• enriching one note with tags, source attribution, or related-note links;
• organizing a vault or Markdown corpus into generated wikis;
• refreshing a wiki from new or changed source notes;
• preparing durable, source-grounded context for an agent or reader workflow.

Default Layout

vault/
  raw/       # source notes; read-only by default
  wikis/     # generated synthesis; writable only in the selected scope
  tags.md    # shared tag registry
  .knowledge-base/
    state.json
    proposals/
    logs/

Adapt to an existing layout after inspecting it. Do not create a parallel vault when a clear local structure already exists.

Workflow

1. State the source root, writable output scope, and whether the user explicitly authorized apply.
2. Read the local tag registry and the target wiki's AGENTS.md/index.md before proposing changes.
3. Read the target note and inspect existing frontmatter without rewriting its body.
4. Propose only evidence-backed metadata:
   • reusable kebab-case topic tags;
   • source and url when the origin is real and known;
   • links to related notes that actually exist.
5. Keep the proposal under .knowledge-base/proposals/ until it is inspected and explicitly applied.
6. On apply, write derived metadata/state and generated wiki pages in the selected scope. Keep raw/ content unchanged unless the user explicitly authorizes a source edit.
7. Record changed sources, skipped ambiguities, unresolved links, and the verification result in a log.

Idempotence

• Track enrichment state in .knowledge-base/state.json, not by adding silent stamps to raw notes.
• Skip notes whose content hash and enrichment inputs are unchanged.
• Reuse existing tags; add a new tag only when it is broadly reusable and record why.
• Never invent source URLs, related-note targets, claims, or wiki entities.