BYBLOS
GOVERNANCE — VERSIONSNo workspace · dev

Version history — every write bumps the version and the previous book is kept whole. Nothing is deleted from this history. The newest version is not authoritative unless canonical state (the live book) says so.

Open the full version history on the rulebook →the canonical book’s version history — exposed, not duplicated
VERSION SNAPSHOTS8current: rb_2026-08-12.8
rb_2026-08-12.12026-08-12 · write #11 rule
R-AE-202
rb_2026-08-12.22026-08-12 · write #21 rule
R-AE-202
rb_2026-08-12.32026-08-12 · write #32 rules
R-AE-202, R-AE-203
rb_2026-08-12.42026-08-12 · write #42 rules
R-AE-202, R-AE-203
rb_2026-08-12.52026-08-12 · write #53 rules
R-AE-202, R-AE-203, R-AE-204
rb_2026-08-12.62026-08-12 · write #63 rules
R-AE-202, R-AE-203, R-AE-204
rb_2026-08-12.72026-08-12 · write #74 rules
R-AE-202, R-AE-203, R-AE-204, R-AE-205
rb_2026-08-12.82026-08-12 · write #8CURRENT4 rules
R-AE-202, R-AE-203, R-AE-204, R-AE-205
WHAT CHANGED SINCE THE LATEST SNAPSHOT
No rule gains or losses since this snapshot — ids match the live book.

The diff is computed against the live rulebook (gained/lost rule ids). Version causality is not invented — only canonical id membership is reported.

SUPERSESSION CHAINS (from the live book)
No supersession links in the live book.
CROSS-DOMAIN LOOP
WORKoperate→AUTHORITYresolve permission→DECISIONSrecord what happened→GOVERNANCEconstrain with active rules
To sign (Human Gate) →the ONE activation door — nothing enters the rulebook unsigned
Decisions under governance →governance explains the institutional constraints visible in a decision
Authority →authority remains read-only from governance — no editing from here