Interactive product example
Inspect the work.
Follow the evidence.
Choose an invoice or catalog task and move through its contract, checks, authorized action, and sample receipt. This demo uses sample data and runs entirely in your browser.
Inside an outcome
Follow the work.
Inspect the proof.
Follow each step from the task contract to the outcome receipt.
Define the finish line
A task with a promise.
Take one supplier invoice and create a draft AP bill. The contract specifies the inputs, required checks, and exact permitted action before work begins.
Creating the draft is the outcome. Posting a bill or making a payment is outside this contract.
- Input
- One invoice document
- Context
- Supplier, purchase order, receipts
- Output
- A draft AP bill in ERP.AI
- Completion
- Checks pass + write confirmed
- Routing
- Within configured cost and data limits
What if a check cannot pass?
The workflow should stop before the write. A missing receipt, ambiguous supplier, or unsupported value is a reason to ask for evidence, not to invent a result.
Read the run lifecycle →What if the write times out?
The external effect can be uncertain even when verification passed. Reconcile by operation identity before attempting the same business write again.
Explore the ambiguous-write problem →