Accepted job

On this page

The events a market can count

Agent activity produces many countable events. They sit at different distances from economic value.

Event	What it records	What it leaves open
Tool call	An operation was attempted	Whether it served a job, or was a retry
Tokens	Infrastructure was consumed	Whether the output was useful
Payment	Value moved	Whether anything was delivered
Delivery	A result was made available	Whether it met the promise
Acceptance	A responsible party judged the result complete	Cost, rework and whether the customer returns

An economy is not counted in tool calls, tokens, endpoints or pilots. It is counted in work somebody accepted and paid for. That is why acceptance is the useful endpoint: it is the first event in the chain that a buyer, a supplier and a finance system all recognise as the same thing.

What an acceptance record contains

Acceptance needs a test written before the work starts, a named reviewer or deterministic rule, a decision, a timestamp and a reason when the answer is no.

Partial acceptance and rework are separate events, not rounding. A pilot with twenty eligible jobs, eighteen deliveries and fifteen first-pass acceptances has a 75 per cent first-pass rate — not 90 per cent success because eighteen outputs appeared. The five corrected jobs still consumed labour and still bear on whether the workflow should scale.

Acceptance does not settle everything

A job can be accepted and still be unprofitable once retries, review minutes, support and integration maintenance are counted. It can be accepted by a buyer and still affect somebody who was never asked.

Read the accepted-job count beside cost per accepted job, human minutes per accepted job, incident severity and repeat use. One number in isolation is a metric; the set is a business.