The Frozen Template Constructor: whole structures, composed not generated

Last week we shipped a way to add a page group by thawing a frozen template. Using it taught us the real shape of the problem — and a cleaner answer. Adding a structure to a site has several independent dimensions: how deep the hierarchy is, where the data comes from, who may see it, which languages. A catalogue would need a finished template for every combination — hundreds of them. So instead of a catalogue, the Agentic Engineering Infrastructure now uses a constructor.

A constructor, not a catalogue

Think LEGO: a handful of well-made bricks compose into an enormous space of models. The constructor keeps a small basis of vetted frozen bricks and a few rules for assembling them. It composes a structure to order — and, crucially, it never generates code. Composition copies and wires proven pieces, so the built-in brain and every coding agent produce the identical result, fast and cheap.

Two slots, and one rule that keeps it simple

Every property of a structure lives in one of two slots: a list provider (where the items come from — files, or a database read at build time) or a uniform aspect (a rule applied identically at every level — languages, or who is allowed to see it). The two never interact. That single discipline is what stops the design from exploding: a role rule is the same rule whether the structure is one level deep or four, file-backed or database-backed.

It matches your request — or refuses honestly

Each brick declares an envelope — its position on every axis (data source, depth, static or dynamic, roles, languages). A request matches a brick only if it fits on every axis. Ask for a news section and it composes one. Ask for something no brick serves — a live dashboard, a shopping cart, a deep database catalogue — and the agent tells you exactly which axis does not fit, then offers to build a new brick (once the shape is proven) or to use classic development. It never forces a bad fit and never invents fragile code. The same honest-matching idea powers our note on multilingual content architecture.

Grown one proven brick at a time

The constructor does not pre-build every possible structure — that would be the same unscalability from the other end. The grid of possibilities is a map, not a build plan: a cell is frozen into a brick only once it has proven itself in real work and repeats. Today there is one reference brick (a flat, file-backed, multilingual list — news, blog, docs); the rest are on the roadmap, each built when it earns its place.

I want the boring, repeatable parts of building software to become a single sentence you say out loud — and the result to be correct, yours, and on your own machine. The constructor is that idea, made disciplined.