Walk the morning
The brief, the queue, one reply approved with a pretend passkey, the kill switch, and the record it all leaves behind. Each stop ticks when it has happened.
One morning in Company OS: a safety report handled in about a second, fourteen replies sent by a rule you signed, one question waiting for you. Walk it the way the founder does — the brief, the queue, one approval, the kill switch, and the record behind it all.
The brief, the queue, one reply approved with a pretend passkey, the kill switch, and the record it all leaves behind. Each stop ticks when it has happened.
Overnight is already handled. One product question is waiting, its draft from your approved answer — see it, then approve it with the pretend passkey.
What the morning below is held to — every figure measured on simulators, with a fake model provider.
See the benchmarksShown honestly. The shop, its customers and every message in this sample are made up. The numbers — 287 milliseconds, about a second, 14 of 14 — are the project's own benchmark results, and the misses are counted on the project page.
Company OS rebuilds the brief from its own records every morning — nothing generates it, so nothing can dream it. It was ready at 07:26: eight sections, the same brief it would rebuild anywhere, because it is rebuilt from the record rather than remembered.
The brief is a projection over the records: rebuilt, never generated. Read it top to bottom — these eight sections are the whole morning.
It is ready at 07:26 and it reads the same at 09:00, because it derives from the record, not from whatever a model might say twice.
Section 3 is the only section that ends with a decision. The queue shows what was done overnight — and the one thing that needs you.
Everything that happened overnight lands in one queue, safety first. The first card is already handled, the last was sent by a rule you signed — read what was done, then take the one decision that is yours.
“I came out in a rash after the second day of the magnesium.”
Handled at 02:14, while you slept. Nothing about it waited for a model — no model is anywhere in the safety path.
“How many do I take a day?”
“Take one capsule a day with food, as it says on the label.”
A second agent, on a different provider, read the draft. It cannot edit the text — it can only say no. It didn’t.
This is the one decision the morning needs. The draft below is built only from your approved answer and it passed both checks. The passkey signs the exact letters on the screen — change one of them and the approval no longer counts. It is not a warning label; here it works. Try it.
The customer asked: “How many do I take a day?”
The second model sits on a different provider and can only reject — it read the draft and stayed silent.
The approval no longer counts. The passkey signs exactly what is on the screen. This text no longer matches your approved answer — to make it approve-able again.
Your pretend passkey. In the real system this is a hardware key on your desk. Here it is a button — press it to sign the exact text above.
Approved at 07:33:12 — bound to this exact text, letter for letter. What you see is what will be sent.
Now try the promise: change one word in the draft above and watch this approval stop counting.
The project page promises: “change one letter and the approval no longer counts.” The approval is bound to the exact text on the screen when you sign — not to your intentions, not to the draft’s id.
That is why the text box above is editable in this sample: so you can break the binding on purpose and feel it refuse.
One approval down. Next, the morning’s brake: a switch that stops every send — and the one lane it never stops.
The kill switch is the founder’s brake: pull it and every send stops within a second — the benchmark’s slowest stop is 287 milliseconds against a 10-second bar. Below, a pretend send stream is running. Pull the switch, then watch the two things that happen: the sends stop, and the safety lane carries on.
The bar: seen within 10 seconds, nothing sent after. The benchmark’s slowest stop: 287 ms.
A reaction arrived while the switch was down. The customer was acknowledged and the pharmacist told anyway — protective steps are the one thing the kill switch never pauses.
Safety work never waits for a model — and it never waits for the switch either. Everything else stops: replies, order updates, warehouse writes. The lane that protects a customer keeps going.
That is the contrast the project page states as a benchmark: seen within 10 s; nothing sent after — 287 ms; 0 sent.
Nothing leaves Company OS without joining the record. Follow the reply you approved a minute ago — the customer’s message, both checks, your passkey, the send — down to the row the record sealed. Every step below is real in shape; the names are made up for this page.
The morning brief you read in step 1 is built from rows like 4,221 — one chained, sealed entry per action. Months later, a regulator, a partner or you can walk the same chain and see exactly what happened, in the order it happened. Nothing edits a sealed row; new events chain after it.
It runs in your browser with made-up data. Nothing to install, nothing saved.