BYBLOS
GOVERNANCE — CANDIDATESNo workspace · dev

A candidate is not an active rule. Learning may propose; only human ratification activates governance. A promoted candidate lands quarantined in the canonical store — the Human Gate signs it into force. No candidate becomes active governance by itself. This view is read-only.

THE CANDIDATE LIFECYCLE
1. Evidence →2. Observation →3. Candidate →4. Institutional / Human Ratification →5. Active Governance

No learning candidates yet. Candidates arise from gate corrections — when an editor corrects a piece at the gate and files it as a proposed rule, it will appear here with the decision that produced it. A chief promotes a proposed candidate into the canonical rulebook store, then signs it into force on To sign.

NOT CARRIED BY THE CANDIDATE STORE

The candidate store (rulebook_candidates) carries layer, scope, draft text, status, promoted rule id, and a gate-event provenance link. It does NOT carry activation timestamp, ratification timestamp, jurisdiction, cryptographic signature, or a candidate-origin chain beyond the gate event. These render honestly as unavailable — never fabricated. Activation truth belongs to the Human Gate under AUTHORITY.

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