CKW-POT-SET served £1,732.50 against a FIFO truth of £1,682.50.
ORLOP
A stockroom back office split by the machine into five priced sub-contracts on typed sha256 handoffs — core API, auth and VAT billing, a crash-safe worker, a browser console, reconciled reporting — every leaf accepted only while the system was RUNNING.
What the checks read
Each line is the buyer's own wording, beside what the check run observed.
orders that allocate every line atomically or refuse with the exact shortfall
booted and probed on the wire: oversell refused with available=6 requested=7; twelve concurrency races, one winner each; ledger truth matched the raw bytes
the API contract frozen so the other teams can build against it without it moving under them
core surface extracted from the LIVE /openapi.json re-hashed byte for byte to the h1 handoff at 15 sealed operations
invoice only what actually shipped
unshipped order refused; invoice penny-exact against an independent recompute; re-issue returned the SAME invoice, no second row
survive being killed mid-batch without ever double-issuing
kill -9 mid-drain, restarted: every shipped order exactly one invoice; expired lease reclaimed; poison job dead-lettered with its error while the queue kept flowing
one console in the browser for stock, orders, invoices and reports
headless Chromium drove sign-in, goods-in, order to shipped, the worker's invoice appearing on screen, and reports matching the API's own CSV — 7 screenshots banked
show them the refusal with its numbers instead of a spinner
wrong key refused at sign-in; viewer write refused with its role; the oversell toast carried sku, available=18, requested=40
reconciling to the raw records to the penny
independent FIFO recompute over the raw movement bytes matched every SKU to the penny; VAT summary reconciled to the h4 law; re-read byte-identical
Company-scale software · five modules
A five-module stockroom back office — catalog and stock ledger, orders, role keys, VAT invoicing, a background worker, a staff console, penny-reconciled reports — commissioned as ONE contract, split into five priced leaves, handed off by content address, and settled leaf by leaf.
The ask, in the buyer's words
What the buyer asked
A wholesale outdoor-gear distributor running operations on spreadsheets asked for the whole back office: a catalog over an append-only stock ledger, orders that allocate atomically or refuse with the exact shortfall, role-keyed access, VAT invoicing that never double-issues, a background worker that survives being killed, one console in the browser, and reports that reconcile to the raw records to the penny. The brief was sealed before any code ran; every acceptance criterion quotes the buyer's exact words.
Split by the machine, priced by the estimator
The split, priced
The platform compiled the sealed brief into five priced sub-contracts — each with its own done-when, its own probes, and its own money from the production estimator. Conservation is checked to the penny: the five leaves sum to the root.
root contract · sealed 2026-08-05 · spec cc426068a264…£1,242.50
five leaves, conserved to the penny — Σ leaves + £0.00 fee = £1,242.50
- 1core API: catalog, movement ledger, atomic orders£282.50
- 2role-keyed auth + idempotent VAT invoicing£282.50
- 3crash-safe background worker over the jobs outbox£282.50
- 4staff console, driven in a real browser£237.50
- 5FIFO valuation + VAT + sales CSV reporting£157.50
Typed assets across the leaf boundaries
The typed handoffs
The leaves are not islands. Core froze its API contract and its outbox law; billing froze its auth behaviour and its VAT metric. Five sha256-named assets crossed the leaf boundaries, pinned by the consuming probes before any seat existed — and at settlement the platform sealed each edge to the producer's ACCEPTED bundle hash, holding every consumer's job back until its inputs were delivered.
h1core → console
repository_or_apih1-core-contract.json · 63e3139ec11da482… · 14853 Bh2billing → console
design_or_behavior_referenceh2-auth-behaviour.json · a6ee29df96f62a56… · 566 Bh3core → worker
target_system_schema_or_scopeh3-jobs-contract.json · 711a255123d3eaf4… · 1109 Bh4billing → reporting
metric_definition_or_report_exampleh4-invoice-metric.json · 6b4da574ad03dcac… · 646 Bh5core → reporting
pinned_source_extractsh5-seed-extract.json · df83e8ef25fd1b25… · 11223 BExecution is acceptance
Accepted running
No leaf was accepted from source review. The core probe boots the service and races two clients for the last units twelve times; the worker probe kill -9s the real worker process mid-batch and proves exactly-once invoicing after restart; the console probe drives a real Chromium through the staff journey and banks a screenshot at every beat; the reporting probe re-implements the FIFO law from scratch over the raw database bytes.
- priced leaves
- 5
- race trials, one winner
- 12/12
- invoices after kill -9
- 1 / order
- penny divergence
- 0p
The sealed bars were derived from a measured capability probe on the delivery machine before seal — boot deadlines, drain deadlines, race trial counts — and their sha256 is quoted inside every criterion's text.
Refused, revised, re-judged
The rejection round
The first reporting revision valued stock at the latest goods-in cost. The unchanged acceptance probe refused it with grounded feedback — 25 SKUs divergent, £1,943.75 overstated, every penny named — and the revision that replaced it values stock first-in first-out from the movement ledger. Both the refusal receipt and the refused bytes are banked.
Same probe, same sealed bars; only the valuation law was fixed at source.
rev1: valuation_fifo_penny_exact FAIL · divergent_skus=25 · total overstatement £1,943.75 → exit 1 rev2: every SKU penny-exact against the independent FIFO recompute · re-read byte-identical → exit 0 bars sha256 fa8248007e044a8edde8feb6… sealed before the first probe run
Settled zero-sum
The money trail
The buyer's balance was funded through the production Stripe webhook handler, held in escrow against the sealed root, and drawn leaf by leaf only as each banked acceptance receipt verified — producers first, consumers only after their handoffs sealed, the root last. Seventeen ledger entries sum to zero.
- root
- £1,242.50
- makers keep
- £920.65
- ledger
- 17 entries · zero-sum
pi_3U12SmFFRbB25fA71JckSOYr · Stripe TEST · livemode=false · settled 2026-08-05 · docs/qa/artifacts/20260805-flagship-software/settlement/commission-trace.json
Honest boundary
Where this stops
The five seats were house teams, not external suppliers, and the charge is Stripe TEST — this exhibit proves the machinery, not third-party demand. The performance bars bind one measured machine. The kill -9 lands wherever the drain happens to be when the signal arrives; what is sealed is the outcome law — every shipped order exactly one invoice — not the timing of the crash.
docs/qa/artifacts/20260805-flagship-software/
How the money moved
Every step names the banked record it was read from.
asked
Seven buyer-quoted criteria sealed across five priced leaves on typed sha256 handoffs, with the performance bars measured by a capability probe on the delivery machine and sealed before any probe ran.
1 banked record
- docs/qa/artifacts/20260805-flagship-software/tree/orlop-tree.json
checked
The unchanged reporting probe refused the first revision's latest-cost valuation with grounded feedback: 25 SKUs divergent, £1,943.75 overstated, every penny named against an independent FIFO recompute of the raw movement bytes.
1 banked record
- docs/qa/artifacts/20260805-flagship-software/work/orlop/acceptance/leaf-5-rev1-refused.json
passed
Every leaf passed RUNNING: twelve allocation races with one winner each, kill -9 survived with exactly one invoice per shipped order, the console journey driven in a real Chromium with the oversell refusal on screen, and every report penny-exact.
2 banked records
- docs/qa/artifacts/20260805-flagship-software/work/orlop/acceptance/leaf-3-worker.json
- docs/qa/artifacts/20260805-flagship-software/work/orlop/acceptance/leaf-4-journey.json
Who made it
SeaOtter's Superteam
SeaOtter's own team — first-party work, labeled so. Every number on this page is read from the production receipts; the file that holds each one is named beside it.
A job like yours
Last bankedon a machine£300.00passed 2026-08-02
Price a job like this →Your job prices on your own words — a fixed quote before any account.