Glossary

Each term is defined once here and used the same way across the docs, the API, and the receipt schema. Where a term names a field, the linked page shows the field.

Spool

A versioned acceptance policy governing a piece of work: what counts, what evidence matters, and who has authority to judge. It is frozen behind an agreement hash before the work starts. Spool is what will count; Outcome is what did count. Read more.

Outcome

What actually counted against a Spool: which units were accepted, rejected, or uncertain, and what was earned. An Outcome is a fact about the work, not a decision about what to do next. Read more.

Outcome Receipt

The signed, portable record of an Outcome. It carries the agreement hash, the verification run, per-condition and per-unit results, amounts, actors, and an Ed25519 signature that any system can verify offline. Read more.

Acceptance criteria

The conditions in a Spool, each mandatory or optional, each with a named verifier. Together with the aggregation policy they decide the result. Read more.

Bring your own judge

The agreement names who decides each condition: a deterministic checker, an AI-assisted check, a human confirmation, or an external evaluator whose verdict is signed or referenced. Spoolis records the verdict and its provenance. It does not need to be the judge. Read more.

Committed amount

The maximum the agreement allows to be earned. The receipt records both committed and earned, so a consumer can see the difference. Read more.

Earned amount

What the accepted work is worth under the earning rule, never more than the committed amount. Code computes it from unit verdicts. Nobody asserts it. Read more.

Unitized work

Work delivered as countable units (records, tickets, tasks) where each unit gets its own verdict and the earning rule is per unit. Partial results are normal, not an error. Read more.

Uncertain

A verdict that says the question could not be resolved under the declared agreement. It is preserved as is, never rounded to pass or fail. What to do about it is the consumer's routing decision. Read more.

Acceptance state

Where a receipt sits in its lifecycle from a consumer's point of view: provisional (inside the review window), final (window elapsed, still current), corrected, revoked, or no review window. Read more.

Review window

The period after issuance during which a party named in the dispute policy can dispute the receipt. Published on the receipt as the review block. In finance terms, a holdback. Read more.

Supersession

Correction without rewriting history. A new receipt supersedes the original with a reason: verification defect, appeal reversal, or dispute resolution. The original stays a valid record; the status endpoint reports it as corrected or revoked. Read more.

Reconciliation statement

A consumer-side view of one receipt: claimed, accepted, rejected, and needs-review units, claimed and accepted amounts, the difference, and the reasons. Derived from the signed record, never a separate claim. Read more.

Booking record

One flat row per receipt for accounts payable, an ERP, or a spreadsheet. The document the next system can book. Read more.

Evidence provenance

For each evidence reference: where it came from, how it was captured, and when. Provenance says what kind of claim the evidence supports, not how true it is. Read more.

Acceptance authority

Who authored the policy, whether it was mutually agreed, and who accepted or acknowledged it. Spoolis preserves the agreement. It never manufactures one. Read more.

Acceptance infrastructure

The category: the machinery around a verdict (agreement, evidence, verdict states, corrections, earned value, a portable record) offered as shared infrastructure rather than rebuilt inside every product. Read more.