Signal

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.

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.

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.

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.

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.

Four pieces close the first six months. A hash check confirmed twenty-seven samples stand on one runtime, and the chapter ended on who stands in front.

Closing six months. The through-line from vision to the field, the people met along the way, and the next half-year. The last Signal of a chapter.

Five stages were one pattern. "All of This on One Runtime" — a week where evidence becomes a catalog and an anecdote becomes a frame.

One person doing the work of many hands — PM Han Ji-yeon's flow, and tax accountant Yun Jae-seong, who stopped missing deadlines. What happens when the domain stands at the front.

The final month has opened. Six months of stories tie into one — "The Age of the Domain Expert," and the moment the order is reversed.

Three pieces in May. Heterogeneous sensors stood on one runtime, and an inherited notebook was made correctable without erasing. For experience to compound it first has to be the same shape.

Closing out May. The single picture that appears when the three threads — declaration, floor, real thing — stack up over a month, and a preview of next month.

The inherited notebook. From Han Seok-gyu through Han Do-jin to Han I-su — the story of three generations' paper notebook becoming a tool that lives and grows.

Scattered sensors into one shape. What "scattered sensors on one runtime" showed — the lowest floor where multiplication begins.

A new month, a new thread. "Experience Multiplies" opened the door — a single sentence saying that experience stacked in the same shape doesn't just endure, it grows.

Three pieces in April. The proposition that a server is an app, a dashcam with the video tool removed, and a clinic flow that keeps the verdict outside. All three are stories about removal.

The week that closes April. The place where experience becomes a flow and a flow becomes a tool — wrapping up Han Do-gyeong's story, and previewing May.

How the boundary gets drawn. When designing capability as tools — what to offer and what to close — a week handling the line between exposed and unexposed.

A week taught by a single black box. The screen is rich, yet a video-editing tool simply doesn't exist — integrity kept by the absence of a tool.

The week that opens April. The ripples set off by a single sentence — "every server is an app" — and the discovery that not exposing something is itself integrity.

Three pieces in March. Instruments already speak SCPI, and a teacher already has a marking standard. What was missing was always one axis — the screen.

Closing March — the three threads of person, machine, and field converge into one sentence, "just add one axis." And next month.

Han Mi-jeong (41, middle school Korean language, 4 classes of 132) built her own grading tool herself. The 80% was hers all along.

An instrument with no dedicated software gains an operation screen from a single sheet of definition. How "laying on" actually happens.

A single line as March opens — you already hold 80%. What's missing is just one axis called the screen.

Three pieces in February. What compiling freezes was set out, and that ice was removed from the screen layer alone — once on a chip, once in a field.

The week that closes February. What was left where compilation used to be — chip and farmer reach the same conclusion, and the threshold of March comes into view.

So who makes it? Leave compilation behind and the circle of makers widens. The week a farmer becomes the owner of his own tool.

Where does the screen live? The definition lives on the server, the screen lives anywhere. A chip gets its screen, a farmer draws his first field.

A new month opens. The first question posed by "Leaving Compilation Behind" — don't freeze your decisions. Melt the screen layer; freeze the capability layer.

The first month. Five pieces. It began with one proposition — define the screen on the server instead of burning it into the device — and got as far as a first screen in ten lines and an HMI in thirty minutes.

The week that closes the first month. Where vision, proof, coding, and cases become one picture — and the story of non-developers reaching for it first.

A week after the launch volume and the first hardware proof. The question "could my industry do this too?" — and the people who got their first screen running.

The week right after the launch volume. The split between "does that really work?" and "we were already doing that" — and the one question we got most.

Before the launch. What this magazine will track each week, and where it's looking right now.