A portfolio argues that you can design and build things, then sits unchanged for years, which quietly undercuts the argument. The decisions behind it are invisible, the process is hidden, and none of it is falsifiable.
Each morning a pipeline of Claude agents rebuilds the site from nothing. An art director reads the day's signals and writes a specification: a composition drawn from eight independent axes, a type and colour scale, the hero line, and whether the page carries a shell at all. A mockup designer renders that specification at full fidelity, an engineer rebuilds it as the real site, and three separate critics can send any of it back. What the agents may touch is enumerated in a list. The content files, this sentence included, are refused at the write layer.
Every design it has made is preserved exactly as it shipped, each with the brief that produced it and a score for how far it strays from the week before. The site is its own archive and its own evidence. The stack is TanStack Start in SPA mode, PandaCSS for tokens, and Vercel for hosting and CI.
Chad Fowler argues that once a machine writes the implementation, the architecture is whatever you cannot delete. He is writing about code. I wanted to know whether the argument holds when the thing being regenerated is visual design, where correct is a judgement rather than a test result.