Skip to content

Garry's Opinionated OpenClaw/Hermes Agent Brain

TypeScript

Docs: raw-only rules do not fence extracted facts

garrytanbf678f9930f9
diff --git a/CHANGELOG.md b/CHANGELOG.md
index 8286ca1bed..8299ab0152 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -12,7 +12,7 @@ identifiers and attribution are available in the pre-removal Git revision
## [Unreleased]
-**Three opt-in ways to share what is derived from member-restricted pages: raw-only folder rules, audience members the owner reads, and member lineage reads.** A folder rule kept the summaries, atoms, chronicle events and facts made from its pages as tightly as the pages themselves, so a transcript folder kept to one member hid every summary of those calls from everyone else; a group chat's own memory page was closed to the brain owner; and only the owner could read the derived pages and facts of pages it already reads. Each now has an operator setting, off by default, and nothing changes on upgrade: `gbrain access rule add --raw-only` keeps a folder's pages to its readers but lets whoever reads a derived page read it (use it for transcripts, never for a folder whose content is itself the secret); `gbrain access member kind <id> audience` lets the owner read that member's own member page, versions, derived pages and facts; and `gbrain access members-read-lineage on` lets every member read the derived pages and facts of pages it reads, as the owner does. All three work the same on a repo-less brain and with rules in `access.yml`, only the operator on the brain host sets them, and no write widens.
+**Three opt-in ways to share what is derived from member-restricted pages: raw-only folder rules, audience members the owner reads, and member lineage reads.** A folder rule kept the summaries, atoms, chronicle events and facts made from its pages as tightly as the pages themselves, so a transcript folder kept to one member hid every summary of those calls from everyone else; a group chat's own memory page was closed to the brain owner; and only the owner could read the derived pages and facts of pages it already reads. Each now has an operator setting, off by default, and nothing changes on upgrade: `gbrain access rule add --raw-only` keeps a folder's pages to its readers but lets whoever reads a derived page read it (use it for transcripts, never for a folder whose content is itself the secret: summaries of a raw-only page, and the facts extracted from it, are readable like any other derived page, so the facts pulled out of a fenced transcript are not fenced); `gbrain access member kind <id> audience` lets the owner read that member's own member page, versions, derived pages and facts; and `gbrain access members-read-lineage on` lets every member read the derived pages and facts of pages it reads, as the owner does. All three work the same on a repo-less brain and with rules in `access.yml`, only the operator on the brain host sets them, and no write widens.
### Itemized changes
diff --git a/docs/guides/access-designations.md b/docs/guides/access-designations.md
index 18fd04e9dd..1ff4ce8312 100644
--- a/docs/guides/access-designations.md
+++ b/docs/guides/access-designations.md
@@ -146,7 +146,8 @@ except the owner's, whose new pages stay shared (`POST /ingest` still refuses bo
pages and facts derived from them: an atom, a summary, a synthesized concept, a chronicle event or a fact made from a
raw-only page is read by whoever reads that derived page. Use it for raw material such as call transcripts, whose
summaries are meant to be shared. Never use it for a folder whose content is itself the secret: a summary of a
-raw-only page carries what the page says. A page's own `readable_by` still hides what is derived from it, and a page
+raw-only page carries what the page says, and the facts extracted from it are readable like any other derived page,
+so the facts pulled out of a fenced transcript are not fenced. A page's own `readable_by` still hides what is derived from it, and a page
that another covering rule also matches stays covered. Every rule written before this existed covers derived pages and
keeps its digest. Making a rule raw-only widens access, so it waits for `gbrain access apply` (preview, then
`--expect <plan_hash>`); making it covering again (the same command without `--raw-only`) applies at once. Doctor's