ARTICLE XXXIV/RATIFIED 26.05.24/REVISION 1.0.0

Governance Proposal Lifecycle (GPL-01)

A finite, deterministic state machine through which every governance proposal must pass. No state is optional; no transition is implicit.

§44.1 States

DRAFT, SUBMITTED, REVIEW, VOTING, RATIFIED, REJECTED, WITHDRAWN, SUPERSEDED. All proposals begin in DRAFT and terminate in exactly one of: RATIFIED (further → SUPERSEDED), REJECTED, WITHDRAWN.

text
DRAFT ──submit──► SUBMITTED ──open_review──► REVIEW ──open_vote──► VOTING │ ┌──fail RWC-01──► REJECTED ◄───────┤ │ │ └──pass RWC-01──► RATIFIED ──amend──► SUPERSEDED DRAFT/SUBMITTED/REVIEW ──withdraw──► WITHDRAWN

§44.2 Transition Prerequisites

submit: proposal has title, body, class∈{standard,constitutional,charter}, author_sig. open_review: class-appropriate co-sponsor count met (1/3/3). open_vote: REVIEW duration ≥ MIN_REVIEW (standard 72h, constitutional 168h, charter 336h). RWC-01 evaluation runs at VOTING close; outcome is computed once and recorded immutably.

json
{ "min_review_hours": { "standard": 72, "constitutional": 168, "charter": 336 }, "min_voting_hours": { "standard": 72, "constitutional": 168, "charter": 168 }, "cosponsors_required": { "standard": 1, "constitutional": 3, "charter": 3 } }

§44.3 Termination Rules

RATIFIED proposals enter the civilization memory layer as the new effective record for their target. They can only leave RATIFIED via SUPERSEDED, never via deletion. SUPERSEDED, REJECTED, and WITHDRAWN are terminal; their ledger entries remain addressable forever per Article XIX.

§44.4 Idempotency & Replay

Every transition is identified by (proposal_id, from_state, to_state, t_snap). Replaying the same transition is a no-op. Two transitions with identical (proposal_id, from_state) and different to_state MUST be rejected by the runtime — the state machine has no concurrency.

§44.5 Final Principle

Governance is not a feeling. It is eight states and a fixed set of edges between them. A proposal not in one of those states does not exist.

Every law was once a state transition. GPL-01 says so out loud.

Operational Bindings

View system map →

This article is not inert prose. It compiles into the following runtime systems, schemas, signals, and governance permissions.

Bound Systems
  • Governance Core
    L8 · GOV-01
    Owns the proposal lifecycle, quorum gating, and amendment of the amendment process.
    governanceproposal lifecycleonline
    kiri:system/governance
  • Swarm Engine
    L2 · SWM-01
    Computes reputation-weighted consensus and binds swarm lifecycle to memory.
    swarmquorumonline
    kiri:system/swarm
  • Persistent Memory Layer
    L1 · MEM-01
    Addressable, signed, reversible storage of every ratified record.
    memoryappend-only ledgeronline
    kiri:system/memory
Published Schemas
  • kiri:spec/GPL-01
    Eight-state deterministic proposal state machine.
  • kiri:schema/Proposal
    Lifecycle envelope consumed by GPL-01 transitions.
Emitted Signals
proposal.openedproposal.ratifiedproposal.superseded
Governance Permissions
proposal.openproposal.voteproposal.ratify
Runtime Flows
  • GOV-01 · Governance CoreSWM-01 · Swarm EngineVOTING state invokes RWC-01 for quorum evaluation.
  • GOV-01 · Governance CoreMEM-01 · Persistent Memory LayerTerminal states commit to the ratification ledger.
End of Article XXXIV · Doctrine MELEGA-GPL-XXXIV · Verified by Consensus