What ended up living in the brand
Hundreeds illustrations in the first cycle — across the site, marketing, presentations, and events. All of them obey one visual language and read as "servers.com" without a logo in the frame.
Principles of the visual language
Before touching any model, I locked down what a "servers.com illustration" had to be. These six principles aren't a style description — they're the interface to the system. Using them, I can decide in under a minute whether a given generation is publishable.

Agent setup
The system runs as a configured agent — not as a clever prompt typed each session. Its instructions carry company's principles, the prompt template, and the rejection criteria, so the brand language holds even when someone else operates it. The screens below are the actual setup that ships these illustrations.
What I learned
The thing I take away from this project is that the designer's role in the AI era doesn't disappear – it shifts. I made fewer illustrations by hand than I ever had. And at the same time I owned the brand's visual language more tightly than I ever had.
A system architect isn't an operator typing "cinematic 8k masterpiece." It's the person who decides which principles hold the style, which steps in the pipeline don't get delegated, and where the line runs between "works inside the brand" and "averagely beautiful internet picture."
AI took execution off the table. The designer's job is to describe the system so precisely that execution doesn't break the meaning. That's the next iteration of the craft.