Garry's Opinionated OpenClaw/Hermes Agent Brain
On a source whose pages are canonical in Git (canonical: git), a fact for an entity with no page under a folder access rule is no longer kept in the database only: it is held on the holding page of the entity's folder (partners/memory/unattributed for partners/acme-example), in Git (or database-only where the folder is) with exactly the readers the entity's page would have. The reply names that page. gbrain access rule add previews the held facts a new rule covers (held_facts_moving) and its apply moves them off their holding page (held_facts), as do gbrain access apply, gbrain access resume and a sync that applies a rule from Git; the moved rows and those entities' struck rows also leave that page's saved versions in the database (held_versions_editing, held_versions_edited), and Git history is not rewritten. A saved version stored in segments is not edited: the preview names how many (segmented_versions_not_edited) and the apply says complete: false. A move still pending is reported with its request id (pending, HELD_FACT_PENDING), not counted as moved. A held fact is now also hidden from a caller who cannot read its holding page, even under a rule with covers_derived: false. gbrain repair facts-home writes such facts to their folder's page and lists as folder_restricted only an exact page rule or unreadable rules. A remember for a page-less entity under an exact page rule now refuses git_home_required with a fix that creates the page, and one whose access rules this database role cannot read refuses access_policy_pending; both wrote the fact to the database before. An existing page whose slug ends in /memory/unattributed is now read as a holding page: a row with no entity cell becomes a fact with no entity, a row naming an entity in the page's own folder becomes that entity's held fact, and a row naming an entity of another folder is a fence problem. Non-strict sources and brains with no Git repository are unchanged.