Blog

The Ze blog.

Design notes, deep dives, and engineering essays on how Ze is built. For week-by-week shipping notes, read the changelog.

Article

Keeping documentation in step with the code

Ze generates public reference from its code and records, with links to the decisions behind them. Operators and future AI sessions can use the same maintained account of the system.

Read the article
Article

AI coding has not had its Rails moment

AI coding needs shared conventions for connecting requirements and design decisions to their implementation, and for keeping those relationships current.

Read the article
Article

The repository is half the AI harness

Ze's development rules define what an AI agent must achieve and how to check the result, including the qualities a working demonstration can leave untested.

Read the article
Article

The proof is the expensive part

Ze aims to meet every applicable mandatory RFC requirement. Interoperability labs and tests tied to the RFC text help establish what the running router does and which claims remain unverified.

Read the article
Article

How Ze reuses memory for BGP UPDATEs

From the Amiga demo scene to BGP UPDATEs, earlier experience informs how Ze reuses memory and avoids unnecessary allocation in Go.

Read the article
Article

AI slop is human slop

AI often writes better code than I would, and far more tests per feature. I judge that code by what it does and the evidence behind it, and remain responsible for what Ze releases.

Read the article