Nothing Is Overwritten — What an Inherited Notebook Needs to Be Useful
In 2026-05 we ran a piece about inheriting a father's work notebook. The difficulty of an inherited record is not reading it but not knowing who knew what and when. This time we built it — here nothing is overwritten. A line proved wrong stays exactly where it is, and why it was believed stays readable.
Latest Vol · VOL. 8
Down to the Floor
A queue, a picking route, a shift handover, a till with the network gone. Ten field tools on what a screen has to survive when it stands where a person stands.
View VolHorizon
- What You Do Not Expose Protects the App — Every Server Is an App, and What Comes AfterISSUEFREE
A server becoming an app does not mean putting every capability on a screen. What you never turn into a tool is the shape of that app, and its safety. We made that argument in 2026-04 and deferred it with "the next pieces will show you". This time we do not defer — that a capability absent from the tool list really cannot be reached is paid back in execution logs and a real board's answers.
- Sitting Down Without an Interpreter — Where One Piece of Judgment Becomes a RuleISSUEFREE
In 2026-03 we wrote that "eight tenths of a tool is judgment, and that judgment is already in your hands". How those eight tenths sit down on a screen without an interpreter was stated only in prose. This time we pay it in real things — a farmer's piece of judgment was seven lines, and the verification stops the foreman's checklist from having a single character changed.
Build
- Swap the Sensor, the Control Stays — How Not to Build a Greenhouse TwiceITEMDEV
The real reason greenhouse controllers are expensive is that sensors and control are wired 1:1 inside the code. Let the nodes declare themselves and write rules by kind rather than by model, and swapping the temperature probe leaves nothing to fix. A record of running two different greenhouses on the same server and the same rules.
- Attach to One Chip and the Attached Device Becomes the Terminal — POS, Kiosk and Kitchen Screen at OnceITEMDEV
One server stood up beside the payment terminal already in the shop, with a tablet, a PC and a kitchen screen attached. No app was built for any of the three, and each became a kiosk, a POS and a kitchen display. The card authorisation path was not touched by a single line. Full code, run log, and the three screens exactly as rendered.
Field
- Nothing Is Overwritten — What an Inherited Notebook Needs to Be UsefulISSUEDEV
In 2026-05 we ran a piece about inheriting a father's work notebook. The difficulty of an inherited record is not reading it but not knowing who knew what and when. This time we built it — here nothing is overwritten. A line proved wrong stays exactly where it is, and why it was believed stays readable.
- The Tool That Refuses to Read — Keeping Judgment Outside a Clinic FlowITEMDEV
In 2026-04 we ran a piece about a doctor building a clinic flow tool. That piece stated in prose what the tool does not do. This time we drew it in code — this server has no tool that produces a judgement, and it throws if it tries to emit a word that sounds like a verdict.
Signal
View all- Two Real Boards Found a Spec Violation
The last week of July, run with no simulator. An STM32H723 on the desk and an ESP32 across Wi-Fi each handed over their own screen — and along the way it emerged that our client was violating the MCP spec.
- A Screen That Never Asks, a Tool That Never Judges
Week four of July. The kitchen screen stops polling and the server says only "it changed." And the clinic flow tool has no verdict tool at all. A week about what was left out.
- Where It Said Yes Twice — Where Duplicates Come From
Week three of July. Two bookings land in the same slot, and a retry creates one more order. Both were problems inside the server, not on the screen. Plus a farmer's judgement became a seven-line rule.
- The Screen Arrives From the Server — and Who May Press It
Week two of July. A screen definition arrives from the server and gets drawn, and permission is stopped at the tool boundary rather than on the screen. Plus the two launch-issue vision pieces paid back in measurements.
- First Week of a New Chapter — Starting Again From One Server
The first week of July. If the past six months were "this works," this chapter is "so how do you build it." It opens with one server running inside a chat window and a 45-line tool made on a weekend.