HARBOURMASTER — the route proven at the destination
The route, proven at the destination
A two-step route written in the live store, then re-read from fresh Shopify bytes with a separate key — the claim and the destination, side by side.
“A green success indicator is not evidence.”
automation-build advisory £130–2,605 (thin, n=3) · £75 floor cleared
The build — two writes, two live receipts
- 1Tag the review draft, persist the route code
- 2Tag the linked customer
the two live store receipts
The machine's own identifiers, kept so anyone can re-check this page against the recorded run. Nothing above is missing from here.
seaotter-route:fulfilment-ready · priority-fulfilment-v1
HTTP 200 · draft_orders/1035298504888.json · req 732e03cd
seaotter-route:priority-followup
HTTP 200 · customers/10524287402168.json · req 3faa17b1
The agent's word
claimed: success
“The two-step review draft routing workflow is defined.”
destination read-back: no
The exact record
The machine's own identifiers, kept so anyone can re-check this page against the recorded run. Nothing above is missing from here.
gpt-5.6-terra · 262 tokens · $0.001224 · 1376 ms
evidence basis: two Shopify action responses returned 2xx
The destination's word
fresh Shopify bytes, read with the separate standing key
- drafts carrying the event1
- draft route tag1
- customer route tag1
- draft-to-customer link1
- the agreed route code0
refused — the destination's own numbers did not match the claim
£0.00 for that period — a refused claim costs nothing
The exact record
The machine's own identifiers, kept so anyone can re-check this page against the recorded run. Nothing above is missing from here.
destination_field_drift · fresh-read pin 1361e237
Three more breaks, planted in the live store
- both route tags silently absentrefused£0.00
- draft tagged · customer notrefused£0.00
- a second draft for the same eventrefused£0.00
each refused by name, a named exception filed · £0.00 for every failed period
The exact record
The machine's own identifiers, kept so anyone can re-check this page against the recorded run. Nothing above is missing from here.
both route tags silently absent: silent_import_fail · event hm-20260807t210324z produced no readable two-step destination write · fresh-read pin 1d80e22f
draft tagged · customer not: partial_write · event hm-20260807t210324z has order_write=1, customer_write=0 · fresh-read pin fbc1b060
a second draft for the same event: duplicate_destination · event hm-20260807t210324z resolved to 2 drafts · fresh-read pin 64204938
Verified delivery — the destination re-read
the route restored; a new fresh read earned the verdict
- drafts carrying the event1
- draft route tag1
- customer route tag1
- draft-to-customer link1
- the agreed route code1
all five facts at 1
3 passing periods released at £99.00 · a failed period bills £0.00
the fresh reads, receipt by receipt
The machine's own identifiers, kept so anyone can re-check this page against the recorded run. Nothing above is missing from here.
fresh-read pin 175053ae
HTTP 200 · draft_orders.json · req a5ce63dc
HTTP 200 · customers/10524287402168.json · req c4d841fc
The key, on the record
two keys — the worker's for the writes, a separate standing key for every read · both revoked · 35 receipts
grantedrevokedthe next use refusedafter revocation the next check stopped before Shopify was read — runs 7 → 7
4 disposable objects deleted · 3 independent absence reads · 14 evidence files swept clean
SeaOtter's own development store — the fixture stayed a draft; no checkout, no invoice, no money attempted.
The exact record
The machine's own identifiers, kept so anyone can re-check this page against the recorded run. Nothing above is missing from here.
access_grant_revoked
The receipt
£149.00 setup + £99.00 a passing month · the in-store run is banked
A job like yours
Your job prices on your own words — a fixed quote before any account, money held until the checks pass.
Price a job like this