Pattern
LLM Wiki
The clean seed pattern: raw files, maintained wiki, agent instructions, logs, and search. Boring files become useful when agents can work with them.
Open resource
Back to resources
Resource shelf
Second Brain / Company Brain.
Useful company memory starts as inspectable source material. These are the patterns, tools, and references I keep coming back to when thinking about second brains, company brains, and agent-readable knowledge systems.
Foundation patterns
Start with boring files.
The strongest company-brain patterns begin with source material people can read, edit, cite, and repair.
Spec
Open Knowledge Format
Google formalizing the markdown knowledge-bundle direction. Useful bridge from personal wiki to company-grade structure.
Open resourceKnowledge structure
Model the work.
A company brain needs reusable ideas, relationships, provenance, and decision trails. Not just folders.
Practice
Evergreen Notes
Notes written as durable, reusable ideas instead of temporary scraps. Useful company brains should produce reusable building blocks.
Open resourcePractice
Zettelkasten
The older linked-note lineage behind much of modern second-brain thinking. Small notes compound when they are atomic, linked, and revisited.
Open resourceStructure
Ontology
A way to define the kinds of things in the company brain and how they relate: products, customers, decisions, claims, sources, workflows.
Open resourceStructure
Knowledge Graphs
The practical relationship layer: people, projects, products, claims, sources, and decisions connected by typed relationships.
Open resourceDiscipline
Source-First Notes / Provenance
A company brain needs to preserve where claims came from. Source, author, date, confidence, and evidence matter more once agents act on the knowledge.
Open resourceDecision memory
Architecture Decision Records
ADRs capture important decisions with context and consequences. A company brain should remember not just what is true, but why choices were made.
Open resourceOperating discipline
Keep memory trustworthy.
Once agents use a brain as context, stale or messy notes become operational risk.
Principle
Task-Scoped Memory
Memory should be explicit and topical, not an automatic chronological dump. Load the context for the task, not the whole past.
Open resourceWorkflow
Clean and Messy Vault Separation
Agents need a place to be messy without contaminating the trusted personal or company vault. Useful for explaining raw vs curated layers.
Open resourceRisk
Knowledge Drift
Old docs become active risk when agents use them as source of truth. A company brain needs maintenance, not vibes.
Open resourceWorkflow
Persistent Codex Memory in Obsidian
Makes memory boring and useful: editable, diffable continuity across coding sessions. A strong individual memory pattern before company scale.
Open resourceCompany scale
Turn notes into infrastructure.
The company-brain idea becomes serious when permissions, versioning, team spaces, and agent connections enter the picture.
Product thesis
Shared Company Brain
Shared brain connected to agents, permissions, suggested changes, versioning, SSO/RBAC, and private team brains.
Open resourceFoundational tools
Useful building blocks.
Tools that help agents search, inspect, or work with local knowledge and code.
Tool
qmd
Local markdown search and MCP access over notes and docs. Useful when agents need to search a markdown knowledge base without manually skimming everything.
Open resourceTool
ast-grep
Syntax-aware code search and rewrite. Useful when agents need to inspect or transform code by structure instead of brittle text matching.
Open resourceTool
Obsidian
Local markdown notes with links, files, and human-editable structure. A practical substrate for personal or team knowledge bases.
Open resourceCurated from Arun's local AgentTools bookmark mining and Bottl brain notes. This shelf is intentionally source-first: inspectable files, durable notes, provenance, and maintenance before magic memory.