Example stores
The examples/ directory in the
db.md repo
ships five role-flavored example stores. Each is a complete db.md
store showing the two-folder pattern.
Copy and adapt
Everything you configure lives in one file. DB.md carries the
store's identity in frontmatter and, optionally, an ## Agent instructions section (house style, what to prioritize), a
## Policies section (frozen pages, ignored types), and a
## Schemas section (custom type definitions). That single file at
the store root is the whole configuration surface.
The two folders
Every example has the same shape:
sources/holds evidence: emails, transcripts, exports, PDFs, preserved verbatim, plusnotesources that capture what a human told the agent.records/holds everything the agent authors, separated by ameta-typefield.meta-type: fact(the default) is atomic typed data — one file per contact, company, expense, meeting, decision, or invoice.meta-type: conclusionis the agent's synthesis: once you point your agent harness at the store, it owns the conclusion records. You can still edit them; the agent respects the frozen pages listed inDB.md's## Policiessection.
Patterns that show up across all five
- Every conclusion record links to its evidence. A
records/profiles/sarah-chen.mdpage (meta-type: conclusion) links to herrecords/contacts/sarah-chen.mdrecord and thesources/emails/that mention her, always by full path. DB.md ## Agent instructionsis short and direct. A handful of lines is typical; more than a screenful is a smell.DB.md ## Schemasdocuments the type-specific fields, one field per line, sodbmd validatecan enforce them.DB.md ## Policieslists the small set of things the agent should leave alone: frozen pages and ignored types.