Central KB, Project Directories, and Publication Nodes
Defines what the central knowledge base, project directories, and publication node each own, and why a single vault template is not enough for fact governance.
federated-knowledge-base
6 public items tagged federated-knowledge-base.
Why I Do Not Use Chat Logs as My Knowledge Base
Explains why chat logs are not a durable knowledge base and how Obsidian, local Markdown, Codex, project directories, and publication nodes form a federated system.
What Obsidian Actually Does in an AI Knowledge Base
Explains Obsidian's real role in an AI knowledge base: local Markdown, links, backlinks, and human review, not an automatic truth machine.
Boundaries: Privacy, Truth Sources, Audit, and Failure Modes
Summarizes the system boundaries and failure modes: privacy, project truth sources, premature automation, site truth drift, and AI output mistaken for evidence.
Why Project AI Should Not See the Whole Knowledge Base by Default
Explains why project AI should not read the whole central knowledge base by default and how local facts, narrow interfaces, and selective memory reduce risk.
kb lookup / promote / publish: Narrow Knowledge Interfaces
Shows how kb status, lookup, promote, and publish form narrow interfaces that let AI reuse, promote, and publish knowledge without crossing boundaries.