Workflow acceptance and retesting
Compare observed results with agreed criteria and keep Ready, Failed and Unknown outcomes explicit.
Inputs and behavior
The Python 3.10+ local example compares supplied usage and billed-event CSV files and exports a report. Export success alone does not establish acceptance. It does not access customer systems or automatically correct live billing records.
Synthetic usage: event_id=u-001, quantity=1. Synthetic billed event: event_id=u-001, quantity=1. With a confirmed one-to-one event contract, matching rows can be Ready. Missing or mismatched rows can be Failed; unconfirmed scope remains Unknown.
Interpret the result
Acceptance depends on the agreed criteria, authorized evidence and a named reviewer. The local CSV example checks only supplied event rows under a caller-confirmed one-to-one event contract. It does not establish source completeness, accounting or tax correctness, current remote state, or business completion.
Unknown is unresolved evidence. Do not treat it as a pass or permission to take a side effect.
This website provides documentation. It exposes no execution endpoint, account, upload form or hosted API.