Memo 01 — Political Systems

Memo 01 — Political Systems as Norm-Generating Machines

Figure 1.1 — Constituent vs constituted power
flowchart TD CP[Constituent power / founding act]:::root -->|CONSTITUTES| C[Constitution]:::n C -->|LEGISLATES| L[Legislation]:::n C -->|DELEGATES| R[Regulation]:::n Courts[Courts]:::alt -->|ADJUDICATES / precedent| L L -->|refines| R classDef root fill:#3a1730,stroke:#b5468f,color:#ffd6f0; classDef n fill:#16233d,stroke:#2f4670,color:#cfe0ff; classDef alt fill:#12351f,stroke:#2f9e5e,color:#d6ffe4;

Series: The Landscape of Normative Systems (LNS) Series ID: LNS Memo number: 01 Primary JD questions: Q6 (how political systems generate law), Q7 (relations among Politics/Law/Power/Legitimacy/Authority). Secondary: Q1, Q2, Q4. Status of D0: Immutable. Referenced as a frozen interface; not modified, criticized, or defended in this memo.


Scope note

This memo treats the political system as a norm-generating machine: a device that takes some set of inputs (proposals, preferences, claims of authority) and emits norms — primarily the class of norms called law — through a characteristic aggregation/decision function, on a characteristic update cadence, under a characteristic legitimacy claim, and with a characteristic enforcement path and mutation mechanism. The memo compares ten families of political system (democracy, constitutional republic, authoritarian systems, communism/one-party states, monarchy, theocracy, tribal systems, federations, the European Union, and international organizations) along computational dimensions, provides a comparison table, and develops the Politics -> Constitution -> Law sub-graph that Memo 12 extends. It applies the six-part per-source analysis (origin / legitimacy / enforcement / mutation / hierarchy / conflicts / computational implications) to political authority as a source. It is strictly descriptive: it characterizes computational behavior and refrains from ranking systems or expressing political preference, per §0.7 of the conventions. Deeper treatment of international organizations and the EU continues in Memo 08; jurisprudential machinery (Hart, Dworkin) is in Memo 02; mutation dynamics and feedback loops in Memo 09.


1. Framing: the political system as a machine

We adopt a deliberately mechanical vocabulary. This is a modeling choice under M4 (natural language is presentation; we seek computational objects beneath it), not a metaphysical claim that political systems are nothing but machines.

A norm-generating machine NGM is characterized by the tuple:

$$\text{NGM} = \langle\, I,\ S,\ A,\ C,\ L,\ E,\ M,\ H \,\rangle$$

Symbol Component Meaning
$I$ Input set who/what has STANDING to propose or trigger a norm
$S$ State the current norm set + institutional configuration
$A$ Aggregation fn how inputs + state map to an output norm $(I \times S \to \text{norm})$
$C$ Cadence when $A$ is allowed to fire (event-driven / periodic / continuous)
$L$ Legitimacy claim the asserted ground on which outputs are treated as binding
$E$ Enforcement path how deviation is detected and consequences applied
$M$ Mutation mechanism how $A$, $I$, $S$, and the machine itself are changed
$H$ Hierarchy ordering of outputs and of the machine relative to others

INFERENCE Every political system can be described by instantiating this tuple. This is an organizing hypothesis for the memo, not a proven completeness result; its adequacy is stress-tested in Memo 10 (taxonomy) and Memo 11 (threats).

Three cross-cutting distinctions from the shared vocabulary (§0.6) are load-bearing throughout:

FACT These three can dissociate: a norm can be valid but not efficacious (dead-letter law), efficacious but not legitimate (compliance from fear), or legitimate but invalid (a widely accepted practice not yet formalized). The tri-partite distinction is standard in general jurisprudence and is developed in Memo 02. INFERENCE For a compiler, these are three separate observables that must not be collapsed into one "is-in-force" bit.

1.1 What "generate a law" means here

INFERENCE "Generating a law" is the event in which the machine's aggregation function A fires and commits a new norm (or repeals/edits one) into state S with a validity stamp. The content of the law lives above the kernel (Memo 08, JD Q8); what this memo characterizes is the production process — the control flow of the machine — which is comparatively more content-neutral and therefore of direct interest to D1/D2.


2. Established consensus

Claims in this section are broadly agreed within comparative politics, constitutional theory, and general jurisprudence. They are tagged individually; consensus does not upgrade a claim past what its evidence supports.

2.1 On sources and law-production

2.2 On legitimacy, authority, and power (JD Q7 primitives)

2.3 On aggregation and its limits

2.4 On feasibility of computing the whole thing


3. The ten families of political system

Each subsection instantiates the NGM tuple. Descriptions are of idealized types; FACT real states are hybrids and rarely instantiate one type purely. Tags apply to the descriptive claims; normative/ranking claims are deliberately absent (§0.7).

3.1 Democracy (direct / representative)

3.2 Constitutional republic

Treated separately from bare democracy because the distinguishing feature is computational, not merely nominal.

3.3 Authoritarian systems

3.4 Communism / one-party states

Kept distinct from generic authoritarianism because the architecture of the input node differs. Described structurally, not evaluatively.

3.5 Monarchy (absolute and constitutional)

3.6 Theocracy

3.7 Tribal systems

3.8 Federations

Federations are not a fourth branch but a composition operator: they compose multiple NGMs (member units) with a shared one (the federal level).

3.9 The European Union (supranational, sui generis)

3.10 International organizations and international law

4. Comparison table along computational dimensions

Dimensions: Input set (breadth of standing), Aggregation function, Determinism (same inputs → same output?), Latency (input-to-committed-norm), Reversibility (ease of repeal through in-band channels), Veto structure, Error-correction (in-band channel to overrule a bad output/author).

INFERENCE All cells describe the idealized type and are relative, ordinal judgments about mechanism, not measurements and not evaluations of merit (§0.7). Real systems are hybrids (§3 preamble).

System Input set (standing) Aggregation fn Determinism Latency Reversibility Veto structure Error-correction (in-band)
Direct democracy broad (citizens) majority vote low med high few formal vetoes referendum / re-vote
Repr. democracy broad via reps vote (2-level) low med-high high chamber(s), exec veto periodic election
Const. republic broad + entrenched vote + validity check low-med med-high asymmetric * courts, chambers, exec election + judicial review
Authoritarian narrow (ruler/clique) decree high ** low low (in-band) ruler = single veto point weak / out-of-band only
Communist 1-party party organs centralism (agg+lock) high ** low-med low (in-band) party apex internal to party
Absolute monarchy monarch decree high ** low low (in-band) monarch = single veto weak / out-of-band
Const. monarchy parliament vote + assent low med-high high chambers; crown ~ceremonial periodic election
Theocracy authorized interp. revelation-mediated med *** med (rulings) low (base) doctrinal gatekeepers reinterpretation / schism
Tribal system kin/elders/council consensus med high (deliber.) med (drift) any-member objection (~) council reform / desuetude
Federation multi-order gov'ts vote + conflict rule low med-high high (scoped) member vetoes, umpire court courts + elections per order
European Union Commission/Council/EP co-decision + QMV/unan low high med (scoped) unanimity areas, member veto CJEU + EP election + treaty
Intl. orgs / law states (consent) treaty/custom/decision low-med very high (cust) low (consent) sovereign veto; council veto dispute settlement (consented)

Notes:

Symbol Note
* Asymmetric reversibility: ordinary statute easily reversed; entrenched constitutional norms deliberately hard to reverse (two-speed mutation).
** "High determinism" is conditional on a fixed single/apex preference: given the ruler's or party's preference, output is predictable; it says nothing about stability of that preference over time. Vote-based systems are low-determinism because coalition formation is path-dependent (§2.3).
*** Theocracy: derivation from a fixed corpus is more determinate than a vote, but interpretive latitude introduces non-determinism at the ruling layer.
~ Tribal "veto": in consensus systems a sustained objection can block, which functions as a distributed veto rather than a positional one.

INFERENCE Reading the table structurally rather than politically, three orthogonal axes emerge:

  1. Width of the input set (single-writer → multi-writer → whole-population).
  2. Aggregation type (decree / vote / consensus / revelation-mediated / consent-contract) — these are genuinely different functions, not points on one scale.
  3. Presence and speed of an in-band error-correction channel (from "none, only coup/succession" to "scheduled election + judicial review").

HYPOTHESIS These three axes may be closer to the "computational primitives" of political norm-generation than the traditional regime-type labels are, because regime labels bundle content (ideology) with mechanism, whereas the axes isolate mechanism. This is offered for the taxonomy work in Memo 10, not asserted.


5. The Politics -> Constitution -> Law sub-graph

This is the core dependency structure JD Q4 asks the series to build; Memo 12 extends it downward (Regulation → Procedure → JD → KPI) and Memo 09 adds the feedback edges. Here we give the upper sub-graph with its edge semantics.

Diagram
flowchart TD CP["CONSTITUENT POWER
(people / founders / revolution / conquest)
the power to make/replace the machine's own definition"]:::root CONST["CONSTITUTION
highest-ranked norm; higher-order / secondary rules;
defines organs, competences, amendment rule, rights"]:::n POL["POLITICS
(organs: legislature, executive)"]:::n ELEC["ELECTORATE / SELECTORATE
(staffs the legislature; narrow/absent in non-elective types)"]:::alt LAW["LAW
(statutes: primary rules)"]:::n REVIEW["CONSTITUTIONAL REVIEW
(type-checker that can void invalid statutes)"]:::alt NEXT["Regulation → Procedure → Job Description → KPI
(continues in Memo 12)"]:::ext CP -->|"CONSTITUTES: writes the rule of recognition; sets I, A, C, H"| CONST CONST -->|"AUTHORIZES / CONSTRAINS (grants + bounds law-making power)"| POL ELEC -->|"selects"| POL POL -->|"LEGISLATES: A fires, aggregate inputs → candidate norm"| LAW LAW -.->|"submitted for validity check"| REVIEW REVIEW -.->|"reject / void if invalid"| LAW LAW -->|"DELEGATES / EMPOWERS"| NEXT classDef root fill:#3a1730,stroke:#b5468f,color:#ffd6f0; classDef n fill:#16233d,stroke:#2f4670,color:#cfe0ff; classDef alt fill:#12351f,stroke:#2f9e5e,color:#d6ffe4; classDef ext fill:#2b2a12,stroke:#c9a92f,color:#f0e6c0;

Edge semantics (the load-bearing part for D1/D2):

FACT Not every system instantiates every node: pure §3.3/§3.5-absolute systems collapse ELECTORATE and much of CONSTITUTION into the ruler node; §3.6 replaces CONSTITUENT POWER with a sacred source treated as read-only; §3.8–3.10 replicate the LAW node across multiple scoped hierarchies joined by conflict rules. INFERENCE The graph is therefore a template; each regime type is a specific wiring (or short-circuit) of it.

6. Six-part analysis: political authority as a source

Per JD Q2 and the conventions, each source treated in the series receives the six-part analysis. Here the source is political authority — the general capacity of a political system to emit binding norms. (Constitutions, legislation, and treaties are specific instruments of this source; other sources — revelation, contract, custom, science — are the subject of Memos 04–06.)

6.1 Origin

6.2 Legitimacy

6.3 Enforcement mechanism

6.4 Mutation mechanism

6.5 Hierarchy

6.6 Conflicts

6.7 Computational implications (of political authority as a source)

7. Relations among Politics / Power / Legitimacy / Authority / Trust / Law (JD Q7, political slice)

JD Q7 asks for the relations among a larger set (Politics, Law, Ethics, Religion, Culture, Economics, Markets, Technology, Organizations, Power, Legitimacy, Authority, Trust, Incentives). This memo owns the political core of that graph; Ethics→Memo 03, Religion→Memo 04, Economics/Markets→Memo 05, Culture/Society→Memo 06, Organizations→Memo 07, and the full merged graph→Memo 12.

Political core dependency sketch (arrows read "contributes to / conditions"):

Diagram
flowchart TD POWER["POWER
(capacity to affect outcomes; raw, pre-normative)"]:::sub LEGIT["LEGITIMACY
(subjects accept as binding without coercion)"]:::sub TRUST["TRUST
(expectation of future behavior; lowers enforcement cost E)"]:::sub AUTH["AUTHORITY
(recognized standing to issue binding norms)"]:::n POL["POLITICS
(organs running A)"]:::n LAW["LAW"]:::n SOC["SOCIETY / SUBJECTS"]:::n ENF["ENFORCEMENT (E)
(uses POWER, legitimated by L)"]:::alt LEGIT -->|"confers"| AUTH AUTH -->|"exercises"| POL POL -->|"LEGISLATES"| LAW LAW -->|"binds"| SOC SOC -->|"selects (elections)"| POL ENF -->|"applies consequences"| SOC SOC -->|"compliance"| ENF POWER -->|"raw capacity"| ENF ENF -->|"efficacy"| TRUST TRUST -->|"raises / lowers"| LEGIT classDef sub fill:#2b2a12,stroke:#c9a92f,color:#f0e6c0; classDef n fill:#16233d,stroke:#2f4670,color:#cfe0ff; classDef alt fill:#12351f,stroke:#2f9e5e,color:#d6ffe4;

Read-outs (all INFERENCE unless noted):

HYPOTHESIS The political core reduces to four separable observables — a capacity channel (power), a standing predicate (authority = power + legitimacy recognition), an acceptance measure (legitimacy/trust), and a production function (politics → law). If separable, D1/D2 can model each with a distinct type. Offered for Memo 12, not asserted.


8. Competing theories (presented without adjudication)

Per §0.5, live disagreements are logged, not resolved. Attribution follows §0.4 (name a position only when safe).


9. Open questions

Per §0.5 / §0.4, problems this memo cannot resolve and that D1/D2 must treat as unresolved.


10. Research opportunities (for D1/D2)

Per §0.5, where the compiler work could contribute or must decide.


11. Handoff to D1/D2

Concrete implications for the compiler architects (all INFERENCE unless noted):

  1. Norm provenance. Every norm object should record its generator (vote | decree | consensus | revelation_mediated | consent_contract | custom), because determinism, manipulability, and failure modes follow from the generator, not the content.
  2. Three-field status. Replace any single "in force" boolean with { validity, legitimacy, efficacy }; treat legitimacy and efficacy as exogenous, measured, noisy inputs (no agreed metric — §6.2/§9).
  3. Two operation classes. Provide distinct operations for constituted changes (legislate/regulate — run the machine) and constituent changes (amend/replace — edit the machine). Out-of-band mutation (coup/revolution) is a discontinuity that resets the instance, not a modeled transition.
  4. Conflict resolution as pluggable predicate. Implement lex superior / posterior / specialis as deterministic tie-breakers over a partial order; allow scope-restricted supremacy (federation/EU primacy) and a first-class UNRESOLVED result for no-shared-apex conflicts (§6.6/§9).
  5. Enforcement as an attachable subsystem with strength/topology metadata (centralized / dual / delegated / decentralized-social / weak-horizontal / none), never assumed present.
  6. Cadence and veto as machine parameters. Model update cadence (event-driven / periodic / continuous) and veto structure (single-point / chamber / member-unanimity / distributed-consensus) explicitly; they determine latency and reversibility.
  7. Error-correction channel as an explicit edge. Record whether an in-band channel exists to overrule an author/output (election, judicial review, internal-party, referendum) or whether correction is only out-of-band. This is the sharpest structural discriminator among §3 systems.
  8. Honesty constraints (M1/M6). The compiler must be able to represent an incoherent-but-valid aggregation output, an undecidable exception, and an unresolved cross-system conflict — surfacing them rather than fabricating resolution.

FACT , per §0.2 D0 is treated as a frozen interface throughout; nothing above prescribes changes to the kernel. These are inputs the layer above the kernel must supply and the interface (Memo 12) must be able to receive.


End of Memo 01. Cross-references: Memo 02 (validity/interpretation, Hart/Dworkin/ Kelsen), Memo 08 (EU and international organizations in depth), Memo 09 (mutation dynamics and feedback loops), Memo 10 (generator taxonomy), Memo 11 (Schmitt/ Hayek threats to computability), Memo 12 (merged Q7 graph and the invariant interface).