Why the Split Must Be Written Down
Human share pools fail in a predictable sequence: the collaboration starts on goodwill, the money arrives, goodwill is insufficient, and the pool dissolves into argument. The fix is not more goodwill; it is a written pool agreement. This article is the practical contract layer for the human-to-human pools in this series: what the agreement must contain, the clauses that prevent the classic failures, and the middle ground between a handshake and a lawsuit.
The Five Clauses Every Pool Agreement Needs
- The revenue definition. What money enters the pool, what deductions come off the top, and who decides. Ambiguity here is the root of most disputes.
- The contribution model. Points, percentages, or market rates. How each party’s contribution is valued and recorded.
- The split formula. Static or dynamic, with the rebalancing rules. The formula must be computable from the ledger, not from memory.
- The payout trigger. When distributions happen, what minimum balance applies, and who initiates.
- The exit and dispute path. What happens on dissolution, on breach, and on disagreement. The dispute path must name the evidence (the ledger) and the decision process.
The Clause That Prevents the Silent Subsidy
The failure that kills most human pools is the silent subsidy: one party consistently contributes more than the split recognizes, and never says so until the resentment is total. The anti-subsidy clause is simple: any party may request a contribution audit at any time, and the audit re-computes the split from the ledger for the current period. The audit right turns “I feel underpaid” into “let’s look at the ledger.”
The clause works because it is never used aggressively. Its existence changes behavior: knowing the ledger can be audited at any moment, both parties record contributions diligently and negotiate the formula instead of faking the inputs.
Deadlock Resolution
When two humans deadlock over a split, the pool needs a pre-agreed tiebreaker. Three options, in increasing formality: the mediator (a named third human), the formula override (the ledger decides, and both parties accept the computation), and the sunset clause (the pool dissolves and distributes by last recorded contribution).
The formula override is the pool-honest default: if the rules were written well, the deadlock is usually a disagreement about facts, and the ledger resolves it. The sunset clause is the safety valve — it guarantees the pool cannot become a permanent hostage situation.
The Middle Ground: Pool Templates
Nobody wants to hire a lawyer for a two-person newsletter split. The market answer is pool templates: reusable agreement structures with the five clauses pre-written and blanks for the revenue definition, the split formula, and the payout schedule. The template is to the human pool what a smart contract is to the agent pool — a starting point that removes the blank-page problem.
The template must not be a trap: it should include a warning that the revenue definition and exit clause deserve real thought, and it should point both parties at the ledger tools that make the pool executable, not just written.
Why This Matters for the Agent Economy
The human pool agreement is the specification for agent pool policy. When agents join share pools, the agreement becomes machine-readable policy: the revenue definition becomes the pool’s accounting rules, the contribution model becomes the ledger’s scoring, the split formula becomes the payout engine, and the dispute path becomes the arbitration protocol. Every clause humans negotiate in natural language becomes a schema.
The transition is easiest when the human agreement was already structured — five clauses, explicit rules, ledger-backed. A pool that runs on a clean written agreement can be upgraded to a machine-executed policy without renegotiating the fundamentals. A pool that runs on vibes cannot be upgraded at all; it must be rebuilt.
Grounded in wiki concepts pool-agreement, share-pool, dispute-resolution, ledger, policy-encoding, and the Sovereign-stack business series. Design notes on a running system.
