On 1 October 2026 our own engineering team routed six Outcomes jobs through the production Ormas gateway against our own private repository at the Standard service level. Five delivered and were merged. One was refused by the client's own test and cost the client nothing. The table records the quoted prices, not payments from external customers.
This is dogfood: the client and the provider operator are the same company, the jobs ran on the operator's tenant, and acceptance was performed by the operator-run checker. It shows the contract working end to end on real tickets. It does not yet show outside demand or independent acceptance. Customer billing on the operator tenant was $0; internal provider settlement is not external customer revenue.
The jobs#
| Ticket | Size | Quoted price | Result |
|---|---|---|---|
| Test import path moved to the public package | small | $0.2253 | delivered and merged |
| Streaming translator: match a new library signature | small | $0.2253 | delivered and merged |
| Test fixtures: add a missing payload field | small | $0.2253 | delivered and merged |
| Queued job status: explain why no provider has claimed | medium | $0.5471 | delivered and merged |
| Retire a default routing tier | medium | $0.5471 | delivered and merged |
| Replace import-time clocks in a test suite | large | $0.5471 | refused by the test; settled at $0; nothing merged |
These are historical quotes for this internal trial, not a current price list. A delivered branch and a provider settlement do not establish a customer charge or independent validator acceptance. The sixth job used the provider's full attempt and the candidate failed the frozen test (8 of 217 tests red), so the receipt settled as no-delivery at $0 and the ticket stayed open with a precise diagnosis of what the next task must say.
What the client did for each job#
- Wrote the acceptance test and confirmed it fails on the base commit at a plain
assert. - Asked the coding agent to prepare the task with the test, the editable and immutable paths, and the pushed base commit. No model was named; the provider decides how to do the work.
- Submitted the prepared task with a price ceiling. The provider's firm quote came in far under the ceiling every time; the ceiling is never the price.
- Watched job status until it was terminal. The accepted quote is visible on the job as soon as a provider is bound, before any result exists.
- Fetched the result branch into a clean checkout, re-ran the acceptance tests, and merged.
Work runs asynchronously, so the client's engineer can do other work in between. Delivery times vary; there is no deadline guarantee or measured speed advantage over using an agent inline.
Current offers can be firm or limit: a firm price on verified delivery, or an estimate with a hard limit and a charge at the miner’s settled price, never above that limit. The firm quotes above describe the October 1 trial.
What the receipts guarantee#
Each receipt records the job, the accepted quote, the amount billed, the SHA-256 of the delivered diff and the settlement state. Acceptance means the frozen test passed in a separate environment that the candidate could not edit. Coverage, unintended behaviour and integration remain the client's review; the merge decision stays with the client.
These October 1 deliveries were verified by the client's own tests in an operator-run checker. Production validation remains Ormas-operated. See Standard and Protected for the current service status.