New task · Tidewater
Let customers pay by invoice at checkout
How it works
Write the task. It comes back as a plan.
Every task on the list gets a worker. Here is what happens between your words and the finished work, step by step.
01 · Write
Write it in plain words.
From the list, your phone, or the chat. A dropped link or a note becomes a task on its own. When a worker has a question, it arrives with a catch-up, so you never open a task cold.
- No form, no fields, no ticket template
- A link or a note is enough to start
- Questions come with the context already gathered
Plan · Tidewater · waiting on you
Customers can pay by invoice
- What changes
- An “Invoice” option at checkout. The order waits until the invoice is paid, then ships as usual.
- What it touches
- Checkout, the order record, and two billing e-mails. Nothing in payments.
- What could go wrong
- A wrong total on the invoice PDF. The check compares it to the order before it ships.
- How to undo
- One undo of the change. Orders already paid by invoice stay paid.
02 · Plan
The plan in four parts.
A Planner reads the task and writes what changes, what it touches, what could go wrong, and how to undo it. Nothing starts until you have read it. If the Planner could not tell, it says so instead of guessing.
- What changes, in one paragraph
- What it touches, named
- What could go wrong, and how the check catches it
- How to undo, before you say yes
03 · Approve
Say yes once.
One press. Your yes covers the pieces of the plan as long as each piece stays inside the lines the plan drew. “I could not tell” counts as outside. You can take a yes back at any time: unfinished pieces park, and the task says which ones had already gone.
- Four kinds of work always come back for their own yes
- Who may say yes is a setting per business
- Never a merge you cannot read
Always comes back to you
- Anything that cannot be undone
- A data migration, a deleted record, a message already sent. The plan may name it; the work waits for its own press.
- Anything touching security or another business
- Sign-in, keys, and the wall between one business and the next.
- Anything a reviewer flagged
- When the second company's model says hold, the task comes back with the reason in plain words.
- Anything that changes what you will be asked
- If a worker wants to change the questions themselves, you decide first.
Machine · idle9 queued · 3 building · 2 checking
Builder started “customers can pay by invoice” on its own branchBuilder · GPT · now
Verifier is checking the work · a different company's modelVerifier · Grok · 2 m
Second look passed · waiting for a clean walkReviewer · Claude · 14 m
Staging walked clean · live at 03:12Scouts · 1 h
BuildCheckSecond lookLive
04 · Do and check
Workers do it, and a second company checks it.
Planner, Builder, Verifier, Researcher, Librarian, Scouts, Guide and Log writer: digital workers named by what they do. Software work happens on its own branch. Nothing goes live until a worker from a different company than the one that did it has checked it.
- Three model families: Claude, GPT through Codex, and Grok
- The one that did the work never checks it alone
- A clean walk on staging before anything is live
05 · Done
Done, and written down.
Every finished task is one change and one undo. Everything the workers did is written on the task in plain words, and the record lives in your own GitHub account. Leave any day with all of it.
- One change, one undo
- The record is yours, in your account
- No hidden log, no vendor notebook
Tidewater · Task #118
Customers can pay by invoice
Asked: customers can pay by invoiceyou · Mon 08:12
Plan written in four partsPlanner · 08:20
You said yes. One press.you · 08:41
Built on its own branchBuilder · GPT · 09:30
Checked by a different company's modelVerifier · Grok · 09:52
Live. One change, one undo.Scouts · 11:40
06 · Comes back to you
Four kinds of work always come back for their own yes.
Everything else gets done inside the plan you approved. These four never ride a shared yes and never run on their own.
Always comes back to you
- Anything that cannot be undone
- A data migration, a deleted record, a message already sent. The plan may name it; the work waits for its own press.
- Anything touching security or another business
- Sign-in, keys, and the wall between one business and the next.
- Anything a reviewer flagged
- When the second company's model says hold, the task comes back with the reason in plain words.
- Anything that changes what you will be asked
- If a worker wants to change the questions themselves, you decide first.
Unfinished pieces park. Finished ones are named.
07 · At night
While you sleep, the list is tidied and written up.
Four workers run on their own, on a schedule, and leave what they did on the record.
Librarian
Tidies the list on two companies' models and shows you where they disagree instead of picking one.
Guide
Keeps a plain-words guide of your product true after every change, and files a task when what shipped and what was decided drift apart.
Log writer
Writes the Morning Log before you wake, in your time zone, and only on days something happened.
Scouts
Walk the live product after every change and every day, and file what breaks as tasks under their own names.
08 · Not only code
The same list takes other work.
Software is where the workers started. Research, writing, marketing, ops and support come back on the same list.
Research
“How do three competitors price seats?”
A Researcher reads, compares, and leaves a Doc on the task with what it found and where it found it.
Writing
“Draft the launch post and the release notes.”
A draft Post and a Doc on the task, in your voice, waiting for your read before anything is published.
Marketing, ops and support
“Turn last week's changes into the newsletter.” “Reconcile the invoices.” “Sort the inbox.”
They arrive the same way as everything else: a plan, one yes, the work on the record.