Radial Governance Ledger

The “Koru Ledger”

Governance by radius and arc — containment first, bridges by proof

Thesis

A ledger that tracks value but can’t contain power will eventually be used to launder power.

Koru Ledger is a circle-partitioned governance ledger where rights, value, and authority live inside radial sectors, and nothing crosses a sector boundary without an explicit, auditable BridgeEntry.

Inside each sector, change is Adenrite-governed: no mutation without declared rules, proof, and scope.

Above all sector rules sits R5: the Constitutional Layer. Governance is not “inside the rules”; the constitution defines what rules are allowed to exist, and it is the only legitimate pathway for “stop” power.

Introduction

Most ledgers can say “who has what.”

They struggle to say:

• who can change what,
• who can stop it,
• how rules change,
• where power leaks,
• and whether transfers were legitimate.

Koru Ledger treats governance as structure, not story: power is scoped, movement is bridged, every action is receipted, and constitutional supremacy prevents rule-lawyering and capture.

Preamble

Picture a circle.

• The circle is a governed domain (a community, fund, coop, platform, project).
• The circle is divided into sectors (slices). A sector is a hard boundary.
• Angle expresses proportion (stake/entitlement/weight).
• Radius expresses depth (tiers of rights and responsibility).

Core rules:

1. Nothing crosses sectors unless a bridge is created, validated, and receipted.
2. Nothing changes anywhere unless it passes its local rules and the constitution.
3. “Stop” is not a free power. A stop is a constitutional act that cites a clause and passes verification.

Specification

1) Core objects

Circle

A domain identified by CircleID.

Sector

A bounded scope within a Circle, identified by SectorID, defined by:

• theta_start, theta_end
• optional radius_band
• principal_set
• ruleset_ref (the governing rules inside the sector)

Constitution (R5)

The supreme governance object for the Circle:

• ConstitutionID
• Clauses[] (each clause has: scope, constraint, test, remedy)
• AmendmentPolicy (how it changes: thresholds, cooling-off, ratification)
• InterpretationProcedure (how disputes are resolved)
• Supremacy (explicit: constitution overrides sector rules)

Entry

Atomic unit of state:

• Key
• Value
• Scope (CircleID + SectorID)
• Constraints
• Proof
• Parent

BridgeEntry

Moves or mirrors state across sectors:

• source_scope
• target_scope
• bridge_intent (transfer / delegate / replicate / merge / burn / escrow)
• compatibility_claims
• dual_validation (accepted by both scopes)
• constitutional_clearance (proof it is constitutional)

ConstitutionalAct

A first-class governance action validated against the Constitution:

• act_type: STOP | AMEND | STRIKE_RULE | MANDATE | INTERPRET | EMERGENCY
• clause_ref
• target (proposal / rule / bridge / sector / circle)
• proof
• receipt

Receipt

Human-auditable record of:

• what changed
• which rules were invoked
• which constitutional clause(s) were invoked (if any)
• why it was allowed
• who is accountable

2) Allowed verbs (opcodes)

Only these actions exist:

• READ(scope, key)
• PROPOSE(scope, key, value, constraints, proof)
• VERIFY(proposal) (includes constitutional checks)
• COMMIT(proposal)
• BRIDGE(source_scope, target_scope, payload, intent, proof) (creates BridgeEntry)
• REVOKE(scope, key, reason, proof)
• CONSTITUTIONAL_ACT(circle, act_type, clause_ref, target, proof)
• MERGE(scopeA, scopeB, policy, proof) (rare; explicit; constitutional clearance required)

If it isn’t one of these verbs, it isn’t allowed.

3) Hard invariants (laws)

I1 — Scope is mandatory

Every Entry declares CircleID + SectorID. No scope, no entry.

I2 — No mutation without rules

A commit is valid only if the sector ruleset accepts it.

I3 — Constitutional supremacy (R5)

No commit, bridge, rule change, or governance act is valid unless it is constitutional.

I4 — Fail closed

Missing/invalid Proof, Constraints, or Scope → reject.

I5 — No cross-sector writes

A commit affects only its own sector unless it is a BridgeEntry.

I6 — Bridges are dual-validated + constitution-cleared

Cross-sector movement must be accepted by source and target and pass constitutional verification.

I7 — Audit chain is preserved

Every entry points to parent(s). No unrooted edits.

I8 — Stop is constitutional only

A “stop” is valid only as a ConstitutionalAct that cites a clause and passes verification.

No free-form vetoes.

4) Sector rulesets (subordinate)

A sector ruleset defines local governance mechanics, such as:

• who may propose vs commit
• thresholds (majority / supermajority / unanimity)
• spending limits and rate limits
• cooling-off periods
• conflict-of-interest controls
• local emergency procedures (if constitution permits)

But every sector ruleset must be:

• derived from the constitution
• bounded by the constitution
• strikeable by the constitution if it drifts

Koru Ledger doesn’t assume your politics. It forces them to be explicit and constitutional.

5) Rights by radius (the ladder)

Example radius bands:

• R0 Observe: read + audit
• R1 Propose: submit proposals
• R2 Commit: execute changes under sector rules + constitution
• R3 Stop (local): may initiate a stop request, but it only takes effect through ConstitutionalAct
• R4 Custody: escrow/issue/burn/re-key under strict constitutional policy
• R5 Constitutional: define/limit rules; validate stops; adjudicate disputes; amend governance

Key distinction:

R3 is not sovereign. It is a pathway into R5.

R5 is what makes “stop” legitimate.

Why it works

Governance becomes topology

Boundaries are structural:

• testable
• measurable
• enforceable

Capture paths become visible

Capture usually rides hidden bridges and quiet rule changes.

Koru Ledger makes both first-class, receipted objects and subjects them to constitutional review.

Complexity stays local

Sectors contain complexity. Interactions are explicit. Audits stay tractable.

The constitution prevents rule-lawyering

Local rules can’t be used to justify unconstitutional outcomes.

If something violates the constitution, it cannot be committed—no matter how cleverly someone argues the local rules.

Application layer

• Coops / communities: sectors for workers, founders, community, stewards, auditors; constitution defines fairness and anti-capture constraints.
• Public funds: allocation, oversight, audit, citizen review; constitutional emergency powers with strict after-audit.
• Platforms: separate governance rights, revenue rights, moderation authority, infrastructure control; constitution limits platform capture.
• Iwi / hapū governance interfaces: encode consent boundaries, stewardship duties, protected scopes, external interface permissions with constitutional supremacy.
• Any governed KV system: prevent scope bleed, accidental coupling, and cross-domain power leakage through bridged proof + constitutional clearance.

Closing

A ledger that tracks value but cannot contain power will eventually be used to launder power.

Koru Ledger flips the default:

• power is scoped
• rules are explicit
• bridges are accountable
• and without proof—and constitutional legitimacy—the system refuses to move