Outcome coverage
Requisition to receipt
The platform observes 29.4% of the 326 chain links in scope here, reconstructs 58.0%, and estimates that 41 happen where it cannot read them. This statement was produced by stage link provenance and carries a band of plus or minus 17%.
The method behind this statement
Stage link provenance · owned by Diego Fuentes · Service owner
Observed is the count of stage links joined on a shared key. Inferred is the count joined by rule or cohort. Unseen is the residual against the service’s declared instance count.
Observed is the count of stage links joined on a shared key. Inferred is joined by rule or by cohort. Unseen is the residual against the declared instance count.
Requisitions raised verbally to a buyer and entered later under the buyer’s own name.
Who has signed for it
Nobody. This figure rests on its method alone.
An attestation would not turn an estimate into a measurement. It would put a person behind the estimate, which is the difference between a number and a claim. This statement does not have one.
What this statement is, and what it is not
Coverage can only ever be estimated from the outside. Observed is a count the platform can produce from records it holds. Inferred is a count it reconstructs by rule or by cohort. Unseen is an estimate of work the platform knows exists and cannot read, and every statement carries the method that produced it and a stated uncertainty. Nothing here is rounded up.
A coverage statement is disputable by design. The way to disagree with one is to inspect the method and the basis for the unseen figure, both of which are on the statement, rather than to argue about the number.