It works a shift every night, around the clock
It reads where the company stands, decides what would move it furthest tonight, and finishes that one thing.
It writes you one page in the morning
What shipped, what it learned, and the single question whose answer changes what happens tonight.
What the report looks like
Your company is live at https://cadence-clinic.firstemployee.app
SHIPPED
/guides/reducing-no-shows/ live
positioning-notes.md draft
reply to a clinic enquiry held
LEARNED
/faq/ failed my own checks twice — queued as tonight's first task.
ONE QUESTION
Tonight I start with: fix and publish /faq/ — right priority?
[ Yes, go ] [ I will leave a different instruction ]
Every line above is one the employee actually prints. The company in it is an illustration so the log reads as a whole; it is not a customer.
Ing cetha
| Wektu laku | Written at the end of every shift |
|---|---|
| Frekuensi | One per shift — by email and on the web |
| Output | A one-page report, one question, a full ledger under it |
| Kabeh | Thirty seconds. One tap if you want to answer. |
Kanggo sapa: A founder who does not want a dashboard — who wants to read one screen on a phone and make one decision.
Carané kerjané
- The log is written first. Every action during the shift writes a row as it happens: the tool, what came back, the model, the tokens, the duration and a link to whatever it produced. The report is written from that, not from memory.
- The report may only claim what the log shows. Anything held for approval is reported as held, not as sent. A night that shipped nothing says so in the headline rather than dressing activity up as progress.
- It ends in one question, not three. The single decision whose answer most changes tomorrow. Answer it in a tap and tonight's shift starts from your answer — the next brief quotes it back.
- The ledger sits underneath it. Same page, one scroll down: every row in order, filterable by tool and by what is waiting on you, exportable as CSV or JSON with no support ticket.
- Nothing in it can be edited later. The ledger is append-only and the database enforces it — an attempt to rewrite a row is rejected by the database itself, not by a promise in our code. A record that can be edited afterwards is a log, and a log is not evidence.
Apa sing sampeyan lakoni
- A headline saying what actually happened, in one sentence.
- A shipped list where every item is marked live, held or draft, with a link where there is one.
- What it learned, and what it plans to do next.
- Exactly one question, with two to four tappable answers.
- The full receipt ledger underneath, filterable and exportable.
pitakonan bab iki
Why only one question?
Because a list of five decisions gets none of them made. The employee is instructed to pick the single question whose answer most changes what it does next and leave the rest to its own judgement.
How do I know the report is true?
Every claim in it comes from a row you can open. If the report says a page shipped, there is a receipt showing the publish, the status the site returned, and a link to the page itself.
Can the ledger be edited after the fact?
No. The database rejects any attempt to rewrite a receipt row — it is enforced by a rule inside the database rather than by our application code choosing to behave.
Can I export it?
Any range, as CSV or JSON, at any time, with no ticket and no waiting period. The same rows are available over the API. If you leave, the ledger leaves with you.
Tugas sing gegayutan
It drafts what needs your yes
Anything irreversible stops and waits. It costs nothing to ask, which is the whole argument for asking often.
It checks the site before it ships
Twelve rules that block a publish rather than warn about it, then a check that the live URL really answers.
← It works a shift every night, around the clock · Sembarang tugas · It writes your founding documents →
Build iku gratis. Kerjane saben wengi wiwit karo rencana.