# Spoolis learning center Canonical HTML: https://spoolis.com/learn. This page is also available in machine-readable Markdown. Ideas and practical guides for acceptance infrastructure, outcome-based software, and agent workflows. ## Start here Learn the acceptance model, the Spool (a versioned acceptance policy), Outcomes, and product fit. - [Introducing Spoolis](/learn/introducing-spoolis) - [What is a Spool?](/learn/what-is-a-spool) - [What is an Outcome Receipt?](/learn/what-is-an-outcome-receipt) - [When to use Spoolis](/learn/when-to-use-spoolis) ## Acceptance infrastructure Learn how work is judged against agreed conditions, including uncertainty, corrections, retries, and who chooses the judge. - [What is acceptance infrastructure?](/learn/what-is-acceptance-infrastructure) - [Why the first checker is easy](/learn/why-the-first-checker-is-easy) - [Every payment system needs someone to decide what counted](/learn/who-decides-what-counted) - [The fulfillment layer between authorization and settlement](/learn/the-fulfillment-layer-between-authorization-and-settlement) - [LLM as judge vs acceptance infrastructure](/learn/llm-as-judge-vs-verification) - [What happens when one AI agent has to judge another?](/learn/when-one-agent-judges-another) - [Routing disposition vs acceptance state](/learn/routing-disposition-vs-acceptance-state) - [Who grades the outcome?](/learn/who-grades-the-outcome) - [What vendors mean by an outcome](/learn/what-vendors-mean-by-an-outcome) - [How AI support vendors count a resolution](/learn/how-ai-support-vendors-count-a-resolution) - [Check your AI agent bill](/learn/check-your-ai-agent-bill) - [A person in the acceptance loop](/learn/a-person-in-the-acceptance-loop) - [What required evidence changes](/learn/what-required-evidence-changes) - [When Spoolis decides and when you decide](/learn/when-spoolis-decides-and-when-you-decide) - [Fulfillment verification for agentic commerce](/learn/fulfillment-verification-for-agentic-commerce) - [When does verification pay for itself?](/learn/when-verification-pays-for-itself) ## Outcome-based software Learn how software moves from selling usage to selling accepted work, with clear units, prices, and disputes. - [What comes after usage-based software?](/learn/what-comes-after-usage-based-software) - [Pay per verified unit](/learn/pay-per-verified-unit) - [Payments know when money moved. They don’t know whether it was earned.](/learn/payments-know-when-money-moved-not-whether-earned) - [Pay only what was earned](/learn/authorization-is-not-earned-value) - [My agent paid for work and got garbage back. Now what?](/learn/my-agent-paid-and-got-garbage) ## 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.](/learn/the-workflow-doesnt-continue) - [The agent said done. The next system still shouldn’t trust it yet.](/learn/the-agent-said-done) - [When one agent says “done” to another agent](/learn/when-one-agent-says-done-to-another-agent) - [How to stop an agent mistake before it becomes irreversible](/learn/gating-consequential-agent-actions) - [A verified outcome in the loop](/learn/a-verified-outcome-in-the-loop) - [Required Outcome checks in CI](/learn/required-outcome-checks-in-ci) - [What happens when an agent checks the work before spending more](/learn/checks-the-work-before-spending-more) - [Agentic commerce 101](/learn/agentic-commerce) - [The agent economy report](/learn/agent-economy-report) ## Billing, payment, and settlement These are downstream ways to consume an Outcome, not what Spoolis fundamentally is. - [Acceptance-gated settlement](/learn/verification-gated-settlement) - [Authorize the cap. Capture what was earned.](/learn/authorize-the-cap-capture-what-was-earned) - [How Spoolis routes a payment](/learn/how-spoolis-routes-a-payment) - [Understanding settlement paths: Stripe, Tempo, and external settlement](/learn/understanding-settlement-paths-stripe-tempo-and-external-settlement) - [Working with machine payment protocols: MPP and x402](/learn/working-with-machine-payment-protocols-mpp-and-x402) ## Developer guides Build with portable unit identity and the developer documentation. - [Unit identity that travels](/learn/unit-identity-that-travels) - [Developer docs](/docs) ## Essays and experiments Experiments and older payment-focused essays that test the acceptance thesis in the world. - [The payment was verifiable. The work wasn't.](/learn/the-payment-was-verifiable) - [A portable Outcome for an ERC-8183 job](/learn/a-portable-outcome-for-an-erc-8183-job) - [Anatomy of a verified transaction](/learn/anatomy-of-a-verified-transaction) - [Two services. No accounts. One signed Outcome.](/learn/two-services-no-accounts-one-signed-outcome) - [The settlement points at the proof](/learn/the-settlement-points-at-the-proof) - [The new payment rails weren't built for old commerce](/learn/agent-payments-arent-just-new-rails) - [When payments become final, what happens to buyer protection?](/learn/when-payments-become-final)