OUTCOME MODEL · NO THROUGHPUT DENOMINATOR
Acceptance: A Heartbeat Is Not a Verified Result
A long-scroll visual companion to the article. It summarizes the article evidence boundary and method; it does not extend the underlying result.
At a glance
Evidence in scope
- Track failures and retries
- Keep callback receipt separate
- Count unique accepted results only
Evidence boundary: No production acceptance ledger provides an accepted-jobs-per-hour rate for this workflow.
How to use the diagram
Define acceptance first, persist the artifact reference, record verifier state, and reconcile callback submission/receipt separately.
What this visual explains: A run becomes accepted work only after its artifact passes a declared verifier; delivery/acknowledgement is another distinct state.
What it does not establish
No throughput, detector accuracy, or callback delivery rate is claimed.