Home

NormaEngineering

Memory

What gets remembered. Memory is for what the person wants, not for their money. A balance or a bill is looked up fresh every time. A bank login stays in the vault. All of a person’s bots read and write the same memory, and a memory never grants a capability.

Claims and rules. A claim is a purported statement of fact: one thing, one value, said at a time. “The payday transfer is $200.” A rule is a command. “Ask before moving more than $50.”

Where it lives. A bot sends the person’s words to past.dev with the time they were said. past.dev keeps the current value and the one it replaced, each with its date. It sits behind my own interface, so I can change the memory layer later without reworking the bots.

When two claims collide. A later claim replaces the earlier one, and the old value stays as history. If a new value for the same claim arrives inside a set window, Norma asks before writing it on top. If the person says one of the two was a mistake, that claim is deleted. It is not kept as history.

Every call below goes to past.dev with the project key in the Authorization header. That key stays on the server.

Saving a rule. The person tells the savings bot, “On payday, move $200 to savings only if I’d still have more than $500.” The server sends those words as they were said. The audience is this person, and each of their bots is a member of it, so any of them can read what was saved. The identity is the bot that wrote it. That records the author. It does not let the bot do anything new.

POST https://api.past.dev/api/v1/ingest

{
  "id": "msg-1842-savings-payday",
  "content": "On payday, move $200 to savings only if I'd still have more than $500.",
  "timestamp": "2026-11-18T15:04:00Z",
  "audience": "person-1842",
  "identity": "bot-savings",
  "label": "Savings bot"
}

past.dev answers with an ingestionId and a status of queued. The words are not part of memory yet. The server reads the ingestion until status is completed. past.dev has then derived the rule, and the claims inside it.

GET https://api.past.dev/api/v1/ingest/{ingestionId}

On payday the savings bot recalls the rule. The balance is a fresh lookup, not a memory. If more than $500 would remain, the bot asks Norma to move the $200, and Norma still waits for the person.

POST https://api.past.dev/api/v1/recall

{
  "query": "What should I do with savings on payday?",
  "identity": "bot-savings"
}

A claim that changes. Earlier that day the savings bot saved “The payday transfer is $200,” under the source id msg-1842-payday-200. The person then tells Norma, “Make it $300.” Norma recalls the current amount before it writes anything.

POST https://api.past.dev/api/v1/recall

{
  "query": "How much is the payday transfer?",
  "identity": "bot-norma"
}

The $200 claim is inside the window, so Norma asks before writing $300 on top of it. The person says the $200 was a mistake. That source is deleted, and the memory that rests only on it goes with it. $200 is not kept as history.

DELETE https://api.past.dev/api/v1/data-points/msg-1842-payday-200

The correction is then saved as its own source, and the server waits on the same GET until that ingest is completed. $300 is now the current claim.

POST https://api.past.dev/api/v1/ingest

{
  "id": "msg-1842-payday-300",
  "content": "The payday transfer is $300.",
  "timestamp": "2026-11-18T18:12:00Z",
  "audience": "person-1842",
  "identity": "bot-norma",
  "label": "Norma"
}

If that correction had arrived outside the window, Norma would not ask and would not delete. It would ingest the new words with a new id and a later timestamp. past.dev would keep $300 as the current value and $200 as history. A recall from before the change would still return $200.

POST https://api.past.dev/api/v1/recall

{
  "query": "How much is the payday transfer?",
  "identity": "bot-norma",
  "queryTimestamp": "2026-11-18T15:00:00Z"
}