Article XII: Governance Kernel

Section 1: Overview

The GK is a computerised system which records all registered initiatives in a single, append‑only total order corresponding to their order of registration. It is the authoritative record for the Constitution, Law, and Public Service Contracts.

The GK maintains the registered initiatives as an event‑sourced history. The Constitution, Law, and Public Service Contracts, whether in their current form or at any point in the past, are computed by folding over this history.

The formal machine‑readable language used by the GK is Predica. Public Service Contracts shall be expressed as Predica legal specifications. The Constitution and Law may also use Predica where their provisions can be expressed formally. Human‑readable text, headings, commentary, and cross‑references may be recorded as annotations associated with the formal specification.

Predica is used where legal meaning depends on clear structural conditions that can be expressed precisely. Natural language and judicial interpretation remain available where legal meaning depends on judgment, context, evidence, or concepts that cannot be fully captured by formal constraints.

The version of Predica accepted by the GK, including any restricted subset or extension used for legal drafting, is itself part of the GK state. Any change to the accepted Predica version or profile shall be made through the same initiative process as other changes to the rule of law.

Conflicts between initiatives are resolved by a formally defined priority order, applied when folding the relevant filtered history to compute a consistent legal state.

The GK represents the constitutional memory of the system. It provides an immutable record of democratic decisions. It is the single source of truth.

Section 2: Initiative ranking

  1. The GK shall rank registered initiatives using the deterministic initiative ranking defined in Appendix E: Initiative ranking.
  2. This ranking governs all GK procedures that require initiatives to be compared, including conflict resolution and the algorithm for determining inactive initiatives.
  3. Where the ranking depends on voting scores that change over time, the GK shall use the scores applicable at the time for which the legal state is computed.

Section 3: Conflicting initiatives

  1. Two initiatives conflict when the legal effects of one negate, override, or render impossible the legal effects of the other.
  2. Some conflicts are formal conflicts that may be detected by Predica tooling, including unresolved references, type errors, invalid constraint expressions, malformed patches, or changes that cannot be applied to the target Legal Domain. Formal conflict detection does not replace judicial interpretation.
  3. Because initiatives may include human‑readable provisions, legal interpretation, and intended effects that are not fully captured by formal syntax, no algorithm can reliably determine all conflicts. When citizens observe contradictory registered initiatives, the judiciary shall make a determination and update the Initiative Incompatibility Relation (IIR) maintained in the GK. The IIR is an irreflexive, symmetric binary relation on registered initiatives.
  4. Judiciary services that determine whether initiatives conflict are funded through tax in the same manner as other public services.
  5. At the end of each day, the algorithm defined in Appendix F: Algorithm for determining inactive initiatives shall run in the GK to determine which initiatives are marked as inactive. This procedure is deterministic: for any given IIR and the ranking defined in Appendix E: Initiative ranking, the GK produces a unique inactive set.
  6. Inactive initiatives are retained in the event‑sourced history of the GK. The inactive state is used only as a filter when folding over history, so that inactive initiatives behave as though they had never been registered.

Section 4: Legal specifications and event sourcing

  1. The GK represents each Legal Domain as a versioned legal component. The Legal Domains are the Constitution, the Law, and each Public Service Contract.
  2. A Public Service Contract legal component shall contain a Predica specification defining the contract's formal compliance conditions. A Constitution or Law legal component may contain Predica specifications, human‑readable provisions, or both.
  3. A Predica specification may include type declarations, attributes, constraints, derived attributes, functions, enumerations, variants, metadata, and annotations. In normative use, Predica constraints define conditions that the relevant world, institution, public service, or transaction must satisfy.
  4. A registered initiative records a patch to exactly one Legal Domain. A patch may add, replace, or remove Predica declarations, constraints, derived definitions, annotations, human‑readable provisions, or rendering metadata.
  5. The GK stores every registered initiative in an append‑only sequence. To compute the legal state at any point, the GK determines the active initiatives according to Section 3 and then folds the active patches in GK sequence order. Inactive initiatives remain in history but are ignored by this fold.

Section 5: Administrative Initiatives

An Administrative Initiative:

  • records changes to a single Legal Domain like any other initiative, including changes to Predica specifications, annotations, or public renderings, and is processed by the GK in the same manner as any other initiative;
  • is submitted for registration by the Judiciary, not by the Voting System;
  • exists solely for the purpose of correcting mistakes, improving clarity, preserving formal consistency, avoiding ambiguity, or preventing contradictions;
  • shall not change the compliance conditions imposed by the affected Legal Domain.

Section 6: Public text and annotations

  • The GK shall support public renderings of the Constitution, Law, and Public Service Contracts in a form that can be read and understood by citizens.
  • Public renderings may organise legal content into articles, sections, clauses, tables, formulas, examples, explanatory notes, and cross‑references. This organisation is for publication and interpretation unless legal significance is expressly encoded in the Legal Domain.
  • A human‑readable clause is a public textual unit associated with one or more Predica declarations, constraints, annotations, or non‑formal legal provisions.
  • Where a legal requirement is expressed in Predica, its formal compliance condition is defined by the Predica specification. Human‑readable text associated with that requirement shall explain the formal condition without altering it.
  • Where a legal requirement is not fully expressed in Predica, its human‑readable provision remains part of the Legal Domain and is interpreted by the judiciary according to this Constitution.
  • Clauses and annotations shall be narrow in scope. Large or multi‑topic blocks of text shall be divided into smaller units where doing so improves clarity, formalisation, or public readability.
  • The order of public text shall not affect legal meaning unless that ordering is expressly encoded in the Legal Domain.

Failure to meet these requirements, for example by drafting clauses that are overly broad, ambiguous, or structurally inappropriate, requires corrective action through Administrative Initiatives.