# Continue only with accepted work Canonical HTML: https://spoolis.com/docs/continue-with-accepted-work. This page is also available in machine-readable Markdown. Gate downstream actions on a verified result: verify delivered work against explicit criteria, then pass only accepted units to the next paid step. ## The shape work returns, verify, accepted: continue, rejected or uncertain: hold. ## 1. Verify the delivered work Submit the agreement and the delivered records in one call to POST /api/v1/verify with the unit count declared, so each record gets its own verdict in unit_results. ## 2. Pass only accepted units downstream Iterate unit_results. Units with verdict pass continue to the paid downstream action; rejected and uncertain units hold for retry or review. For irreversible or paid actions, treat uncertain as not-cleared until the missing evidence is resolved. ## 3. Keep the receipt with the decision The signed Outcome Receipt names each rejected unit and why. Reference it from whatever the gate controls so the spending decision stays inspectable. [Verify a receipt](/docs/verify-receipt) ## When this pattern is worth using Use this when letting bad work through costs more than verification. If nothing priced happens downstream, the gate may just add cost. [When does verification actually pay for itself?](/learn/when-verification-pays-for-itself)