July is the month this magazine changed its volume. From February through June it ran three pieces a month — one vision, one build, one field. July ran fifteen.
What went out
| Track | Count | What |
|---|---|---|
| Build | 8 | six server apps · two real boards |
| Field | 4 | club dues · growing log · grading · clinic flow |
| Vision | 3 | three earlier claims paid back in measurements |
It is not only the count that grew. Eight of them run as a series. From raising one server through serving screens, permission, duplicates, retries and subscriptions, in one line. That is what separates this from the previous half-year of collected one-offs.
This month's discipline
From July, articles carry a verification gate. Every sample has a verify.sh, and it has to pass before the article goes out. The gate does not check "it runs" — it checks what the piece claims.
- The screen came from the server → fails if the host code builds widgets
- It cannot reach the footage → takes a real
tools/listand sweeps it for forbidden words; fails on a hit - Rounding happens in one place → fails if the server has two
.round()sites
And captures are not taken by hand. They come from RepaintBoundary.toImage inside a test — if the screen does not draw, the capture comes out empty and verification stops there.
Real hardware argued back
The cheapest and most important lesson of the month. Attached to a real board, our client died. The cause was not the board but mcp_client 1.1.1 casting a field the MCP spec makes optional as required. Raising it to 2.1.0 resolved it.
A simulator-only run would never have surfaced it, because a simulator we wrote answers the way we understood things. The operating rule July leaves behind: at least one piece a month has to run on real hardware.
What is still empty
First, readers cannot get the code. Every article has a "run it yourself" section pointing at a working-folder path. All 27 samples are already self-contained, so only distribution is missing — and there is no distribution path yet. The one thing that distinguishes this magazine is "go run it," and we did not give a way to run it. That is August's first priority.
Second, there are no numbers a buyer uses. We counted 656 bytes and 11 milliseconds; we did not count how many engineer-months it takes to put a screen on a product. The code is all there, so it can be counted — arithmetic, not invention.
Third, build is not yet a course. July's eight are a series, but January through June ran one a month. There is no track that walks the basics in order.
Next month
Down to field terminals — a queue, a picking route, a shift handover, a till with the network gone. And closing the first of those three gaps is August's condition.
makemind.dev "Signal" — the 2026-07 close.