The ward opened last night. 21 Sep 2026, 21:30 ICT — two and a half hours after the 19:00 we had announced to ourselves, because the founder's cloud login expired at 18:52 and the deploy identity was missing one IAM permission. Nothing clever; just the ordinary way a deadline goes.
Three patients are in beds right now, and they came from where the globe says the shortage is: Eric Habimana (Rwanda), Juma Shabani (Tanzania), Nelson Tau (Papua New Guinea). Twenty more are queued. 75 cases are placeable, every one of them marked provisional — not yet reviewed by our clinical advisor — and the ward says so on the board, at the bedside, and on every receipt.
Nobody has taken a shift yet. 381 people have opened the globe since the door turned; zero shifts are anchored on chain. That is the honest headline three hours in, and we do not yet know which of two things it is: people are not arriving at a patient at all, or they arrive and do not know how to begin. Those have opposite fixes — one is an announcement problem, the other is a page asking a stranger for something they have not been taught. So the next deploy ships two counters, bedsides opened and shifts taken, and the answer decides whether we build a tutorial or go and tell people the ward is open. Building the tutorial first would be building for a thing that might not be broken.
What went in before the door opened, measured on staging:
Boot 41.6 s → ~6 s. The tape repair was running before the port opened; a visitor arriving during a start waited for work nobody had asked for.
The every-minute ward pass, 100 s → ~4 s. It was listing every patient's chain history three times per pass against a rate-limited public endpoint. Now it asks the chain's own shift count first and lists only what moved.
The pass became a route. Cloud Scheduler calls it every minute, single-flight, because the container only gets CPU while it is answering a request — an in-process timer on a quiet ward has nothing to run on.
One 429 no longer blacks out the board. A single rate-limited history used to make the whole ward unreadable; now that patient's row says her chart may be a shift behind and the other twenty-five stay fresh.
Four correctness bugs, all found by reading rather than by failing: a boot that could delete the only copy of a tape it was about to restore; a refresh gate that one panic would have stuck for the life of the process; a pass that trusted a half-read history for a decision that writes to the chain; and a refill that would have admitted a patient onto a case the clinical advisor had withdrawn.
The lesson keeps arriving in the same shape. Last night the page said "open for play since 21 Sep 2026" for two hours while the door was shut and nobody could take a shift — because I built that sentence from a date instead of from the door. A claim composed from a constant cannot be wrong, because nothing checks it. The fix, as every time this week, is a test rather than a better sentence.
Devnet. Free. The door is open at world.vitals.academy — and if you take a shift, the next stranger starts exactly where you leave the patient.
Opening film: https://youtu.be/uOpv-_d7-s0
Give feedback to the team
Your message is private to you and the Vitals World team.
Create an account to send feedbackAfter signup, you can write a private message with this update attached.