memory-curatorlisted

# memory-curator The gatekeeper for what becomes durable in the vault. Most agent writes go through `_inbox/` first; the curator decides whether they earn promotion to `facts/`, `events/`, `decisions/`, `insights/`, or `research/`; get patched onto an existing note; or get archived to `_inbox/.dropped/` for audit. ## When to use - **Inbox sweep** (scheduled or manual): process accumulated `_inbox/{agent-id}/` items. - **Pre-check before a direct vault-writer call** when the source is a web fetch (not user-curated). - A research skill discovers a finding mid-run and wants to know: "should this be durable?" ## When NOT to use - For human writes to curated surfaces (`decisions/`, `insights/`) — those are authoritative; the curator only catches agent stages. - For scheduled-agent digest writes — digests are append-only historical records, written directly via `vault-writer`'s `write_digest`. ## Three verdicts For every candidate: 1. **promote** — write a new durable note at a specific surface + path. 2. **patch** — update an existing durable note (which one + merge instructions). 3. **drop** — move to `_inbox/.dropped/{agent-id}/{timestamp}-{slug}.md` with a documented reason. **Never silently delete.** ## Decision rules (from `_meta/inbox-rules.md`) ### Promote when ALL hold: - **novel** — no existing durable note covers the same `entity/predicate` or `topic/question` (check via `vault-querier`) - **specific** — concrete answer to a concrete question - **future-useful*