Personal knowledge system components

The operating map of the system.

This is the current component map, not just the evolution story: vault, schema, operating layer, validation, indexes, capture routes, agent runtime, skills, and public outputs. The vault stays the source of truth; everything else reads from it or writes back with provenance.

Source

Markdown vault

Structure

Schema & frontmatter

Operating layer

system/ folder

Integrity

Validation & indexes

Interfaces

Agent interfaces

Taxonomy: hardware, editor apps, hosting, and developer tools belong under Tech Stack. Vault structure, validation, capture routes, skills, and agent interfaces are components of this Personal Knowledge System.

Components

Source Markdown vaultThe durable source of truth: Markdown files, folders, WikiLinks, frontmatter, notes, project context, decisions, and references that stay readable outside any app. Open → Structure Schema & frontmatterThe typed shape of the vault: metadata, entity fields, topics, status, source links, project slugs, dates, and classification rules. Open → Operating layer system/ folderThe internal operating layer: contracts, docs, scripts, indexes, workflow state, templates, and agent instructions that make the vault runnable. Open → Integrity Validation & indexesThe quality gate and retrieval layer: validators, link checks, generated indexes, read models, and failure events when something cannot be safely written. Open → Interfaces Agent interfacesThe access layer on top of the vault: Telegram, voice, screenshots, web capture, email routes, Hermes, repo tools, browser tools, and scheduled jobs that turn the vault into an operational cockpit. Open →

Core rule: Hermes memory, sessions, facts, Telegram, skills, and generated indexes are useful caches/interfaces. The durable truth lives in Markdown files with schema, provenance, validation, and source-backed links.

Open skills registry → Open agent workflow → Open guides →