Personal KMS

A personal KMS is the cleanest expression of the eight principles, because there is exactly one user, one trust boundary, and one source of intent. The work is in making it survive your inattention, not in coordinating across people.

What this tier is

A knowledge layer attached to one person. It captures sessions, conversations, decisions, and references; it compiles them into entities and concepts; it surfaces what's relevant when you start a new task. The interface is whatever surface the person is on right now — Claude in terminal, a vault open on iPad, a quick voice note on a walk.

Trust is total. The system has full read-write access to everything the person knows. No role-based permissions, no audit log, no compliance overhead.

Which principles it uses

All eight, in their strictest form:

• Route, Don't Organize — the person never picks a folder; capture-rate is everything.
• Separate State / Knowledge / Interface — three layers; the warehouse layer doesn't apply.
• Automatic Compilation — runs on every ingest, no review queue.
• Bouncer-Promoter — strict bouncer; the cost of clutter compounds fastest at this scale.
• Design for Neglect — the most load-bearing principle here. Personal KMS dies first to absence.
• Entity Context — people, projects, concepts; the schema is small and stable.
• Ripple & Contradiction — runs continuously; the user resolves contradictions in conversation.
• Hybrid Authorship — the line is permissive; the LLM compiles most things; only durable opinions are human-authored.

Tier-specific divergences

• Session memory + async ingestion. Personal KMS lives between two surfaces: the live Claude conversation (session memory, ephemeral) and the durable vault (markdown, append-mostly). The pattern is every interesting session ends with an explicit "save what mattered" step. The agent compiles the session into vault-ready entries and the user confirms.
• Voice as a first-class input. A personal KMS that doesn't accept voice notes leaves capture on the table. Walk, talk, ingest, compile.
• Generous autonomy. Because trust is total, the agent can route, write, and link without asking. The user's role is editor, not approver.
• One vault, no tenancy. No need for org/user separation. The whole vault is the working set.

What it is NOT

• A team KMS. Sharing a personal KMS with one other person breaks every assumption — role-based permissions, institutional-knowledge extraction, multi-author voice. That's the team tier.
• A productivity app. State (priorities, tasks) lives in the state layer but the KMS is not a task tracker. Confusing the two collapses the state/knowledge separation.
• A note-taking app. Notes are inputs to entities, not the unit of value.

The reference implementation

A personal orchestrator built on Claude Code — markdown vault on disk, an Obsidian companion for browsing, and a small set of skills for ingest, check-in, and session capture. The architecture is described in the system page.