Ryan Perez · Style-guide system

A brand book shows. A guide decides.

Given this communication, this audience, this medium and this condition — what should the creator use, and what must they avoid? A guide that cannot answer that is a gallery. This page is the governance layer over every other system in the library: where a rule lives, who may approve an exception, and what stops an execution from shipping.

The test If a rule cannot change a design or writing decision, it is not operational enough to be in here.
Routing

Seven systems. They connect; they are not the same thing.

Most brand books rot because everything gets filed in one document. The routing rule below decides where a new rule belongs before it is written.
{{ s.a }} {{ s.b }} {{ s.here }}
{{ r.a }} {{ r.b }}
Architecture

Twenty sections, zero indexed

Governance is section 00 because a guide whose version is unknown is not production-ready. Blue sections already exist in this library.
{{ l.t }} ✓
Keep from the classic template

What a 103-page brand book already gets right

{{ k.t }}
The single strongest device in the classic format is showing approved behaviour and the common error side by side. A rule without a counterexample stays abstract.
Missing layers

What a static brand book has no answer for

{{ m.t }}
Built in this library Still open
Section 00 · rendered

The status block, as it ships

Page one of the guide, not an appendix. If a creator cannot read the current version off the front, everything downstream is a guess.
Style guide
Approved
{{ f.k }} {{ f.v }}
Authorised use Internal team, contractors and vendors, for work commissioned by the studio. Assets are licensed for that work only and do not transfer with a completed engagement.
Governance rules

Six, and the deprecation clause

{{ r.a }} {{ r.b }}
The failure mode An old logo left in a shared drive is a live logo. Deprecation is a distribution action, not a note in a document — pull the file or mark it in the filename, or it will keep appearing for years.
Change log · rendered

Every entry names the rule, the reason and the approver

{{ h.t }}
{{ c.date }} {{ c.ver }} {{ c.what }} {{ c.why }} {{ c.by }}
An approved exception is logged with its condition, not folded silently into the rule. Otherwise the next person inherits a rule nobody can explain.
Values, operationalised

Belief + behaviour + evidence

A value that names no behaviour cannot be followed and cannot be audited. Each one carries what to do and what that rules out.
{{ v.name }} {{ v.belief }}
Behaviours {{ d.t }}
Rules out {{ d.t }}
Voice dials

Seven dimensions, set per context

Marks show the standing position. Stable traits never move; the dial is what adapts.
{{ d.k }} {{ d.setting }}
{{ d.low }} {{ d.high }}
Context

Eight audiences, one brand

Different expression, not a different brand. The right-hand column is what actually changes on the page.
Context Expression What moves
{{ c.a }} {{ c.b }} {{ c.c }}
{{ r.a }} {{ r.b }}
The strongest device in the format

Use, avoid, and why the rule exists

Both sides rendered, never described. The third column is the part most guides omit — and it is the only column that lets someone reason about a case the guide never anticipated.
{{ p.n }} {{ p.t }}
Use
Book the audit Accent on canvas, white on accent. contrast 5.9:1 · 8.4:1
Section 02 Where the system forgets you Two roles, one weight change. Hierarchy from scale, not from decoration.
Photograph
Not a metaphor.
Qualified leads rose 41%
n=14 client funnels · Q1–Q2 2026 · no control group
Generated diagram
Illustrative · AI-generated
{{ p.goodNote }}
Avoid
Book the audit Accent on accent-tint, body text dropped to 35%. contrast 2.1:1 · 2.6:1
Section 02 Where the system forgets you Five styles, three weights, an underline and a colour — all doing the job scale should do.
Photograph
Not a metaphor.
Massive growth
Axis starts at 38 · no n · no period · seven hues
Generated photo of a “client”
Calgary, 2026 · on site
{{ p.badNote }}
Why the rule exists
{{ p.why }}
Exception {{ p.exception }} {{ p.approval }}
Five levels

What triggers escalation

The band shows the escalation. Most work sits at level one — the point of a system is that correct use of an approved template needs no meeting.
{{ a.t }}
{{ c.a }} {{ c.b }}
Escalation rules

Six triggers

{{ r.a }} {{ r.b }}
Publication gate

Ten conditions, all required

Not a scored checklist. Any single failure blocks release.
{{ l.t }}
Production

Requirement selects the format

{{ f.a }}{{ f.b }}
{{ r.a }} {{ r.b }}
Selection engine

Twelve steps, in order

Purpose and audience before assets. Steps nine through twelve are the ones that get skipped.
{{ s.n }} {{ s.t }}
Agent contract

One rule, machine-readable

Every style rule in the library takes this shape: conditions, alternatives, accessibility, approval level, and its LAKA states.
{{ l.t }}
LAKA states

Ten guide maturities

{{ l.a }} {{ l.b }}
This library currently sits at Combination — brand guide plus design system plus agent rules — with Inversion already applied, since every page starts from a decision rather than an asset.
Coverage

Which page holds which section

{{ c.a }} {{ c.b }}
The governing principle A style guide should not merely show what the brand looks like. It should explain how to make correct brand decisions under different conditions. What to use, what to avoid, why the rule exists, and who may approve an exception. A guide that answers only the first of those four produces work that is on-brand by luck.