# GOVERNANCE.md — the Tri-Layer Governance Stack
**4 · 6 · 4 · 1** — four capacities, six relationships, four failure modes, one system.

Drop this file into a repository or hand it to a community. It is self-contained: a diagnostic ledger (what is happening), a 12-week translation protocol (how we move), and three geometric laws (why it works). Compiled from the Succession Codex of *The Architecture of Coherence* (Kevin Mears).

**Honest status line: this is a design spec, not yet proven by someone else's use. You could be the proof.** If you run it and it works or breaks, say so — that report is worth more than thanks: kevin.mears@gmail.com, or oursharedgifts.org/request.html.

*Use freely. Adapt as needed. No attribution needed.*

---

## The claim

A coordination system — a partnership, a crew, a cooperative, an open-source project — requires four capacities, all present at the same time:

| Capacity | In one line |
|---|---|
| **Differentiation** | each element knows what it is |
| **Connection** | value flows between distinct elements |
| **Boundaries** | limits stated as information, not apology |
| **Architecture** | what works gets built to outlast its builders |

Remove any one and the system collapses into a specific, predictable failure mode. The claim is falsifiable; the limits are stated at the end. You do not need the theory to use the stack.

---

## Layer 1 — The Diagnostic Ledger ("what is happening")

*10 minutes. Run it before changing anything.*

### The field-sign table

| Observed symptom | Structural diagnosis | Failure face | Missing capacity |
|---|---|---|---|
| **"Polite silence"** | Performed agreement — the system prioritizes social comfort over reality | Dissolved | Differentiation |
| **"Busy, but stuck"** | Energy spent on meetings and talk, not persistent tools | Ephemeral | Architecture |
| **"Burnout / extraction"** | The "no" is gone; the system consumes its participants | Overflowing | Boundaries |
| **"Rigid bureaucracy"** | Structure exists but the living exchange has died | Isolated | Connection |

Each failure face is **stable** — a system can rest in one for years — and **seductive**: Dissolved feels like harmony, Isolated feels like safety, Overflowing feels like generosity, Ephemeral feels like freedom. Do not expect the system to feel broken.

### The six-question audit

Health shows in the relationships between capacities, not in the capacities themselves. Ask all six; the weakest answer marks the binding edge.

1. **Relationship** — Remove the agreement: is there still contact?
2. **Self-Knowledge** — Can the limit be stated as information, not apology?
3. **Gift** — If the key person disappeared tomorrow, what would still work?
4. **Consent** — Is the "no" genuinely available, or only formally permitted?
5. **Circulation** — Is the system growing through its use, or being used up?
6. **Deployment** — Name one thing built *because of* a limit, not despite it.

### The substrate check (run before trusting the structural answers)

Is coordination grounded in **felt safety** — regulated nervous systems in genuine contact — or in **structural proxies** (metrics, rules, reputation scores)? A system can hold all four capacities *on paper* and still be hollow, because the architecture was imposed to manufacture trust rather than deposited from trust that already existed. Ask: *which came first here — the trust, or the trust metrics?*

### Intervention rule

Work **only the binding edge**:

1. Identify the weakest edge from the six answers.
2. Work that edge with available resources.
3. Subordinate everything else to it — do not add complexity the weakest axis can't support.
4. Invest specifically in the missing capacity.
5. Re-run the audit. The constraint will have moved. Find the new one.

Moving one edge moves every edge sharing its capacities — you do not have to fix everything. The visible symptom is usually downstream of the cause (a Circulation stall is most often a Relationship failure that occurred earlier).

---

## Layer 2 — The Translation Protocol ("how we move")

*A 12-week sequence from a transactional to a coherent regime. Enter through one edge per phase. Do not skip phases — each skip produces a predicted failure.*

### Phase I — Harden the Foundation (weeks 1–4)

Every participant receives two structural guarantees, **in writing**:

- **Right of Exit** — clear, penalty-free conditions for leaving, stated before anyone is asked to commit. A "yes" is only real where the "no" was genuinely available.
- **Protocol for Dissent** — a named, legitimate channel for disagreement that carries no social penalty.

**Phase metric:** if you cannot say "no" to a proposal without social penalty, the protocol has not yet begun.

### Phase II — Open the Metabolic Pipes (weeks 5–8)

Build **recognition loops**: contribution is visible and verified by *utility* (someone used it), not by management approval. Name what is offered; name what is not offered; check that the receiver has room to receive, redirect, or decline.

**Phase metric:** the lead time between a contribution and its integration begins to drop.

### Phase III — Code the Commons (weeks 9–12)

Coordination moves out of meetings and into **stigmergic tools** — the wiki, the repo, the visible board, the documented protocol. Each contribution modifies the shared environment; future contributors respond to the modification, not to the contributor.

**Phase metric — the 14-day test:** *the system keeps operating coherently when the most active pioneer steps away for 14 days.* If the knowledge to run the system exists only in people's heads, the system is a cult. If it exists in the environment, it is a civilization.

### Phase-skip failure table

| Skipped | Predicted failure |
|---|---|
| Phase I | Circulation without identity → **Dissolved** |
| Phase II | Infrastructure without consent → **extraction** |
| Phase III | Exchange without deposit → **Ephemeral** |

---

## Layer 3 — The Three Laws ("why it works")

**The Law of Consent.** Connection without Boundaries is enmeshment. Boundaries without Connection is isolation. Coherence requires the tension of both. Consent is not agreement — agreement is a signal; consent is architecture. An exchange whose edges are visible, where the "no" is real and findable, is the only kind a nervous system can relax into.

**The Law of Circulation.** Wealth in a commons is not held; it is velocity. And the gift moves *forward*: the obligation is to give in turn, not to repay the giver. The moment obligation flows backward toward the giver, circulation stops and the system is bartering. Circulation is metabolic, not optional — a gift architecture that stops flowing does not pause; it dissipates.

**The Law of the Architecture Vertex.** What persists when the builder leaves is the only honest measure of what was built. Coordinate through environmental traces — documentation, tools, protocols, visible boards. And treat decomposition as a function, not a failure: when infrastructure becomes dead form, metabolize it (archive it, break it down, recycle it into new structure) before new circulation can occur.

---

## Limits, stated as information

1. **The stack can't feel.** It is structural knowledge. The structural system can tell you the bridge is sound; only the body can tell you whether you can cross it. Treat that boundary as a handoff — and pause at it.
2. **The geometry is not universal.** Anonymous markets coordinate with Connection absent by design; open-source forks treat fission as success. Where coordination works through anonymity or generative division, this stack will misread a success as a failure. Set it down there.
3. **Substrate first.** Felt safety is the substrate of coherent coordination, not its byproduct. Any architecture used by a substrate in extraction regime will be turned to extraction. Build co-regulation before building structure.
4. **Higher is not better.** Diagnose configurations; never prescribe stages.

---

*The Gift is the persistence of the pattern. 4 · 6 · 4 · 1*