12, Governance
Canonical home
Section titled “Canonical home”This repository, kept in local Git with no remote, is canonical. brand.noiz.co.za publishes its Astro documentation; the artifact is an alternate edition. Product sites consume versioned assets and tokens rather than establishing another brand source.
Sibling: the Service Portfolio
Section titled “Sibling: the Service Portfolio”The brand system and the Service Portfolio are siblings, not parent and child. Each is authoritative in its own domain and each constrains the other:
| Owns | Does not own | |
|---|---|---|
| noiz-brand (this repo) | Every brand value, colour, type, spacing, motion, marks, voice, and the pillar taxonomy’s identity: what a pillar is called. Pillars carry no colour since 2026-09-22. | What Noiz sells, at what price, in which tier. |
| noiz-portfolio (sibling) | Every service: taxonomy beneath the pillar, description, tiers, specs, pricing, positioning, status. | Any colour, typeface, mark or wording rule. |
The shared interface is the pillar taxonomy. It is the one thing both must agree on, and it is the reason they are siblings rather than one repo: a pricing change should not touch the brand system, and a palette change should not touch a price book, but renaming or retiring a pillar changes both at once.
The contract:
- The pillar set lives here, as names in
docs/00-strategy.md. It is currently three: Infrastructure, Security, Services. There are no pillar tokens:color.semantic.pillar.*was removed on 2026-09-22 when amber became the only identity colour. - Every service in the portfolio declares exactly one pillar, using those names.
- Adding, renaming or retiring a pillar is a coordinated release: a minor here (updated strategy chapter, updated name grammar) and a matching release there. Neither ships alone.
- The portfolio may not colour a pillar. A pillar is a name and the monochrome mark; amber is the only identity colour and belongs to no branch.
Support remains part of the four-word brand line hosting | cybersecurity | software | support. The existing portfolio mapping lists three sold service categories; it does not remove Support from brand communication or give it a separate colour.
This repository defines the interface with the portfolio. The portfolio’s current delivery state, catalogue and pricing belong to that project’s own records.
Framework boundaries
Section titled “Framework boundaries”| Site | Owning implementation |
|---|---|
noiz.ie |
WordPress / Avada |
noiz.co.za |
WHMCS / Croster |
dev.noiz.ie |
Hugo |
docs.noiz.ie |
Astro / Starlight knowledgebase |
brand.noiz.co.za |
This repository’s Astro / Starlight brand documentation |
Brand work may produce adoption notes for the other projects. Their owners adapt and deploy the system within their own framework. Never publish this site’s build, or the Hugo build, over another site’s content.
Change process
Section titled “Change process”Branch (draft/<topic>) → PR to yourself → the PR names the SemVer category and the changelog line → merge → tag when releasing.
Cadence
Section titled “Cadence”- Weekly: trivial fixes batched into the next patch.
- Quarterly: end-to-end review; cut a minor if anything was added.
- Annually: signed major review; reconcile against live sites; archive a stamped PDF.
- Ad-hoc: a major for any logo or palette change, never silently.
Ratification
Section titled “Ratification”0.x remains the pre-ratification series. Before 1.0.0, every core chapter needs usable guidance, examples need verification and unresolved proposals must be decided or explicitly deferred. Deleting a draft marker is not ratification. The owner approves the identity and release; release metadata must describe the actual tag. Read package metadata for the current version rather than copying it into a page.
A changed component includes a specimen, its states, keyboard and accessibility guidance, and the source CSS. Check narrow layouts, focus, error paths and preference fallbacks. Use the token build, validation, artifact lint and documentation build as gates, alongside visual review. These checks do not certify WCAG conformance.
The playbook
Section titled “The playbook”The full research and rationale behind this repository’s structure, why tokens, why Git, why SemVer, how other design systems are built, and the staged adoption plan, is preserved in brand-system-playbook.md. That document is the reasoning; this repository is its implementation.