Engineering notes from building Itiner, Odd Bits and Nucleus CSS.
How we build interface systems that stay predictable as they grow, for humans and for the AI tools that now write a lot of the markup.
Notes on the frontend architecture choices behind Itiner, what we render where, and why.
Where AI does real work in the products: drafting, regenerating, and the constraints that make that safe to ship.
What we ship as a default, not a configuration option, grounded in what Nucleus actually includes out of the box.
Work that isn't a customer-facing product yet, kept clearly separate from the ones that are.
