Garry's Opinionated OpenClaw/Hermes Agent Brain
TypeScript
docs: CHANGELOG entry covers the repair's exclusions, per-speaker restores and the unmanaged-brain limit
garrytan1ae6cbcf1c5d
diff --git a/CHANGELOG.md b/CHANGELOG.mdindex 40675d2ffa..7fa0571f44 100644--- a/CHANGELOG.md+++ b/CHANGELOG.md@@ -12,14 +12,16 @@ identifiers and attribution are available in the pre-removal Git revision## [Unreleased]-**A page write or a managed `extract_facts` run no longer retires facts that the page's `## Facts` fence never held, and `gbrain repair unwithdrawn-facts` restores the ones earlier releases retired.** A fact a `put_page` writer attached to a page with a row number, but that was never in the page's fence, used to be expired by any later write that projected the fence. That included a write that changed nothing in the fence, often the page's first facts-fence generation, which `gbrain repair generations` cannot undo because it has no earlier generation. Now a row retires only when a fence held it: a facts-fence generation recorded it, the page as the writer read it carried it, or a stored version of the page did. Every other row stays active with its id. Removing a row from the fence still retires it, as before. Doctor `unwithdrawn_facts` counts the facts that were already retired and points to the new repair, which previews first and restores the original fact ids and lifecycle from the generation ledger. It works on brains with and without a repository.+**A page write or a managed `extract_facts` run no longer retires facts that the page's `## Facts` fence never held, and `gbrain repair unwithdrawn-facts` restores the ones earlier releases retired.** A fact a `put_page` writer attached to a page with a row number, but that was never in the page's fence, used to be expired by any later write that projected the fence. That included a write that changed nothing in the fence, often the page's first facts-fence generation, which `gbrain repair generations` cannot undo because it has no earlier generation. Now a row retires only when a fence held it (a facts-fence generation recorded it, the page as the writer read it carried it, or a stored version of the page did) or when the incoming fence states its claim. Every other row stays active with its id. Removing a row from the fence still retires it, as before. Doctor `unwithdrawn_facts` counts the facts that were already retired and points to the new repair, which previews first and restores the original fact ids and lifecycle from the generation ledger.++The repair restores only what a later write would keep. It leaves a fact retired when you forgot it, including on your own memory page, and when the page's fence states the same claim. For copies of one claim it restores one per speaker. It picks the narrowest visibility first, and a copy that is still valid before one whose validity had lapsed. On a brain without managed persistence the `extract_facts` reconcile still retires rows its fence lacks, so the repair lists those facts as `excluded:unmanaged_reconcile` and restores none of them.### Itemized changes- `src/core/generations/fence-evidence.ts` (new): `factsFenceHeld` decides whether a fence ever held a fact row, from the facts-fence ledger, the replaced body and the page's stored versions. `moveKeptRows` moves a kept row whose number an incoming fence row claims above the page's rows.-- `src/core/generations/adapters/fact-rows.ts`, `src/core/persistence/canonical-projections.ts`, `src/core/trust/fence-guard.ts`: the page projection's fact generation retires only held rows. Conversation-extractor rows still give up a number a fence row claims. Its expire statement and the trust guard leave kept rows alone.-- `src/core/cycle/extract-facts.ts`: on a managed brain the reconcile keeps stale rows no fence held, and moves one whose number a new fence row needs. An unmanaged brain's reconcile is unchanged.-- `src/core/repair/unwithdrawn-facts.ts` and `src/commands/doctor/checks/unwithdrawn-facts.ts` (new): `gbrain repair unwithdrawn-facts [--include-ambiguous] [--apply --expect <hash>]`, bound to each page's revision at preview. Managed brains apply it through a database-only `managed_maintenance_restore_unwithdrawn_facts` request; unmanaged brains apply it under the page lock. A fact a fence held, a withdrawn, superseded or duplicated fact, and a page written since the preview are refused. Doctor check `unwithdrawn_facts`.+- `src/core/generations/adapters/fact-rows.ts`, `src/core/persistence/canonical-projections.ts`, `src/core/trust/fence-guard.ts`: the page projection's fact generation retires only held rows and rows whose claim the incoming fence restates. Conversation-extractor rows still give up a number a fence row claims. Its expire statement and the trust guard leave kept rows alone.+- `src/core/cycle/extract-facts.ts`: on a managed brain the reconcile keeps stale rows no fence held, unless the fence restates their claim, and moves one whose number a new fence row needs. An unmanaged brain's reconcile is unchanged.+- `src/core/repair/unwithdrawn-facts.ts` and `src/commands/doctor/checks/unwithdrawn-facts.ts` (new): `gbrain repair unwithdrawn-facts [--include-ambiguous] [--apply --expect <hash>]`, bound to each page's revision at preview. A managed brain applies it through a database-only `managed_maintenance_restore_unwithdrawn_facts` request. Each fact is listed with its class: evidenced, ambiguous, or excluded with a reason (`fence_held`, `withdrawn`, `fence_states_claim`, `active_duplicate`, `duplicate_candidate`, `unmanaged_reconcile` and others). A page written since the preview restores nothing. Doctor check `unwithdrawn_facts`.- Tests: `test/fence-first-generation-8819.test.ts` and `test/repair-unwithdrawn-facts-8819.test.ts`, on PGLite and Postgres.## [0.60.611.0] - 2026-11-08