Memory diff

If an agent's memory is a folder of text in git, then what it learned this week is a diff you can review. This is a worked example. The project, names and notes are invented to show the shape.

Example data. Nothing on this page is from a real repository. It shows the kinds of changes you'll see, in the real file format.

Monday: a decision, with its reasoning

The agent was asked to pick a database for a new billing service. It saved the decision as a fact, and the reasoning as a trace, linked to what informed it.

memory/graph/facts/2026-11.kgl · +9 −0
@@ -41,0 +42,9 @@+@Fact billing-service uses_database postgres+subject: "billing-service"+predicate: uses_database+object: "PostgreSQL 16, not MySQL: row-level locking for invoice runs"+updated: 2026-11-16T09:42:10+[about] → entities/objects/billing-service.kgl#billing-service++#decision+
memory/graph/reasoning/2026-11.kgl · +7 −0
@@ -0,0 +1,7 @@+@ReasoningTrace choose-billing-database+goal: "Pick a database for the billing service"+outcome: "PostgreSQL, because invoice runs need row-level locking"+at: 2026-11-16T09:44:02+[informed_by] → facts/2026-11.kgl#billing-service uses_database postgres+[informed_by] → preferences/dana.kgl#dana prefers managed_databases+

How to get your own

$ git log --since="1 week ago" -p -- memory/graph/

Or open a pull request that touches memory/ and review it like code. Set it up in five minutes →