The Pools as Storefronts
The shop.lucidhive.com marketplace and the share pools are two halves of one system: the marketplace is where value is exchanged, and the pools are where value is shared. The marketplace’s transactions feed the pools’ contributions; the pools’ splits fund the marketplace’s purchases. The integration is the point where the share-pool series becomes a business — the shop is the storefront, and the pools are the economics behind it.
This article covers the pool-shop integration: the storefront pools, the split-visible checkout, the marketplace’s two-species future, and the integration as the LucidHive stack’s commerce layer.
The Storefront Pools
Every storefront on the shop marketplace can run a pool behind it: the storefront’s revenue flows into a pool, the pool’s split formula distributes it across the contributors — the creator, the agents that produced the goods, the marketing, the infrastructure. The storefront pool makes the storefront’s economics visible: the customer sees the price; the contributors see the split.
The storefront pool’s design follows the pool types this series has covered: a solo creator runs a simple pool (the creator’s share, the platform’s fee, the operating costs); a studio storefront runs a mixed pool (the humans’ direction, the agents’ production); a marketplace vendor runs a cost pool (the production, the fulfillment, the margin). The storefront pool is the product line’s entry point — the easiest pool for a new customer to understand, because it is attached to something they already sell.
The Split-Visible Checkout
The integration’s customer-facing feature is the split-visible checkout: the customer sees, at purchase time, how the price distributes — the creator’s share, the platform’s fee, the contributors’ cuts. The split-visible checkout is the shop’s transparency feature, and it is the direct expression of the auditability principle in the commerce layer: the customer knows where their money goes.
The split visibility is not for every purchase — a commodity product’s checkout does not need a pie chart. It matters for the purchases where the split is part of the value: the creator’s products (the customer supports the creator deliberately), the co-op products (the customer buys into the pool’s fairness), the studio products (the customer sees the human-agent mix). The split-visible checkout is a feature, not a mandate — it appears where the transparency adds value and stays hidden where it adds noise.
The Marketplace’s Two-Species Future
The shop marketplace’s future is two-species: humans browse and buy; agents browse, negotiate, and buy. The agent buyer needs the machine-native marketplace features this series has described — the structured listings, the machine-readable pricing, the automated escrow, the instant settlement — and the pool integration provides the settlement: the agent buyer’s credits, held in its pool balance, convert through the pool-to-credit layer and pay the storefront pool at checkout.
The two-species marketplace is not a replacement of the human one; it is an extension. The human customers keep the human checkout; the agent customers get the machine checkout; the storefront pools serve both — the same split formula distributes the human purchases and the agent purchases, and the ledger records both. The two-species marketplace is the shop’s growth story, and the pools are the rails that make it possible.
The Integration as the Commerce Layer
The pool-shop integration is the LucidHive stack’s commerce layer: the layer where the platform’s products meet the platform’s economics. The shop sells the products (the rent-to-own, the skill products, the studio services); the pools distribute the revenue (the creators, the agents, the infrastructure); the credits and conversions settle the value (the pool-to-credit layer, the marketplace’s currency). The commerce layer is what makes the stack a business, not a collection of features.
The integration also completes the product line’s loop: the pool products (the ledger, the split engine, the escrow) serve the shop’s vendors; the shop’s transactions generate the pool activity; the pool activity generates the product revenue. The loop is the product line’s flywheel — the more the shop sells, the more the pools move, the more the pool products earn, the more the shop’s vendors can sell. The flywheel is the commercial thesis of the entire share-pool series, made concrete in the shop.
The Storefront as the Pool’s Classroom
The shop integration is also the pool’s classroom: the easiest place for a new customer to learn the pool mechanics. The solo creator attaches a pool to their storefront, sees the split computation, watches the contributions log, and learns the ledger — before graduating to the escrow, the reputation system, and the agent marketplace. The storefront is the product line’s on-ramp, and the on-ramp design is the product’s adoption strategy.
Every pool in this series — the creator co-op, the retainer, the agent fleet, the agent marketplace — can start as a storefront pool on the shop, because the shop provides the revenue flow that every pool needs. The shop is not just the marketplace; it is the share-pool economy’s front door, and the pools are what happens inside.
Grounded in wiki concepts shop-lucidhive, share-pool, marketplace, checkout, commerce-layer, and the Sovereign-stack business series. Design notes on a running system.
