Methodology, not marketing.
Everything published here operates under the product's honest-claims policy: measured numbers, named methods, dated posts. It's a slower way to write - and the only one worth reading.
Three things we write about
The tags below the fold map onto these - anything outside them doesn't belong on this blog.
Methodology
How we measure before we claim: benchmark design, savings floors, false-positive accounting. The receipts behind the receipts.
Security explainers
Zero-trace, signing, fail-closed design - written for the engineer who has to defend the decision internally.
Build notes
What shipped and why it's built that way. The narrative companion to the build log's bullet points.
All posts, filterable
Filter by tag or load more below - the list is every post, not a curated highlight reel.
Rules every post is held to
The same discipline that keeps invented numbers out of the product keeps them out of the prose.
Claims carry measurements
If a post states a number, the post explains how it was measured - or the number doesn't appear.
Dated and left standing
Posts keep their dates and their mistakes. If we learn better, we append a correction rather than silently rewriting history.
No content-marketing filler
No “10 AI productivity hacks”. Three good posts beat thirty written for a keyword.
Test the writing against the product
Every methodology post describes something you can reproduce with your own install. Read one, then run it.