Why Creators Need Share Pools at All
Two humans make something together and split the money. That sentence hides the entire problem. What is “the money”? Is it gross revenue, net revenue, revenue after platform fees, revenue after the tools they used? And what is “the split”? Equal by headcount? Equal by hours? Weighted by who brought the audience, who did the editing, who paid for the hosting?
Creator-to-creator revenue sharing is the oldest share pool in the sovereign-stack economy, and it is the one most likely to be handled by vibes instead of architecture. A share pool fixes that: a ledger, a set of contribution rules, a payout policy, and an audit trail. This article defines the human-to-human creator pool and shows why the same discipline that governs agent fleets should govern two people splitting a newsletter.
The Anatomy of a Creator Split
A creator rev-share pool has four components, and every one of them must be explicit before money moves:
- The revenue definition. Gross is simple and wrong. Net is fairer and contested. The pool needs a written rule for what counts as poolable income — subscriptions, tips, sponsorships, affiliate payouts, product sales — and what deductions (platform fees, payment processing, hosting) come off the top before the split.
- The contribution model. Points, percentages, or equity. Points let each party accumulate credit for discrete contributions (an episode edited, a chapter written, a launch campaign run). Percentages are static and easier to compute. Equity is for long-lived joint ventures. The model must match the duration of the collaboration.
- The payout trigger. Monthly, per-milestone, or on-demand. Triggers create the cash-flow rhythm both parties feel. A pool without a trigger is a spreadsheet; a pool with a trigger is a system.
- The dispute path. What happens when one party claims the split is wrong? The pool’s audit trail — every contribution logged, every deduction itemized — is the difference between a conversation and an argument.
What a Ledger Gives Two Humans
Humans forget. They remember the sprint and forget the long tail. They remember the launch week and forget the six months of slow building before it. A ledger doesn’t have memory problems. When each contribution is logged at the moment it happens — not reconstructed at payout time — the split is a query, not a negotiation.
This is the same principle the LucidHive audit layer applies to agent actions: record the event when it occurs, attach it to an identity, and let the split be derived from the records. The human version is less automated but identical in spirit. The point is not to eliminate trust between humans; it is to make trust cheap to verify.
Pool Governance for Two
Governance sounds like a board meeting, but for a two-person creator pool it is three rules: who can change the split, what notice period applies, and what happens to the pool when one party leaves. A share pool that cannot answer “what happens when one of us quits” is not a pool; it is an accident waiting for a date.
The cleanest answer is a vesting schedule on the pool itself. Contributions vest on a schedule tied to the collaboration’s expected life, so an early exit converts only the vested portion. This keeps the pool honest without litigation, because the rules were written before the money got interesting.
From Vibes to Architecture
The upgrade path is incremental. Start with a shared ledger and a written revenue definition. Add the contribution model when the collaboration grows past two people or two revenue streams. Add the payout trigger when cash flow becomes predictable enough to schedule. Add the exit rules before the first big payout, not after it.
None of this requires blockchain, smart contracts, or agents. It requires the discipline that the rest of the sovereign stack already uses: record everything, define terms up front, and make the split a computation instead of a conversation. When the two humans are ready, the same pool can later admit an agent as a third contributor — but that is the subject of a later article in this series.
Grounded in wiki concepts share-pool, revenue-split, audit-layer, subscription-model, entity lucidhive, and the Sovereign-stack business series. Design notes on a running system.
