notion-schema.md
Language Markdown1.8 KB38 lines
# The `better-memory` Notion databaseOne database, written only by the nightly distiller, read by any Claude that has theNotion connector. Each page is one entity; the typed Relations in page bodies make thedatabase a small knowledge graph.## Properties| Property | Type | Notes ||---|---|---|| `Title` | title | The entity's name, in Title Case. **The match key for idempotent upserts:** one page per title, updated in place. || `Type` | select | `person`, `anchor`, `thread`, `context` or `note` (below). || `Distilled` | date | The run date that last wrote the page. || `Derived from` | text | Short tags naming what the page was built from. || `Tags` | multi-select | Lowercase topic tags. Seed the vocabulary before the first run, or writes that use a new tag can fail. |### Type| Type | Meaning ||---|---|| `person` | A real human in the owner's life. || `anchor` | A foundational, identity-shaping entity others refer back to. || `thread` | An active, time-bound initiative with a goal. || `context` | A setting or environment that frames other work. || `note` | The catch-all: a creative work, a tool, a concept. |## Page body1. **A recall paragraph**, two to four sentences, answering "what would you need toknow to discuss this usefully." Self-contained; it often answers the question alone.2. **`## Observations`**, one fact per bullet as `- [category] fact`. Categories:`context`, `goal`, `constraint`, `decision`, `pattern`, `preference`, `question`,`blocker`, `status`, `lesson`.3. **`## Relations`**, one edge per bullet as `- relation_type -> Entity Title`, wherethe target is another page's exact Title. Types: `part_of`, `works_on`, `maintains`,`collaborates_with`, `depends_on`, `relates_to`.See [`examples/distilled-entity.md`](../examples/distilled-entity.md).