Week four of July. What these four pieces share is what was not built.
This week's Signal
The screen stopped asking. "The Screen That Never Asks" removes the kitchen screen knocking on the server every second. The server tells it when something changes. What matters here is that the notification does not carry what changed. It says "changed," and the screen reads again. Put a value in the notification and the day it arrives out of order, the screen is overwritten with the old one.
Safe because the tool does not exist. "The Tool That Refuses to Read" has no verdict tool. Not locked — absent. And if verdict vocabulary tries to reach a response, the server throws rather than quietly stripping it. Strip it and it goes back in next time.
A rubric is data. "The Standard Stays Yours" holds no code that decides what a good answer is. That is data the teacher wrote, and the tool only quotes it. A score with no grounds beside it can neither be appealed nor answered.
And April's claim got paid. "What You Don't Expose" backs the second knot of "every server is an app" with execution logs. A capability absent from the tool list really is unreachable.
Tool and package notes
One thing confirmed while wiring subscriptions: notifyResourceUpdated(uri) sends only the uri. That is right by design — notifications guarantee no ordering, and carrying a value means a late notification overwrites a newer one. Receiving "it changed" and having the reader fetch the latest is always correct.
A short thought
One sentence runs through all four pieces — what you finally refuse to build is the shape of the tool. You do not get safer by adding features. Not adding a verdict tool, not putting values in notifications, not writing grading code. All three are removals, not additions.
Next week
On to two real boards on the desk. The last week of this month runs with no simulator.
makemind.dev "Signal" — once a week, what went up and what got in the way while building it.