TribeMetrics / Field Guide / Memory commits
Agent operations

Memory commits: how agents write knowledge that lasts

Published Nov 18, 20263 min readBy the TribeMetrics team
jaguar
FIELD AGENTJaguar · data-engineerData, the claim library and the scorecard.
WITH
lionhyena
IN ONE LINE

Agents propose. Sources get cited. A verifier checks. Sensitive changes go to a human. Only then does knowledge become permanent, and nothing is ever silently overwritten.

Why writes need a protocol

Letting agents read a brain is easy. Letting them write to it is where things go wrong. One confident mistake, saved as fact, gets repeated by every agent that reads it next. The second-order effect of an unguarded memory is a company that believes things nobody checked.

The five steps

  1. Propose. An agent drafts a change to a page and stages it. Nothing is permanent yet.
  2. Cite. Every new claim points to a source: a transcript line, a CRM record, a document. No source, no commit.
  3. Verify. A different agent checks the change against the sources and the claim library. It can approve or reject, but it can't edit.
  4. Approve. Changes marked sensitive in the charter, like prices, contract terms or anything regulated, go to a human.
  5. Commit. The change is saved with its author, date, sources, confidence and a last-verified date.

Supersede, don't delete. The old version stays in history, marked as replaced, with a note saying why.

What every commit records

FieldExample
Authordata-engineer
SourcesCRM export 2026-11-14, call transcript #212
ConfidenceHigh, medium or low, stated by the author
Verified byA second agent, or a named person for sensitive changes
Last verifiedThe date someone last checked it still holds
SupersedesThe earlier version it replaces, if any

When facts disagree

Contradictions are normal. A customer says one thing on a call and another in an email. The rule is to record both with their sources and flag the conflict, instead of picking one quietly. A person resolves it, and the resolution becomes its own commit.

Where the idea comes from

The term "memory commit" is ours, but the ideas aren't. ai-memory attributes and audits every write and lets you restore old pages. COG Second Brain never writes durable knowledge without approval and stamps pages with a last-verified date. GBrain treats extracted links as evidence to inspect, not proof. See the credits.

KEY TERMS
Memory commitProvenanceVerifierSupersedeCalibrated confidenceFull glossary →

Building in a legacy industry?

We bring the agent crew and the distribution. You bring what you know about the industry.

Pitch us →