Metobe · commitment memory, in development

It remembers promises. It verifies reality.

Metobe turns your team's meetings, chats, email and tools into a living model of commitments, decisions and people, then checks every promise against what actually happened.

Reality ledger reconciling 4 sources
Ship the prototype to MariaAlex · meeting · due Fri
MR !182 opened prototype.zip delivered
Checking
Release on the 12thPlatform team · planning · due Oct 12
no release tag found
Checking
Talk to Sam about pricingAlex · team chat · this week
meeting held · Oct 9
Checking
Send the contract draftMaria · email · due Thu
waiting for evidence
Checking
4 promises every row links to its source

Illustration. Names and data are fictional.

Memory is not chat history

The unit of memory is a change in the world.

Most AI memory finds a similar piece of past text. Metobe turns raw information into data about the world: who promised what to whom, by when, and whether it happened.

Typical AI memory

  1. chat history
  2. embeddings
  3. vector database
  4. retrieve similar text
  5. LLM guesses

“Find something that looks like this.”

Metobe

  1. raw informationmeetings, chats, email, tools
  2. eventswhat happened, when, from which source
  3. entitiespeople, projects, artifacts
  4. relationshipswho works on what, who waits on whom
  5. commitments & decisionsfirst-class objects with a lifecycle
  6. statewhat is true right now, and why
Claudeextracts a structured draft“Looks like Alex promised Maria a prototype by Friday.”
Resolvermatches it to known entitiesAlex → Person #12 · prototype → Artifact #47
Memoryappends an eventcommitment.created · source: meeting #182

The model proposes an interpretation. A deterministic layer decides what changes in memory.

Commitments are first-class objects

Every promise has a lifecycle.

Memory is append-only. Nothing is overwritten; current state is rebuilt from events. So Metobe can always explain why it believes something.

Event log

    Current state, rebuilt from events

    Auditable by design

    Memory you can check.

    Every fact has a source, every guess has a confidence, and the expensive questions are answered by queries, not by asking the model to reread everything.

    Provenance

    Ask why Metobe believes something and get the exact moment it came from.

    Why do you think I promised this?
    You said it in the product sync on Oct 7.
    “Fine, I'll get the prototype to Maria by Friday.”
    Meeting · Oct 7 · 14:32

    Hypotheses aren't facts

    A possible match is stored with its confidence until evidence settles it.

    “the demo build” → Prototype v2?
    0.74proposed
    MR !182 title: “Prototype v2 demo build”

    Entity resolution

    Many names, one person.

    Detectors are queries

    Deterministic checks find what needs attention. Claude explains it and suggests what to do.

    select * from commitments
    where deadline < now()
      and status = 'promised'
      and evidence_count = 0;
    Claude Three promises passed their deadline with no sign of delivery. The release on the 12th blocks two of them. Draft a check-in with the platform team?

    For teams

    Memory becomes a model of the organization.

    With a whole team connected, Metobe sees who waits on whom, which decisions are still in force, and where work actually gets stuck.

    Find the bottleneck

    Waiting chains surface on their own.

    1. LLenaneeds a pricing decision
    2. MMaxneeds usage data
    3. OOlegneeds database access
    4. DDevOpsblocking 3 people · 6 days

    Decisions stay decided

    Until someone decides to revisit them.

    Let's start building the mobile app.
    On Oct 7 the team decided to postpone the mobile app and focus on the web first. Do you want to revisit that decision? Decision · product sync · Oct 7

    Knowledge

    The company uses PostgreSQL.

    Max works on the backend.

    Memory

    On Oct 7 the team decided to use PostgreSQL for Metobe.

    Max took over the backend integration and promised it by Friday.

    Built with Claude

    Claude reasons. Memory keeps score.

    Bigger context windows don't mean everything belongs in them. Metobe rebuilds just the context a question needs, from events, at the moment it's asked.

    Sources

    Meetings · chats · email · documents · calendar · GitHub/GitLab · CRM · tasks · other agents

    Claude

    Reads long, messy conversations. Tells a promise from a maybe. Explains state and drafts actions.

    Metobe memory

    Append-only events, resolved entities, commitments and decisions with lifecycles, deterministic detectors.

    People

    Answers with sources, proactive check-ins, actions that wait for approval.

    Storage for agent memory exists. Metobe decides what is worth remembering, ties it to real people and work, and checks it against what happens.

    Where we are

    The workspace ships. Memory is next.

    • shippingSelf-hosted workspace: models, MCP tools, charts from live data
    • buildingCommitment memory: events, entities, reconciliation
    • buildingBackground agents that act on what memory finds
    • looking forDesign-partner teams who lose track of promises

    What your team promised, kept honest.

    We're looking for a few teams to shape commitment memory with us.