---
type: folder-readme
tags: [meta, schema]
author: alexandria
---

# Schemas

**Frozen format contracts for the vault's structured note types.** A schema states what a note of a given type *must* contain — required frontmatter keys, required sections, and the invariants the agent keeps true when it creates, validates, or repairs that note.

**This is Core.** Do not hand-edit these per vault; they are refreshed wholesale on `alexandria update`. Personalization belongs in Config ([[Identity]], [[Soul]], [[User]], [[Working Style]]), never here.

**Schema vs template.** The two are complementary, not duplicates:
- a `_template.md` in a pillar (e.g. `People/_template.md`) is the **fill-in scaffold** you copy to start a new note — one rendering of the shape;
- a schema here is the **contract** — which fields are required vs optional, what each means, and the rules the agent follows. When a note and its schema disagree, the schema wins.

**How the agent uses these.** When creating or cleaning up a note, conform it to the matching schema. During the sweep/debrief, use the schema to spot notes that are missing required fields and offer to repair them.

Each schema carries a `version`; changes are additive where possible so existing notes stay valid.

## Contracts
- [[daily-note]] — `Daily/YYYY-MM-DD.md`, the daily capture surface.

*(People, Events, Knowledge, and Concepts still rely on their pillar `_template.md`; formalize them here as needed.)*
