| … | … | @@ -295,8 +295,12 @@ OrgEventLog, and the autobee migration guard. It converts a silent fork into a l |
| 295 | 295 | 3. **Community and list URIs** for `visibility` (§11 #4). |
| 296 | 296 | 4. **Reply visibility inheritance** (§11 #5) — almost certainly inherit, but the failure mode is |
| 297 | 297 | publishing to the wrong people, so it must be explicit rather than emergent. |
| 298 | | 5. **Where `STRIP_VERSION` is stamped** — the room's StateBase, the commit, or both. §10.3 fixes the |
| 299 | | pattern, not the location. |
| 298 | 5. ~~**Where `STRIP_VERSION` is stamped**~~ **RESOLVED 2026-09-05: the ROOM's StateBase.** The signer |
| 299 | role is per-room — a signer materialises *that room's* record set — so the version that gates it |
| 300 | must be per-room too. An under-versioned peer refuses the signer role **for that room** and can |
| 301 | still sign others, which is what makes a fleet rollout possible at all: a single global stamp would |
| 302 | force every room to move at once. The commit is the wrong place: it is a projection artifact, and a |
| 303 | guard that lives in a projection cannot gate the thing that produces it. |
| 300 | 304 | |
| 301 | 305 | --- |
| 302 | 306 | |