The deliverable
Six interconnected layers.
A brand system is not one document. Each layer is a standalone file with its own audience and its own job.
Brand Book
Purpose, mission, vision, values, promise, positioning, differentiation, story, architecture, naming — plus audiences, ICPs, five buyer personas, jobs to be done, triggers, objections, and the open-facts register. The canonical domain is now settled.
Open Brand Book →Visual Design System
A full logo chapter — variations, palette, clear space, colourways, sixteen misuse rules, the master-file suite. Plus the navy and teal system, four-band tokens, Manrope and IBM Plex Mono, the wave motif, four reveal types, ~60 components, eleven breakpoints, and three verified contrast failures.
Open Visual Design System →Messaging Playbook
Master narrative, 25/50/100-word descriptions, boilerplate, four messaging pillars, an eight-row messaging matrix, verbal identity, the settled spelling rules, ten objection scripts, CTA library, taglines and approved claims.
Open Messaging Playbook →Communications & Content Playbook
Format standards, sensitive-content rules, crisis communications, the sales asset inventory, discovery framework — plus governance: the CMS workflow, ownership, approvals, file naming, AI policy and the open-items register.
Open Communications Playbook →Brand Asset Library
Far more exists than first appeared — a design system in code, a fifteen-block template library, three guides, a multilingual runtime. The real gaps: logo master files, photography, contact values and sales collateral.
Open Asset Library →AI Brand Kit
The system as machine-readable instructions: a master system prompt, ten task prompts, an image prompt library with real brand hex values, and a validation checklist. Ships with ssz-brand-kit.json — 25 structured domains.
Layer 01 · Foundation
The idea the whole brand rests on.
The best writing on the site, and the truest expression of the brand. It sits in two separate sections of /approach/ — both quoted exactly as they appear.
Most roadway safety problems are not a mystery to the people who live with them. A particular approach, a particular stop, a particular work zone — someone already knows it is a problem. What is usually missing is reliable information about what is actually happening, and a defined way to act on it.
Hero, under "Technology is only part of the solution."
SaferSmart Zones exists to close that gap. We help organizations identify a behaviour worth changing, measure it properly, understand the pattern behind it, and build a program that responds — with public awareness, operational change, enforcement, or some combination of the three.
Under "Why we exist" · "From a described problem to a defined response."
Purpose
To close the gap between a roadway problem people already know about and a response an organization can defend.
Brand promise
You will be able to show why you acted. Everything the platform does resolves into that one promise.
Four things we hold to.
Stated on the site, and unusually good — specific, falsifiable, written with a point of view. Adopt verbatim.
Data before decisions
A program built on an assumption is a program that will be argued with — by council, by the public, and eventually by a court.
Technology with purpose
Every deployment is tied to a defined challenge in a defined place. We are not interested in monitoring for its own sake.
Awareness that connects
Awareness is not a consolation prize before enforcement — it is often the part that changes behaviour.
Action with confidence
Validated information and a reviewable record are what make a decision defensible after the fact.
The category to claim
Buyers default to filing SSZ under automated enforcement / red-light camera vendor — a category loaded with revenue-generation accusations and due-process baggage.
Claim instead: roadway safety program intelligence. Software that helps an organization understand a behaviour, validate it, and build a defensible program around it — of which enforcement is one possible response. That framing is already implicit across the site, and it is the single most valuable positioning move available.
The program model
Cinq gestes, dans l'ordre.
The brand’s core structural device, and its clearest differentiator: two full stages sit ahead of any technology decision. This section is a navy band — every token below re-resolved automatically.
- 01
Understand
Define the safety, compliance or mobility challenge in a specific place.
- 02
Validate
Capture reliable information about what is actually happening there.
- 03
Design
Turn events into patterns, and patterns into a defined program.
- 04
Communicate
Tell people what is happening and why the program is running.
- 05
Act
Support the appropriate response, with authorized review where it applies.
Authorized human review
The automation boundary — absolute, not subject to exception
The tightest formulation in the whole brand, from the style guide:
"Defined program decisions remain subject to authorized review inside the organization responsible for the outcome. The system prepares the record; it does not conclude it."
Every description of an automated step is followed, in the same section, by the statement that a person decides. Not a disclaimer bolted on — the product position.
Layer 02 · Logo
The mark, and the rules that carry it.
Documented from Our Brand Logo.pdf — the exported « Preliminary Brand Guides » deck. The Canva /edit link needs an authenticated session and could not be opened, so this comes from the PDF export of that same deck.
Status of the guide — read before relying on it
It is titled Preliminary Brand Guides, and it is exactly that: a Canva template with the SSZ specifics filled into some fields and placeholder copy still sitting in the rest.
Real and usable: the four named colours with hex values, the logo font, the three variations, the clear-space principle, the positioning formats, the six misuse rules, the symbolic rationale.
Still template boilerplate — don't quote it: the sentence "Presentations are communication tools that can be used as demonstrations…" appears ten times as body copy; "The Beuaray Corp. Logo Today" and "About Beuaray Corp." are a leftover template company name; the download link points to the agency's address.
The practical read: the logo decisions have been made and documented. The logo guide has not been written. Layer 2 §1 writes it.
The artwork, as measured
Six SVG masters — three variations × two colourways. Every figure below is measured from the files, not estimated. The symbol here is rendered from the real path data.
Two mirrored forms, each natively 345 × 345 square. Gap 10.9% of a form's width. Straight lines only — no curve anywhere in the file.
An angular hourglass with a Z woven through the waist. Natively square — this is what the favicon should use.
| File | Variation | Colour | Ink | Ratio | Status |
|---|---|---|---|---|---|
| 4.svg | Horizontal | #071C42 | 233.41 × 20.55 | 11.357:1 | Clean |
| 3.svg | Horizontal | #FFFFFF | 233.41 × 20.55 | 11.357:1 | Clean |
| 1.svg | Stacked | #071C42 | 205.95 × 88.43 | 2.329:1 | Lopsided canvas |
| 2.svg | Stacked | #FFFFFF | symbol missing | — | Defective |
| 6.svg | Symbol | #071C42 | 727.25 × 344.80 | 2.109:1 | Clean |
| 5.svg | Symbol | #FFFFFF | 727.25 × 344.80 | 2.109:1 | Clean |
✅ The logo is monochrome — and that defuses the palette worry
Every file uses exactly one colour: navy #071C42 for light backgrounds, white for dark. Tech Turquoise, City Night and Cement Median do not appear in the logo at all — they are a supporting palette.
And the one colour it does use is --navy-800, the exact brand navy. The logo and the website agree perfectly. What remains is a narrower, collateral-only decision about the three supporting colours and the typeface.
It also means the currentColor implementation on the site isn't a clever workaround — it's the natural expression of a single-colour mark.
🔴 2.svg is defective and must be regenerated
The white stacked lockup isn't clean vector. Against its navy twin: 3.4× the file size, two fewer vector paths, 4 embedded raster PNGs, 2 masks, 2 colour-matrix filters, and 47,640 characters of base64.
The proof: in 1.svg the ink starts at y = 5.24, where the symbol sits. In 2.svg it starts at y = 32.09 — the top of the wordmark. The symbol is missing from the vector layer; it's been rasterised and re-coloured with a filter stack.
It will soften when enlarged, won't print cleanly, and renders inconsistently across engines. Regenerate from 1.svg — or better, ship one currentColor file and drop colourway pairs entirely.
🔴 The favicon test — use one form, not two
The symbol is 2.109:1, so it can't fill a square favicon. I rendered it at 16, 24, 32, 48 and 64 px:
| Size | Both forms, letterboxed | One form |
|---|---|---|
| 16 px | Illegible — counters fill in, reads as two grey smudges | Tight, but the Z resolves |
| 24 px | Still muddy | Clean |
| 32 px | Marginal | Clean |
| 48 px + | Fine | Fine |
Favicon, app icon, social avatar and map pin use a single form. It's natively 345 × 345, so it fills the canvas with no letterboxing and no cropping decision. The full symbol stays for 48 px and above.
✅ Three questions the artwork settled
The wordmark is outlined — all six files are path geometry only, no <text>, no font dependency. Poppins isn't needed to render the logo.
The wordmark is spaced — "SaferSmart Zones™", with the ™ built into the artwork. The artwork and the style guide agree, and the closed-up form is just a specimen treatment. One consequence: never add a second ™ beside the logo.
Two of the three stated design intentions check out exactly. "Strong Sharp Infrastructure Lines" — confirmed, straight lines exclusively. "Balance, Synergy & Symmetry" — confirmed, exact mirror. But "Diamond Sign" doesn't match as drawn: the silhouette is an hourglass. The triangular counters are probably what was meant.
What the mark means
Three symbolic notes are recorded. Terse, but they are the design rationale and should survive into any future guide.
Diamond sign
"Diamond Sign is a Secure Passing"
Line work
"Strong Sharp Infrastructure Lines"
Composition
"Balance, Synergy & Symmetry"
Reading That describes a mark built from the North American road-sign diamond — the shape a driver already reads as "pay attention to this zone" — in sharp infrastructure linework, composed symmetrically. A good fit, since the brand's whole proposition is the defined zone. Worth confirming against the artwork and then saying out loud; right now it exists as five words in a Canva file.
Three variations
Horizontal
The default. Mark and wordmark side by side. What the website uses.
Vertical
Stacked. Narrow columns, square formats, apparel, signage, vehicle panels.
Icon
Mark alone. Favicon, app icon, social avatar, map pin, and below the wordmark's minimum size.
The logo palette
Four named colours, given as "our colour palette for logo usage". The naming is roadway-literate and memorable — keep it.
🔴 The divergence — the most consequential finding in this document
Only one of the four logo colours made it into the built design system. The other three appear zero times across theme.css and styles.css — and so does the logo font.
| Element | Logo guide | Built system | Status |
|---|---|---|---|
| Primary navy | Academy Navy #071C42 | --navy-800 #071C42 | Identical |
| Accent | Tech Turquoise #3DCAB1 | --teal-400 #2DD4BF | Diverged |
| Darkest | City Night #121212 | --navy-950 #030A18 | Diverged |
| Neutral grey | Cement Median #BCBCBB | none | Absent |
| Typeface | Poppins Bold | Manrope 800 | Diverged |
In practice: a business card, a booth banner and a PowerPoint built from the Canva file will not match the website. The navy lines up; the accent teal, the black, the grey and the typeface do not. Side by side, the two teals read as a mistake rather than a variation.
Recommendation — bring the logo to the web system. The built system is contrast-verified across four bands, has a full seven-step teal ramp including a light-safe --teal-700, and is what every visitor already sees. The logo guide is explicitly preliminary. The alternative — keeping two palettes scoped by medium — is how brands drift, and the logo would be the one thing on the page in the wrong teal.
On the typeface, it's easier than it looks: the wordmark is artwork, not type. Once it's outlined, Poppins stops being a live dependency. Record it for redraws, never set live text in it, never re-typeset the wordmark.
Sixteen misuse rules
✕ From the guide — authoritative
- DO NOT change the colour — use colours in the palette
- DO NOT crop the logo
- DO NOT add shadows or effects
- DO NOT rotate the logo
- DO NOT put over another illustration
- DO NOT use tint or opacity
✕ From the implementation rules
- Don't re-compose the lockup — it is one asset in a fixed relationship
- Don't hard-code a fill colour — it must inherit
currentColor - Don't replace
.u-spritewithdisplay:none - Don't stretch, condense or distort
- Don't re-typeset the wordmark, including in Poppins
- Don't enclose in a non-approved box or badge
- Don't add a tagline unless it's a supplied lockup file
- Don't screenshot the logo from the site or a PDF
- Don't put the SSZ logo on public campaign material where the client organization should lead
- Don't use a literal ™ in a filename
There is no logo asset library
The artwork exists in exactly two places: inside a Canva design, and inside the web theme's SVG sprite. Nothing is exportable, versioned, or handable to a printer, a partner or a client organization.
Two files in Drive look like logos and are not. safer_smart_zones_logo.svg (two copies) is a development placeholder — a green #22C55E circle with a white cross and "SaferSmart / ZONES" set in Arial. A favicon.svg in an app repo is purple and belongs to a different project. Delete or clearly mark both before someone ships one.
What's still open
Three of my four earlier questions are now answered. One could not be — clear space is a rule about the space around the mark, so it can't be measured from the artwork.
The clear-space measurement
Still open. Layer 2 §1.7 proposes the cap height of the "S" as 1×, because a letterform-based unit scales automatically where a millimetre value doesn't. Needs sign-off, or the real figure.
Confirm the S · S · Z reading
Two forms, each carrying a Z. If that's the intent, it's worth one sentence in the guide — a monogram that resolves into the company's initials shouldn't be undocumented.
Which single form is the icon?
Left or right. They're mirrors, so it's a design call rather than a technical one. The produced asset currently uses the left.
Approve the variation naming
The guide says Vertical · Horizontal · Icon; the artwork is a stacked lockup and a two-part symbol. Suggested: Horizontal · Stacked · Symbol · Icon.
Three clean assets, produced from the masters
Rebuilt from the exact path data, re-origined to a tight bounding box, set to currentColor with fill-rule="evenodd". Rendered output is pixel-identical to the supplied files.
| File | Size | Purpose |
|---|---|---|
| SSZ_Symbol_Full_currentColor.svg | 852 B | Full two-form symbol. One file for both colourways. |
| SSZ_Icon_Square_currentColor.svg | 566 B | Single form, natively square — favicon and app icon. |
| SSZ_Icon_Maskable_currentColor.svg | 617 B | Single form + 10% safe area, Android maskable. |
Because they use currentColor, one file serves navy, white and any future context — no colourway pairs to keep in sync, and no way to repeat the 2.svg problem.
Layer 02 · Colour
Navy and teal.
Light on white, dark on the brand navy.
Transcribed from theme.css. Light mode is built on #FFFFFF; dark mode is built on the brand navy #071C42 — which is why the dark theme reads as a brand rather than an inversion.
Navy — brand and canvas
Teal — the tone
The working end of the system. Which step is correct depends entirely on the band — the single most important thing to understand about SSZ colour.
Verified The source comment on --teal-700 reads "AA-safe as text on white" — confirmed at 5.47. The comment on --amber reads "darkened: AA on its own 9% tint, not just on white" — confirmed at 5.90 on its own tint, 6.77 on white. That is genuinely careful colour work; most systems check text against the page, not against the tinted chip it actually sits in.
The band system — the core concept
Two independent axes — data-band (light or dark section) × data-theme (light or dark theme) — giving four combinations. Components read only the semantic tokens, so one component works in all four without variants. Switch the appearance control in the header to see both themes.
White section
--tone: teal-700--ink: #071C42
ink 16.75 · soft 7.45 · mute 5.49
Navy section
--tone: teal-400--ink: #FFFFFF
ink 16.75 · soft 10.12 · mute 6.64
Navy page
--tone: teal-400--ink: #EDF3FF
ink 15.05 · soft 9.09 · mute 7.06
Deep navy section
--tone: teal-400--ink: #FFFFFF
ink 18.57 · soft 10.40 · mute 6.35
All pass Every body-text token clears AA or AAA in all four bands. This is a well-built system.
Three rules that keep the band system intact
- Components read only band tokens —
--bg,--ink,--ink-soft,--ink-mute,--edge,--surface,--tone. Never a raw--teal-*or--navy-*. A raw value cannot serve four contexts and will fail in at least one. --toneis not a colour, it is a role. Light band: teal-700. Dark band: teal-400. Writingcolor: var(--teal-700)on a component breaks it on navy.- Set
data-bandon every section.
Three verified contrast failures
Found by calculating every value in the source. All three are real and actionable.
| # | Issue | Fix | Severity |
|---|---|---|---|
| 1 | --tone-bright resolves to teal-600 #0D9488 on the light band. 3.74 on white — below 4.5:1 for text under 24px. Used as text in .cta__region (12px), .readmore:hover (11px) and link hovers. Fine on navy bands, where it is teal-300 at 11.36. | Set --tone-bright: var(--teal-800) on the light band — 7.61 AAA. Two declarations to change. | High · 1.4.3 |
| 2 | Form input borders use var(--edge), which fails 3:1 in all four bands (1.23 on white). An input border is a non-text UI component under WCAG 1.4.11. The contact form is the primary conversion surface. | Add an --edge-control token meeting 3:1 and apply to form controls. --edge stays correct for decorative hairlines. | High · 1.4.11 |
| 3 | The invalid-field colour #FF8A5B is 2.32 on white, and is the only colour hard-coded outside the token system — so it cannot follow a band. | Tokenise as --error per band. Also add per-field text and an icon — WCAG 3.3.1 means an error must not rely on colour alone. | High · 1.4.11 / 3.3.1 |
Layer 02 · Typography
Manrope and IBM Plex Mono.
Real values from source, rendering in the real fonts. Headings are weight 800 with negative tracking and text-wrap: balance. The mono is load-bearing, not decorative — it carries every eyebrow, category label, numeral and record field, roughly thirty distinct uses.
clamp(36–76px)
1.0 · −.045em · 800
clamp(34–56px)
1.04 · −.042em · 800
clamp(30–50px)
1.1 · −.03em · 800
clamp(19–24px)
1.24 · −.022em · 700
clamp(16.5–19px)
1.62 · 60ch
17.5px · 1.72 · 68ch
11.5px mono · 500
+.16em · uppercase
12.5px
11.5px mono · +.12em
The section pattern
EYEBROW ← mono 11.5px / 500 / +.16em / uppercase / --tone
with a 6px --tone dot, 9px gap, 18px below
Statement headline. ← 800, negative tracking, sentence case,
Second line for meaning. FULL STOP, text-wrap: balance
Supporting copy at 60ch ← --ink-soft, line-height 1.62Plus .rule — a 56 × 1.5px --tone hairline that draws in ahead of the copy. Visible at the top of the Colour section above.
The settled spelling rules
Canadian English with two deliberate American exceptions: program (never programme, 201 instances) and license for both noun and verb — it is a license plate. Also curb, never kerb (corrected in 33 places).
Keep the -our (behaviour, colour) and -ize (organization, authorized). Keep centre, metre, defence, travelled, cheque. Dates: 7 January 2026 in prose, 2026-01-07 in data.
Say "organization", not "agency" — agency is narrower than the audience and quietly writes construction contractors out. And never global, worldwide or international: the region is Canada and the United States, and that is a commitment rather than a limitation to hide.
Layer 02 · Components
Tout ce qu’un réviseur doit voir, au même endroit.
Live components built from the real token system. Roughly sixty exist in source, fifteen of them as saved Elementor templates — don’t rebuild what is already built.
Buttons
Verified White on teal-700 = 5.47 AA · hover teal-800 = 7.61 AAA · dark theme uses #04202B on teal-500 = 6.77 AA · dark band uses #042A26 on teal-400 = 8.27 AAA. The near-black text on bright teals is the correct call — white on teal-400 would fail. Tab through to see the 2px --tone focus ring at 3px offset.
The evidence review record
The brand's most distinctive UI object. Mono tabular figures, ISO dates, and the authorized reviewer required line that is mandatory and never removed.
- Event
- EVT-4821
- Date
- 2026-05-14
- Time
- 10:42:17
- Location
- Sample Ave / 3rd St — NB approach
Sample, non-identifying data shown for illustration.
The photography-pending component
A purpose-built answer to an incomplete asset set: a pending photograph holds its frame and states its own brief on the page. The same pattern covers portraits. This is the right way to ship an incomplete brand — the remaining task is to commission the photography, not to fix the site.
The corridor. A municipal arterial road with roadside camera infrastructure mounted on a utility pole, vehicles approaching in both directions and a posted speed-limit sign. Overcast daylight, documentary framing, no readable license plates.
The four reveal types — the whole motion vocabulary
From the source: "Four types only. A: editorial text. B: photography mask. C: hairline draw. D: large statement clipping up. Everything else reuses one of them." One easing curve, cubic-bezier(.22, 1, .36, 1). Adding a fifth type is a design decision, not an implementation one.
Editorial text
Opacity 0→1 with a 22px rise.
Photography
Mask clip-path opens; image settles from scale(1.045).
Hairline
scaleX(0→1) from left, or a stroke-dashoffset draw.
Statement
Each line clips upward from translateY(105%).
Reduced motion — the pattern worth copying
Every element whose resting state is opacity: 0 or a clip-path is explicitly forced visible — not merely un-animated. A naive implementation that only cancels animations leaves reveal content permanently invisible. This one doesn't. The boot loader and page transition are removed entirely rather than sped up.
Any new animated component must add its resting state to that block.
The wave — five placements only
The brand has one graphic device and the source is emphatic about its restraint: "Photography leads. The SSZ hairline wave is the signature motif, used in five places only." Hero, panel, flow, CTA and the boot sequence. Never interactive, never above content, never recoloured — it reads --wave-color from the band and re-tints automatically.
The hairline recurs as a family, which is what makes it a system rather than a decoration: .rule, .panel__thread, .flow__thread, .wire__links, .arch__link, .ptile::after, .xfade__line, and custom list markers — "a short SSZ rule rather than a browser bullet."
✓ Photography do
- Real locations, real infrastructure, real weather
- Natural available light — overcast reads documentary
- Eye-level: the perspective of someone who works there
- Winter and adverse conditions — operating realities, and showing them is credibility
- Negative space for type overlay
✕ Photography don't
- No readable license plates — blur or replace, non-negotiable
- No identifiable individuals without written release
- No collision, injury or emergency-aftermath imagery
- No children in an enforcement context
- No surveillance aesthetics, no "AI" visual clichés
- No synthetic people in an authority role
Governance
What's open, and what just closed.
Eight items closed when the source files arrived. Thirty remain open, six of them blocking — and four of those need only a decision rather than production work.
The marker convention is a brand asset, not a defect
v1.0 of this system treated the [… TO BE VERIFIED] markers as failures. They are a deliberate, documented convention with drafted replacement text and a live approval trail. The style guide explains why:
"The marker is visible on the page on purpose. A placeholder that looks like copy gets published; one that looks like a defect gets fixed."
Same instinct as the photography-pending component, and as the rule that says write nothing rather than an unmeasured claim. The brand would rather look unfinished than unsubstantiated. For this audience that is exactly the right trade. Progress: 58 markers reduced to 22.
✅ Closed since v1.0
| Item | Resolution |
|---|---|
| Security, encryption, residency, retention | Published. Encrypted in transit and at rest; per-user named access; reviewer identity and time on every decision; residency hyperlocal to the market served. This was the most likely deal-breaker in the pipeline. |
| Camera compatibility | Published as assessment criteria — network reach, format and resolution, clock accuracy, field of view. Describes the assessment, not a list, so it does not become false when a new device appears. |
| Program integrations | Published with a conditional "where the organization can expose…" clause. Never drop that clause. |
| Colour and font values | Extracted. Layer 02 rewritten from source. |
| programme vs. program | Settled: program. |
| kerb vs. curb | Settled: curb. |
| Partner name | Settled: Site2020, one word, an independent partner company. |
| Alt text | Partly a false finding. Empty alt on a decorative image inside an aria-hidden link is correct practice. |
| French | Already built — three languages, switcher hidden, one line to re-enable. The task is validation, not creation. |
🔴 Still blocking
| Item | What's needed | |
|---|---|---|
| Logo master files & palette divergence | No exportable artwork exists, and only 1 of 4 logo colours matches the built system. Blocks every piece of collateral. | Blocking |
| Which build is canonical | Source files and the live site disagree on team, markers, naming and languages. Resolve first — it changes which findings are live. | Decision |
| Contact values | Six positions. One phone number or none — "a number that rings nowhere is worse than a form." City and province, not a street. Role addresses, not personal ones — the live build publishes three personal addresses. | Decision |
| Team data | Six slots: name, title, two-to-three sentence bio, square-cropped portrait, work email, LinkedIn. "No adjectives about passion, no 'thought leader'." | Decision |
| Privacy, Terms, Accessibility | On the older build all three footer links point to the homepage. Confirm the newer build publishes them. | Blocking |
| Three contrast failures | --tone-bright, form input borders, invalid-field colour. Small, well-defined code changes. | Code |
| Brand name form | Both forms in use on the older build, plus decks and biographies already in circulation. | Blocking |
Also worth fixing quickly
Every external research citation on the two long-form use-case pages carries ?utm_source=chatgpt.com in its href, the FHWA is labelled "Administration Fédérale des Autoroutes" in English copy, and the logo filename contains a literal ™. Individually small; collectively a visible provenance trail on exactly the pages carrying the brand's only statistics.
Separately: the site cites IIHS at 21% in body copy while its own reference list includes a paper titled "…Reduces Fatal Red Light Running Crashes by 24 Percent." Read both papers and reconcile before either number appears in a deck or a council presentation.
Layer 06 · AI Brand Kit
AI may draft.
AI may not claim.
The system as machine-readable instructions, so you can stop saying « write this in our brand voice » and start giving a model enough structure to reliably operate inside the brand — including knowing what it is not allowed to say.
Master system prompt
What the company is, voice, terminology, the corrected spelling rules, the automation boundary, approved and forbidden claims, audiences and structure patterns.
Ten task prompts
Blog, LinkedIn, one-pager, council material, campaign copy, outreach, RFP response, press release, voice rewrite, compliance review.
Image prompt library
Visual-DNA prefix, seven subject prompts, and diagram prompts carrying the real brand hex values — with the rule to pick the teal by background.
ssz-brand-kit.json
25 structured domains. Every design token with its calculated contrast ratio, the four-band map, all personas, the messaging matrix, and the open-items register.
Validation checklist
Ten blocking checks, nine high, six medium, and a final human gate. One blocking failure stops publication.
Marker convention
The seven approved markers, and the rule that a marker always beats an estimate — and that softening one into a hedge is worse than either.
The hard rule
No AI system may generate a statistic, performance figure, case study, testimonial, client quote, named certification, named camera model, or encryption version for SaferSmart Zones™. Every AI-assisted asset requires human review and named sign-off before publication.