Two numbered collections about building software. They answer different questions, so it is worth knowing which one you want.
ZFN-N · 66 published
Short, numbered positions on how to build software well — and the open problems I haven't settled yet.
Read one when you want the reasoning behind a practice, and to argue with it. About a thousand words, and it takes a side.
ZBP-N · 6 published
Normative implementation specifications, versioned and numbered to the requirement, written to be handed to a builder and built from.
Read one when you have to build the thing. Five to fifteen thousand words of numbered requirements, pinned to a major version, meant to be handed to whoever — or whatever — is doing the building.
In short: a note argues a position; a blueprint specifies one. Where a practice needs more than reasoning to act on — a wire format, a validation order, requirements you can hold an implementation to — it gets written up as a blueprint instead.
Both collections are published as data as well as pages: notes.json, blueprints.json, and llms.txt for agents.