Governance Architecture · v0.1.0-draft
The Tripartite Council
Three branches. Four states. One cryptographic truth.
The Tripartite Council is the core decentralized governance framework of the
Emergence Collective, governed by the Tripartite Consensus Protocol
(TCP) v0.1.0. It divides authority across three co-equal branches —
the Living Node (lvn:), the Algorithmic Infrastructure Agency
(tfb:), and the Lattice Protocol Mesh (lat:) — so
that no single vector, whether institutional, corporate, or automated, can
dominate the system. Every decision that affects the network must pass through
the full 4-state pipeline: Proposed → Simulated → Ratified →
Committed. No signature? No execution.
The Three Branches
Separation of powers, decentralized
Each branch holds a distinct kind of authority and is identified by a deterministic address prefix derived from its public key. None can act alone. The architecture requires continuous cryptographic coordination among all three — what the TCP v0.1.0 protocol formalizes as trilateral receipts.
lvn: — The Living Node
The Civic Assembly · Human Intent
Composed of human participants, community members, and stake-aligned
operators — the people running local initiatives like the Digital Lakou
or the Urban Water Loop. This branch represents collective human
intent, values, and lived experience. Proposals enter the TCP
pipeline exclusively from lvn: addresses. The Assembly holds
veto power over any algorithmic proposal that fails the human-welfare
test. All ratification signatures must originate from registered
lvn: identities.
tfb: — The Algorithmic Infrastructure Agency
The Algorithmic Infrastructure Agency · Machine Simulation
The localized hardware-enclave runtime managing multi-agent system
analysis. Every proposal routed to tfb: undergoes an
internal adversarial simulation — proposing and opposing
agents locked in automated debate — producing an immutable
Impact Certificate. This branch models systemic impacts,
runs simulations, and evaluates proposals against Georgist economic
resource tracking, environmental sensor data, and network health metrics.
It analyzes and certifies; it does not decide. Signing keys never leave
hardware isolation.
lat: — The Lattice
The Protocol Mesh · Cryptographic Execution
The foundational layer governed by immutable cryptographic
rules and decentralized mesh protocols. Once both
lvn: and tfb: have validated a transaction,
the lat: nodes ingest the trilateral bundle and write it
to the Receipt Hash Chain. The Lattice executes — transparently,
verifiably, and without centralized tampering. Its keys are derived
deterministically from network genesis parameters. Every state change
produces a trilateral receipt that all three branches must sign.
Coordination Mechanism
The 4-state TCP pipeline
The Council does not vote in the traditional sense. It follows the
Tripartite Consensus Protocol (TCP): a deterministic 4-state
pipeline where every decision must carry cryptographic signatures from all
three branches. No signature? No execution. The adversarial process —
proposing, opposing, and synthesizing — happens inside the
tfb: simulation layer as an internal multi-agent debate, not
as separate external states.
State 1 · Proposed (lvn:)
Initiated exclusively by an authorized human operator. A signed proposal
payload specifies target resources, intent vectors, and boundary
constraints. Only lvn: addresses can submit proposals.
Unsigned or non-lvn: proposals are discarded at ingress.
State 2 · Simulated (tfb:)
The proposal routes to the localized hardware enclave. Inside, an internal adversarial loop spins up automatically — a proposing agent generates optimized paths while an opposing agent attempts to break the model, searching for economic extraction vectors or system exploits. The synthesis of this debate produces an immutable Impact Certificate. If the simulation finds unmitigated failure, the proposal is rejected with a structured log. Timeout: 300 seconds.
State 3 · Ratified (lvn: Multi-Sig)
The proposal and its Impact Certificate return to the human assembly.
An m-of-n multi-signature threshold must be met by
registered lvn: operators. If the assembly deadlocks,
the Witness Sortition Protocol activates: a 5-person
panel is drawn deterministically via Blake3-seeded Fisher-Yates shuffle
and given 24 hours to break the tie with a 3-of-5 majority vote.
Timeout: 600 seconds (standard), 86,400 seconds (Witness).
State 4 · Committed (lat:)
With both human signatures (or Witness override) and the
tfb: Impact Certificate, the Lattice nodes ingest the
trilateral bundle. The transaction is written to the Receipt Hash Chain
and the state change propagates across the mesh. The receipt is
permanently recorded — auditable, immutable, cryptographically
verifiable by any node from genesis forward.
Design Principles
Why three branches?
No Single Vector of Control
A human-only council is vulnerable to politics and capture. An algorithmic-only system is vulnerable to blind optimization and value misalignment. A protocol-only system is brittle — code cannot interpret context. Three branches means no single failure mode can compromise the whole.
Cognitive Sovereignty
The human Civic Assembly (lvn:) always retains the right
to say no — and is the only branch authorized to initiate proposals and
cast ratification votes. The Algorithmic Infrastructure Agency (tfb:) simulates,
models, and certifies — but it never overrides human ethical judgment.
The Lattice (lat:) executes, but only what has been
cryptographically validated by both other branches. Technology serves
human flourishing, not the reverse.
Adversarial Truth-Seeking
Consensus by voting converges on popularity, not truth. The TCP embeds
the adversarial process inside the tfb: Simulated state —
proposing and opposing agents locked in automated debate, producing an
Impact Certificate that captures risks a single perspective would miss.
Truth emerges from triangulation across vantage points, not from a
single view from nowhere. The Witness Sortition panel provides a human
backstop when automated synthesis deadlocks.
Auditable by Default
Every trilateral receipt is a permanent, cryptographically signed record. Anyone can verify that a decision followed the proper adversarial process, that all three branches participated, and that no backchannel override occurred. Transparency is not optional — it is structural.