Monday, September 28th, 2026

I learned that semantic versioning can't tell you which features are ready. However, feature certification can.

Creature Workshop Weekly Roundup

I'm building a language for the development lifecycle itself, and an open-core ecosystem on top of it. Every Monday I’ll be running a one-man sprint retrospective, and this is what came out of last week's work.

The Big Picture

Time for a Redo

This week I had the privilege of sitting in on a staff meeting over at Redo up in Draper, and got to hang out with amazing Kyle Hilton (No relation to Paris, but 2nd cousins once removed from me) and the illustrious Matthew Brown (also no relation to Paris).

The energy over at Redo is unreal. Folks like Kyle and Matthew mean business, and the engineering crew all seem tight knit, friendly, and generally actually happy. People feel like people, and care about delivering on something meaningful for their customers. It’s been a while since I’ve seen that kind of raw drive. I guess that’s the reason why they were recently valued at over $1B - which for a company of less than 500 people is insane.

Their company recently hit enormous success, and as a result Redo’s filled to the brim with work to do. It makes perfect sense that they're striking while the iron is hot over there. They’re putting their best foot forward together as a team to scale with their growing customer base.

A pace like that isn't for everyone. But for the time I was there talking with the staff, it seems like a fantastic place to work.

Certification as Configuration

I realized something recently. Even with an efficient merge queue and CI/CD setup coming down the pipeline¹, the validation and promotion of commits is basically always going to be expensive on some level. That’s because you can’t leave anything up to chance. Eventually you have to run the full suite of tests before you ship code out to production.

There’s a heck of a lot of wiggle room in the word eventually, though.

Not every changeset is going to need every test in the suite to validate it. Not every change to every feature is worth blocking a production release. That’s the core idea behind dynamic test selection. You can carry the benefits of this idea—set decomposition and subset selection—over to versioning and promotion as well. I call it feature certification, or tracking feature certificates.

Why does versioning need it though? Because a semver tag tells you a release passes the tests and should be compatible with consuming code. However, it doesn't guarantee which features in it are actually ready for dependents to rely on them.

An Analogy: Uptime

Think of how massive companies like Google, Meta, Cursor, Anthropic, and others operate. They keep a live report of their uptime and the current status of their services. Google as a whole never goes down,² but a service or two of theirs might have a regression from time to time, which shows up on their status dashboard with a timeline of reports trailing behind it.³