BYBLOS
GOVERNANCE — ACTIVENo workspace · dev
GOVERNANCE REGISTER4 rules
SYSTEM STATE
GOVERNANCE ACTIVE4 active · 4 totalversion rb_2026-08-12.8 · 8 snapshots
RATIFICATION

Governance enters the book through human ratification — a named chief signing a proposed rule into force. Nothing enters unsigned. The signing surface is the only door.

Signing surface →
ACTIVE GOVERNANCE

R-AE-204

Flag scheduling or content tied to religious holidays in AE-market pieces for human compliance review before publication. Editorial flag only, derived from the taxonomy note that religious holidays are a named compliance concern in this market. This rule names no specific holiday and asserts no legal claim or prohibition.

GOVERNANCE STATE
STATUSACTIVE
GOVERNINGYES — constrains decisions
LAYERcompliance
EFFECTADVISORY
FROZENYES — held; human ruling required
QUARANTINE THRESHOLD20 pieces

This rule is active governance — it may constrain a decision. Active governance ≠ authority: it does not establish principal authority, mandate validity, or execution permission.

RATIFICATION
RATIFIEDYES — ratified by a named human
RATIFIERratified by gaspard (chief) — ratified by Gaspard 11 Aug 2026 — "we can start working now and refine later, it's fine." Source: the four candidate fixtures derived from byblos-taxonomy.md line 46 (alcohol, modesty, religious holidays, political sensitivities). Advisory-only: route to human review, suppress nothing. Refine-later noted; every promotion is versioned, attributable, and removable in one act.

Ratified \u2260 Active. Ratification is a human act recorded in the provenance channel; activation is the canonical status field. A ratified rule may be quarantined (not yet governing). A signature is not authority — it does not establish mandate, delegation, or attenuation validity.

SCOPE
MARKETSAE
CATEGORIESall

Scope is presented canonically. This surface does not evaluate applicability — it does not independently calculate whether a rule governs from market, category, or scope combinations.

PROVENANCE
ORIGINmanual
DERIVED FROMbyblos-taxonomy.md:46
RECORD CREATED2026-08-12

Provenance.created_at is the record creation date, NOT the activation timestamp. No separate activation timestamp is stored.

CITATION USAGE
CITATION COUNT0

Citation count shows usage frequency, NOT policy weight. Precedent \u2260 policy — a frequently cited rule is not a stronger governance force.

UNAVAILABLE SEMANTICS
Activation timestampNot stored \u2014 provenance.created_at is record creation, not activation.
Ratification timestampNot stored separately \u2014 version history carries snapshot dates.
JurisdictionNot available \u2014 market \u2260 jurisdiction; no canonical jurisdiction field.
Piece typeNot available \u2014 scope is market + category only.
Priority / precedenceNot available \u2014 no priority/precedence field in the rulebook.
Temporal validityNot available \u2014 A2/A3/A3.5 frozen; no start/end dates on rules.
Mandate / delegation / attenuationNot available \u2014 no mandate, delegation, or attenuation references.
Cryptographic signatureNot available \u2014 provenance.author is human text ratification, not cryptographic.
Precedent referencesNot available \u2014 no precedent links in the rulebook; citation count \u2260 precedent.
Candidate originNot available \u2014 the promote route records promotedRuleId on the candidate, not on the rule.
DOCTRINE

Only active governance may constrain a decision.

A ratified rule is not governing until it is active.

A signature is not authority.

A candidate is not a policy.

Unknown is a legitimate state.

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