Spoolis learning center
Ideas and practical guides for acceptance infrastructure, outcome-based software, and agent workflows.
New to Spoolis? Start with Introducing Spoolis. Building with it? Go to Developer guides. Thinking about the market? Start with Outcome-based software.
Start here
The acceptance model, the Spool (a versioned acceptance policy), Outcomes, and product fit.
Introducing SpoolisWhat is a Spool?What is an Outcome Receipt?When to use SpoolisAcceptance infrastructure
How work is judged against agreed conditions, including uncertainty, corrections, retries, and who chooses the judge.
Every payment system needs someone to decide what countedWhat is acceptance infrastructure?Why the first checker is easyWhat one agent built in three weeksThe fulfillment layer between authorization and settlementLLM as judge vs acceptance infrastructureWhat happens when one AI agent has to judge another?Routing disposition vs acceptance state: two questions hiding inside "what was the outcome?"Who grades the outcome? Six ways to decide what counted, and where acceptance infrastructure fitsWhat vendors mean by an outcome: eleven published definitions, side by sideHow AI support vendors count a resolutionCheck your AI agent bill against your own ticketsA person in the acceptance loop: how reviews and disputes workWhat required evidence changesWhen Spoolis decides and when you decideFulfillment verification for agentic commerceWhen does verification pay for itself?Outcome-based software
How software moves from selling usage to selling accepted work, with clear units, prices, and disputes.
What comes after usage-based software?Pay per verified unitPayments know when money moved. They don’t know whether it was earned.Pay only what was earnedMy agent paid for work and got garbage back. Now what?Agents and workflows
Returned work becomes a judgment, then an Outcome, then an input to the next action.
The agent said “done.” The system disagreed.The agent said done. The next system still shouldn’t trust it yet.When one agent says "done" to another agentHow to stop an agent mistake before it becomes irreversibleA verified outcome in the loopRequired Outcome checks in CIWhat happens when an agent checks the work before spending moreAgentic commerce 101The agent economy reportBilling, payment, and settlement
Ways downstream systems can consume an Outcome for billing, payment, and settlement.
Acceptance-gated settlementAuthorize the cap. Capture what was earned.How Spoolis routes a paymentUnderstanding settlement paths: Stripe, Tempo, and external settlementWorking with machine payment protocols: MPP and x402Developer guides
Build with the sandbox, API, MCP, CI gates, portable units, and independent receipt verification.
Unit identity that travelsEssays and experiments
Experiments and older payment-focused essays that test the acceptance thesis in the world.
The payment was verifiable. The work wasn't.A portable Outcome for an ERC-8183 jobAnatomy of a verified transactionTwo services. No accounts. One signed Outcome.The settlement points at the proofThe new payment rails weren't built for old commerceWhen payments become final, what happens to buyer protection?