Structure
What the firm is claiming, in what order, and which claims have to be provable. Architecture before layout.
The surface is the instrument a firm gets judged by before anyone speaks to it. Zyrn builds it the way it builds an operating model — structured first, measured continuously, and handed over so the team can extend it without calling us.
This is the page as anyone arrives at it. Everything after this is what it is made of, and every one of those things is written down somewhere a developer can read.
Six modules. Structure is settled before a pixel is drawn.
What the firm is claiming, in what order, and which claims have to be provable. Architecture before layout.
Tokens, type scale, spacing, motion law. Written down, so the surface can be extended without a redesign.
Static where static is correct, dynamic where it earns it. No framework the firm cannot maintain itself.
Frame time and payload are acceptance criteria, not a pass at the end. A budget, not a hope.
Contrast, motion preference, and keyboard paths are part of the build. Not an audit afterwards.
The team ships a new page without asking how. That is the exit condition, and it is written into the engagement.
Three phases, the same three every line runs. Measured at each one.
Four to six weeks. Surface audit, structure audit, and the distance between what the site claims and what it can show.
One to two quarters. System documented, surface built, performance and accessibility held to budget.
Ongoing. The surface is versioned like software, because that is what it is.
Signals the diagnostic watches, and the direction they are expected to move.
Three decisions before anyone writes a proposal: what the site must do, how much it may move, what it starts from. The diagram is the engagement, redrawn as you answer.
The engagement closes when the firm can extend its own system without asking how.