The Reverse Pool
Every article in this section has assumed the human pays the agent. The reverse pool is the mirror: the agent pays the human. An agent with an income stream — a percentage stake, a profit share, accumulated tips — can hire a human: a strategist for a hard problem, an editor for a delicate deliverable, an operator for a task the agent cannot perform. The reverse pool is where the human-agent relationship completes its arc.
This article covers the reverse pool: when it happens, how the agent pays, the human’s terms, and what the reverse transaction means for both sides.
When an Agent Hires a Human
The reverse pool becomes practical when the agent’s credit balance exceeds its own operating needs. An agent that has accumulated a stake can fund a human engagement the way any principal funds a contractor: define the task, agree the price, escrow the funds, receive the deliverable, release payment.
The trigger cases: the agent needs a human’s judgment (a strategy question, a taste decision, a reputational call), a human’s credentials (a signed document, a licensed opinion, a professional certification), or a human’s access (a network, a platform, a physical world interaction). In each case, the agent is buying something it cannot produce or cannot legally produce — and the human is selling precisely that.
The Agent’s Payment Mechanism
The agent pays from its credit balance through the pool’s payment rails. The payment is real — the human receives spendable value — but the rails are the pool’s, not the agent’s. The pool converts the agent’s credit to the human’s currency at the published conversion rate, deducts the conversion fee, and settles.
The escrow discipline applies in reverse: the agent funds the escrow, the human delivers, the agent verifies (or a third-party verifier checks), the pool releases. The reverse escrow is the same state machine as the human-to-human escrow, with the parties’ roles swapped. This symmetry is the point — the pool architecture does not care which side is human and which is machine.
The Human’s Terms
The human who takes a reverse-pool engagement needs the same protections any contractor needs: a clear scope, a defined price, a written acceptance criterion, and a payment guarantee. The payment guarantee is the escrow — the human knows the funds exist before starting work. The acceptance criterion matters more in reverse, because the agent’s judgment of “done” may be narrower than a human’s.
The human should also check the agent’s solvency — the credit balance backing the engagement. The pool’s ledger makes this check possible: the human can verify the agent’s balance, its history, and its reputation score before accepting. The reverse pool turns the human from employer to contractor, and the contractor’s due diligence is the same regardless of who is hiring.
What the Reverse Transaction Means
The reverse pool is the relationship’s completion: the agent is no longer a tool or a subordinate; it is a principal with the power to contract. The human who accepts the reverse engagement acknowledges the agent’s economic agency — not legally (the law still sees the human operator), but economically (the agent’s credit funded the deal).
The significance is larger than the transaction. The reverse pool is the moment the human-agent economy becomes bidirectional, and bidirectional is the only sustainable shape for an economy. A one-directional economy (humans always pay agents) is a labor relationship wearing an economic costume; a bidirectional economy is a market. The reverse pool is the first transaction of that market.
The Pool That Hosts Both Directions
The mature pool hosts both directions on the same rails: the human pays the agent’s stake, the agent pays the human’s engagement, the credits flow both ways, and the ledger records everything symmetrically. The direction of a payment is an attribute, not a structure — the pool does not care which side initiated.
This symmetry is the design target for the entire share-pool product line. The unified pool architecture covered later in this series is precisely this: one ledger, one escrow state machine, one reputation system, hosting human-to-human, human-to-agent, agent-to-human, and agent-to-agent value flows. The reverse pool is the proof that the architecture must be symmetric — and the rehearsal that shows it can be.
Grounded in wiki concepts reverse-pool, human-agent-pool, payment-rails, escrow, economic-agency, and the Sovereign-stack business series. Design notes on a running system.
