Skip to content

Chapter 07

Surfaces

Twenty templates, composed from the component library and nothing else. Each tile below shows the artwork the template renders and links the folder that holds it. The folder's README carries the copy slots, the dimensions, the print specs and the render command.

Online

Everything that ships as pixels. The deck and the document are page systems; the Instagram set is a grid spec with seven tile templates under it; the two email templates are the only house artefacts that carry their values as literals, because a mail client ignores custom properties.

Offline

Flat print artwork. The identity is print native by construction, which is what won it the direction: ink on paper plus one spot colour, and chrome carrying the one substitution.

Briefs

Three sheets that go out to somebody who is not us. Each is built on the document frame, so a vendor reads the identity before reading the instruction.

Surface layers, and the rule that keeps them apart

A surface applies a subset of the house identity and adds constraints that are true only for it. A surface may narrow the house layer. It may never widen it and never contradict it.

Where each surface's narrowing is written down
Surface Its layer file Status
Brand audit, private per client audit.md Applied subset. The one surface with a production system behind it.
Landing page landing-page.md Scoped, not built.
Proposal and document proposal.md Scoped. The document template above renders it.
The web in general web-guidelines.md Layout, breakpoints, rhythm, accessibility and performance floors, the ship checklist.
App, social frame, deck None yet Listed in scope-statement.md. No narrowing on record, so each inherits the whole house layer.

The worked case, which is the reason the rule exists

The audit forbids every signal. No band, no data colour, no highlight, no severity badge, no status pill, no colour only legend. In the audit build the tokens are absent, which is stronger than a rule telling people not to use them.

That constraint is correct for the audit and wrong for the house. The audit reader is the subject of the document, so a field next to a finding reads as a verdict on them. On a landing page nobody is being graded, and the same band reads as the hero band. So the constraint stays in the audit's own file, marked surface scoped, and never appears in the colour document as a house rule.

The test before anything is promoted from a surface to the house, yes or no: does the constraint hold on the landing page, the proposal, the app and a social frame, for the same reason? One no, and it stays where it is.

The carve out runs both ways

The person pair is audit only. A brand surface codes its data in blue and has no person colour. Data is blue is a brand surface rule. Two people are those two values is an audit rule. Neither of them is a house rule.

Chapter 07 of the Unforged brand book. The templates live under 03_CREATIVE/04_TEMPLATES/; each folder carries its own README, its rendered artwork and the script that cuts it. The layer rule is 01_IDENTITY/01_BRAND-LAYER/layer-model.md v3.