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.
@@ -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+
Wednesday: a preference changes, and the old belief is superseded
The user said they'd rather avoid managed databases after all. The agent doesn't overwrite the old preference. It closes it out with valid_to and writes a new one that supersedes it. In review you can see both, and when one replaced the other.
memory/graph/preferences/dana.kgl · +8 −0
@@ -3,5 +3,13 @@ @Preference dana prefers managed_databases subject: "dana" predicate: prefers value: "managed Postgres where possible" updated: 2026-11-09T10:01:12+valid_to: 2026-11-18T14:10:33++@Preference dana prefers self_hosted_databases+subject: "dana"+predicate: prefers+value: "self-hosted Postgres: compliance wants data on our own infrastructure"+updated: 2026-11-18T14:10:33+[supersedes] → preferences/dana.kgl#dana prefers managed_databases
Friday: a bug fix, a convention, and one wrong note caught in review
Two more notes land. In review, someone spots that the second is wrong, and fixes it with a one-line commit before it can mislead the agent next week.
@@ -58,3 +58,3 @@ subject: "billing-service" predicate: convention-object: "Migrations run automatically on deploy"+object: "Migrations are run by hand before deploy; never automatically"
That second diff is the whole point: a wrong belief was visible, attributable and correctable in a normal pull request.