Layer 2 · Governance
1 Decision Matrix
- Layer: 2 — Governance & Decision Logic
- Status: Stub — not yet adopted
- RCOS reference: §4.2, §4.4, §4.7
Maps every decision type and domain to an authorized role or body, mechanism, threshold, and escalation path. Decisions made outside this matrix are considered invalid.
Consensus Principles
RCOS definition4.2.1, 4.2.3, 4.2.4
- 4.2.1 Each decision type MUST have an explicitly defined decision-making mechanism.
- 4.2.3 Decision mechanisms MUST specify:
- 4.2.4 No informal or ad hoc decision mechanism MAY be used for collective decisions.
Why pin down mechanism, threshold, and timing?
A decision process without a predefined mechanism, threshold, and review window is an invitation to manufacture outcomes after the fact. Declaring these parameters in advance makes every collective decision reproducible and contestable on the same terms, whether members are present in the meeting or consenting through the absentia review period.
<Consensus method, voting power rules, formal threshold, absentee review period, and informal decision process — to be defined.>
Matrix
RCOS definition4.4.1, 4.4.2, 4.4.3, 4.4.4
- 4.4.1 The community MUST maintain a Decision Matrix as a core governance artifact.
- 4.4.2 The Decision Matrix MUST map, at minimum:
- 4.4.3 The Decision Matrix MUST be publicly accessible to all members.
- 4.4.4 Decisions made outside the Decision Matrix MUST be considered invalid.
Why a single authoritative matrix?
If the rules for who decides what live in people’s heads, authority becomes whatever the loudest or most senior person says it is. A public matrix that binds every decision to a domain, body, mechanism, and threshold makes out-of-scope action visible the moment it happens — and makes any decision made outside it invalid by construction.
| Decision Domain | Decision Type | Authorized Body | Eligible Participants | Mechanism | Threshold | Blocking / Veto conditions | Escalation |
|---|---|---|---|---|---|---|---|
Decision Type Definitions
RCOS definition4.1.1, 4.1.2, 4.1.3, 4.1.4, 4.1.5
- 4.1.1 All collective decisions MUST be classified into exactly one of the following decision types:
- 4.1.2 Operational Decisions concern day-to-day functioning and execution within existing rules.
- 4.1.3 Strategic Decisions concern long-term direction, allocation of significant resources, or creation/removal of major structures.
- 4.1.4 Constitutional Decisions concern changes to Layer 0 invariants, purpose, scope, or the governance system itself.
- 4.1.5 If a decision cannot be clearly classified, it MUST default to the higher-impact decision type.
Why classify every decision?
Without a type, every decision gets handled at whatever speed and scrutiny happens to suit the moment — routine changes stall in debate, and constitutional shifts slip through unnoticed. Fixed types tie the weight of a decision to the process it must pass through, and the default-higher rule closes the gap where ambiguity would otherwise be exploited.
- Operational — Day-to-day functioning within existing rules.
- Strategic — Long-term direction, significant resource allocation, creation or removal of major structures.
- Constitutional — Changes to Layer 0 or the governance system itself.
If a decision cannot be clearly classified, it defaults to the higher-impact type.
Ratification Record
- Adopted:
- Decision type: Constitutional
- Version:
- Decision record: