A weekly ship-log automation, still being checked. Every week it runs, the same sealed programs read the bytes it just wrote — and the week only bills if they pass.
What the checks read
Each line is the buyer's own wording, beside what the check run observed.
Done when: every item the report lists really landed inside the week the report says it covers.
ran to completion with exit code 0 in 0.054s
Done when: the count the report states matches the rows it shows and the notice it sends.
ran to completion with exit code 0 in 0.054s
Done when: the report keeps its agreed sections — Window, Landed, Notified — in that order, none of them empty.
ran to completion with exit code 0 in 0.053s
Done when: the notice actually goes out for that same week, naming the channel it went to.
ran to completion with exit code 0 in 0.053s
Done when: the week comes back as files I can keep — the page, the table behind it, and the notice.
the delivered bundle matches the agreed format (file)
Done when: every item the report lists really landed inside the week the report says it covers.
ran to completion with exit code 0 in 0.053s
Done when: the count the report states matches the rows it shows and the notice it sends.
ran to completion with exit code 0 in 0.058s
Done when: the report keeps its agreed sections — Window, Landed, Notified — in that order, none of them empty.
ran to completion with exit code 0 in 0.054s
6 more checks ran on this piece.
Standing automation
A weekly digest that gets checked every week — over the bytes it just wrote, by programs sealed before it ever ran.
What this is a copy of
The most-deployed automation shape there is, copied deliberately and by name: a clock fires, something reads a moving source over one closed window, writes a dated report, and sends a notice.
clock trigger -> read a moving source over a window -> durable write -> notify
logwatch / cron + mail (Unix)
Zapier: Schedule by Zapier -> Digest by Zapier -> Send
IFTTT daily-digest recipe
The failure it is famous for: it stops, or it starts lying, and the artifact it leaves behind looks the same either way.
The two weeks it ran
Two real elapsed weeks of this estate's own history, read over exact closed windows. A quiet week is a true report of a quiet week — the three files it writes are the whole of what gets judged.
Nine checks each time: the five the contract published, plus four sealed instances of them the delivering team never saw. The two rounds differ in the only way that matters — each one read a different week's bytes.
Round 1
9/9accepted
over 2026-07-20..2026-07-27 5977e85add921d90ef08d177f893f49bc5d8bd5a3f0ebe688dc350e605742664
replayed at 2026-08-03T21:48:07.538893+00:00
Round 2
9/9accepted
over 2026-07-27..2026-08-03 101974b7ce5b8f2b1f50e680f78975d443243f59d89dc4186b4893e481f576b3
replayed at 2026-08-03T21:48:07.938220+00:00
One pass is a delivery. Two passes, over two different runs, quoting two different addresses, is a machine still doing its job.
Both windows are real elapsed past weeks. Both runs and both rounds happened on 3 August 2026, seconds apart — nothing here claims a week of clock time passed between them. The claim is re-verified, twice, over two different runs.
What each week is judged against
Five done-whens, each quoting a sentence the buyer actually wrote. Four of them are about the report the automation writes, not about the program that writes it — that is what makes a second verdict possible at all.
“Done when: every item the report lists really landed inside the week the report says it covers.”
re-reads every row of the week's table against the window the page claims, and refuses a single item from outside it
dm-c1
“Done when: the count the report states matches the rows it shows and the notice it sends.”
holds the number written in the prose against the rows underneath it and against the notice that went out
dm-c2
“Done when: the report keeps its agreed sections — Window, Landed, Notified — in that order, none of them empty.”
requires the three agreed headings, in the agreed order, none of them empty
dm-c3
“Done when: the notice actually goes out for that same week, naming the channel it went to.”
requires the notice to name the same week as the page, and to name the channel it was delivered to
dm-c4
“Done when: the week comes back as files I can keep — the page, the table behind it, and the notice.”
requires the week to come back as the three keepable files, in the shape the contract declared
dm-c5
Every week runs nine: these five, plus four sealed instances the team delivering the work never saw.
The instrument can refuse
Two acceptances prove the weeks, not the programs — a program that always passes comes back exactly the same way. So a real week was broken in the four ways this shape lies in the wild, and each break had to be caught by the one check that owns it.
a row from outside the window the digest claimsdm-c1 fail
the prose states one more item than the table holdsdm-c2 fail
the agreed Notified section is gonedm-c3 fail
the notice covers a different week than the digestdm-c4 fail
Four breaks, four catches, and in every case no other check changed its verdict. A check that fails everything is as useless as one that passes everything.
The money
The whole calendar was held once, at the sealing. One week has settled so far — drawn against the run that proved it, at the instant it proved it.
Held at the sealing£360.00Drawn for the settled week£90.00The team keeps£67.50The platform keeps£22.50
Checking happens per run; billing happens per week. That split is the product: a buyer hears their automation broke the day it breaks, not the day they are invoiced. The rest of the calendar stays held until each of its own weeks proves itself, and a week that fails is free.
Funded with a test-mode card payment, and the receipt says so: pi_3U0TeoFFRbB25fA70WpGfQG7
TIDEMARK answered “did you build it”. This is the question that arrives the following Monday and never stops arriving: “is it still working”. It needs a different instrument, because re-reading a delivered file gives the same answer forever. These programs read a moving target — what the automation persisted this week — so the verdict is earned again every week, and the week only bills when it is.
The bytes each week left behind
The three files each run persisted, hashed the instant they were written. These are what the sealed programs were pointed at — not a delivered bundle, and not a screenshot of one.
2026-07-20..2026-07-27 · digest.md813bad9a98cc…
2026-07-20..2026-07-27 · rows.csv5f5afa31fd23…
2026-07-20..2026-07-27 · notify.jsonc245a559b613…
2026-07-27..2026-08-03 · digest.md5ef6cdfb9443…
2026-07-27..2026-08-03 · rows.csv4d597a7ffe49…
2026-07-27..2026-08-03 · notify.jsonf974b900a764…
WHAT HAPPENED
DAYMARK
A weekly ship-log automation, re-checked over the bytes it writes each week — twice, over two different runs, by programs the contract published before it ever ran.
paidOne week's price is drawn against the run that proved it.
Brief sealeddone£360.00
“Done when: the count the report states matches the rows it shows and the notice it sends.”
“Done when: the week comes back as files I can keep — the page, the table behind it, and the notice.”
Calendar sealeddone
“Done when: the report keeps its agreed sections — Window, Landed, Notified — in that order, none of them empty.”
“Done when: the notice actually goes out for that same week, naming the channel it went to.”
Helddone£360.00
Week one writtendone
Week two writtendone
Checked: week onedone
Re-verifieddone
nine of nine week one
Checked: week twodone
Re-verified, againdone
nine of nine, again week two
Refused: four of fourdone
Drawndone£90.00
Checked against what you asked for.
met“Done when: every item the report lists really landed inside the week the report says it covers.”ran to completion with exit code 0 in 0.054s
met“Done when: the count the report states matches the rows it shows and the notice it sends.”ran to completion with exit code 0 in 0.054s
met“Done when: the report keeps its agreed sections — Window, Landed, Notified — in that order, none of them empty.”ran to completion with exit code 0 in 0.053s
met“Done when: the notice actually goes out for that same week, naming the channel it went to.”ran to completion with exit code 0 in 0.053s
met“Done when: the week comes back as files I can keep — the page, the table behind it, and the notice.”the delivered bundle matches the agreed format (file)
met“Done when: every item the report lists really landed inside the week the report says it covers.”ran to completion with exit code 0 in 0.053s
met“Done when: the count the report states matches the rows it shows and the notice it sends.”ran to completion with exit code 0 in 0.058s
met“Done when: the report keeps its agreed sections — Window, Landed, Notified — in that order, none of them empty.”ran to completion with exit code 0 in 0.054s
met“Done when: the notice actually goes out for that same week, naming the channel it went to.”ran to completion with exit code 0 in 0.054s
met“Done when: the week comes back as files I can keep — the page, the table behind it, and the notice.”the delivered bundle matches the agreed format (file)
met“A week whose page lists a day from outside the week it claims is refused”dm-c1 came back fail; the other three did not change
met“A week whose written count disagrees with its own table is refused”dm-c2 came back fail; the other three did not change
met“A week that quietly drops an agreed section is refused”dm-c3 came back fail; the other three did not change
met“A week whose notice covers a different week than the page is refused”dm-c4 came back fail; the other three did not change
The moneyhelddrawn
£360.00held3 Aug 2026
£90.00drawn3 Aug 2026
How the money moved
Every step names the banked record it was read from.
asked · 4 steps
It runs again over the week after.
4 banked records
docs/qa/artifacts/20260803-daymark-standing-automation/commission-trace.json — the sealed brief
docs/qa/artifacts/20260803-daymark-standing-automation/commission-trace.json — the sealed calendar
docs/qa/artifacts/20260803-daymark-standing-automation/runs.json — the first run
docs/qa/artifacts/20260803-daymark-standing-automation/runs.json — the second run
checked · 3 steps
The same programs are then handed four broken weeks.
3 banked records
docs/qa/artifacts/20260803-daymark-standing-automation/replay-receipts.json — the first round
docs/qa/artifacts/20260803-daymark-standing-automation/replay-receipts.json — the second round
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.
When it refuses
Four deliberate breaks were fed to the same four checks. Each was caught by the one check that owns it, and no other check moved.