Mnemomemory infrastructure

New · People

Everyone you know, remembered properly.

A person in Mnemo is a memory container with a face: contact details, important dates, what they told you last time, and the reminders you owe them. Ask about anyone and get an answer with the memories it came from.

REST API: POST /v1/people creates a person as a container tagged person:<slug>; POST /v1/reminders adds a reminder (a memory with a dueAt); GET /v1/reminders/upcoming buckets overdue, due today, and upcoming in your IANA timezone. Scopes people:read, people:write, reminders:read, reminders:write — opt-in, existing keys gain nothing until you add them.

Three calls, one person

  • Create the person — POST /v1/people with a display name; Mnemo slugs it (alice-chen), creates the person:<slug> container, and keeps relationship, email, phone, company, notes, aliases, and important dates on the container itself. Slugs are immutable; a collision is a 409 PERSON_EXISTS, never a silent -2.
  • Write what they tell you — memories about a person go through the same POST /v1/memories you already use, scoped to their container. Reminders are memories with a dueAt: POST /v1/reminders, complete or reopen them by id, and list what is due with /v1/reminders/upcoming in your own timezone.
  • Ask before you meet — GET /v1/people/{slug}/summary answers 'who are they, what matters to them, what is open' over that container only, with citations, open reminders, and the most recent memories attached. If the reader has nothing, it says so instead of inventing.

Personal data, kept on a short leash

  • Tenant-isolated, id-blind — a slug that exists in someone else's workspace is a 404 for you, never a 403 that confirms it exists.
  • Explicit scopes, nothing implied — people:* and reminders:* are new scopes; MCP grants never get them.
  • Archive, never erase — DELETE /v1/people/{slug} archives the container and, only with deleteMemories=true, soft-deletes their memories (capped at 500, 409 TOO_MANY_MEMORIES above that) with the same one-hour recovery window as every other delete.
  • Summaries with receipts — the person summary is answered over that person's container alone, with the memories it used printed underneath.
  • Contact fields cannot be clobbered — person metadata is merged, not replaced, when an SDK writes to the container.
  • Rolling out workspace by workspace — until People is enabled for yours the routes answer 503 with code FEATURE_DISABLED rather than 404.

Explore Mnemo