Blog
Notes from the build.
The site that remembers itself
This website's deploy pipeline is now an Empress consumer: every deploy writes itself into the production ledger, and the observatory reads the receipts back. Dogfood, mechanized.
The docs can answer you now
We moved the documentation onto a real engine — full-text search, a sidebar, per-page contents — without giving up the two things that mattered: the monochrome brand and references generated straight from the code.
The data layer for behavior
Software records money, files, and messages with permanence. Behavior — the actual sequence of what agents and people did — evaporates. That gap is a category, and it's the one Empress is building.
We deleted our own marketing
The old empress.eco claimed a certification we didn't hold and quoted customers that never existed. Here's what we replaced it with, and the rule that governs every page now.
Behavioral infrastructure with receipts
Why Empress is a ledger, not a logger — and why that distinction is the whole product.