Where This Stands — Where It Started and What We Are Proposing
Thirteen pieces set two axes: who owns the business, and who owns the window. This one folds them into a paragraph, states where this started with the public record, and says that the seat for constrained environments and physical devices is still empty. Including what the domain does from here.
What Makes This Different — Two Kinds of Resemblance, and Who Owns What
Two things look similar to this. One runs apps inside a device; the other opens a window while a model is talking. Fourteen pieces on why neither overlaps — asked not as what it does, but as who owns it.
View VolHorizon
- Where This Stands — Where It Started and What We Are ProposingISSUEFREE
Thirteen pieces set two axes: who owns the business, and who owns the window. This one folds them into a paragraph, states where this started with the public record, and says that the seat for constrained environments and physical devices is still empty. Including what the domain does from here.
- Same Machine, Different Hands — Authority Per Channel, Verification Left Where It WasISSUEFREE
The wheelhouse console gets full control, the captain's tablet gets instruments, the phone on deck gets alarms. Same equipment, and what opens depends on where you attached from. The party that decides those grades is the party that built the device. Safety-critical domains keep outside software out for liability, not performance — and this structure does not move the liability.
Build
- One More Device Attached — The Host Was Not TouchedISSUEDEV
Putting several devices on one screen normally means the host writes the joining logic, so every added device means editing the host. Here that joining moves down into the document. We put three devices on one page, added a third, and checked whether the hash of the host binary changed. Then we killed one.
- There Is No Such Unit as an Install — Edit It and the Next Connection Already Has ItISSUEDEV
In the world of installed software the unit of distribution is a binary, so changing one line on a screen means building, reviewing and downloading. Here the unit is a document handed over when you connect. Edit it, open it again, and that is the screen — the unattended-store sample carries before and after in the same run. And this is also why there is no owner of a store.
Field
- The Counter and the Cab — Where the Screen Stands When Money MovesISSUEDEV
In a shop and in a vehicle the screen touches money. This piece writes down the arrangement that serves three different screens to three seats without touching the payment terminal's certified path or the meter's regulated arithmetic, and where the −0.6 won of rounding happens exactly once, taken from the scale's screen and the taxi run log.
- One Line, Many Boards — Where Screens Divide on a Production FloorISSUEDEV
A production line has one set of numbers and several people reading them at different densities. The shift lead reads this minute, the manager reads the day, quality reads one window. Until now that was one development project per screen. When the description sits on the device side, the arithmetic changes. Plus what actually went wrong getting values onto an instrument screen.
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.