Agreements

Explicit, programmable commitments between holons and their members

In the Holons protocol, agreements are the explicit contracts that make a holon's coordination legible. They describe who has committed to what, with whom, under which conditions, and how the result will be tracked.

Where casual coordination relies on shared memory and trust, holonic agreements turn intentions into structured records that can be referenced, validated, and acted on by both humans and contracts. This is what makes it possible for autonomous holons to collaborate across organizational boundaries without giving up their independence.

What an agreement looks like

A holonic agreement typically captures:

• The parties. Which holons or individuals are involved.

• The purpose. What the agreement is for, in the holon's own terms.

• The contributions and flows. What resources move, in which direction, under what rules.

• The value system. Which contributions are recognized, and how they are weighted in the value equation.

• The governance. How decisions are made and how conflicts are resolved.

• The duration and review. When the agreement starts, when it is revisited, and how it can change.

These same elements show up at every scale—from a two-person Memorandum of Understanding to a federation contract spanning many holons.

Where agreements live

Agreements operate on two layers:

• Human-readable text — the kind of document people sign. The Memorandum of Understanding is a canonical example and a useful starting template.

• Programmable contracts — the on-chain or off-chain records that enforce flow, track commitments, and update reputation. These are managed by the Commitment Registry and related primitives described in Funding Flow.

A working holon usually has both: a written agreement that members can read and discuss, paired with the corresponding contract configuration that makes the agreement enforceable in practice.

Where to go next

• Memorandum of Understanding — a template agreement for participants collaborating on THEOS.

• Funding Flow — the primitives (Commitment Registry, splitters, thresholds, federation contracts) that make agreements programmable.

• Setting up your holonic organization — how to start a holon whose agreements are operationalized through the HolonsBot.