34. Brand System and Required Brand Kit

The Glitchpad brand reinforces a compact, technical, calm, and slightly unconventional product without taking space from the document. Brand expression belongs in the application icon, typography, color, restrained motion, empty state, packaging, and public materials.

The required source kit contains primary symbol, wordmark, horizontal and stacked lockups, light/dark/monochrome variants, clear-space and minimum-size rules, accessible color tokens, typography and fallback stack, icon style, motion rules, naming and voice guidance, misuse examples, and license/provenance records.

Required exports include SVG master assets; Windows ICO with required embedded sizes; macOS ICNS; Linux PNG/SVG sizes; Android adaptive foreground, background, and monochrome layers; launcher and notification icons; repository social preview; release artwork; favicon/web metadata; store listing icon, feature graphic, and screenshots; and print-safe monochrome assets.

Source assets live under brand/ and generated application/store assets live under platform-owned directories. A deterministic export command regenerates outputs and CI checks drift. Color tokens pass WCAG contrast in both themes. Fonts require redistribution and embedding approval recorded with the brand sources.

Brand changes use Spec Kit when they alter product naming, UI tokens, accessibility, packaging, or public assets. A release cannot publish placeholder icons or assets that disagree with the approved kit.

The unreleased S007 repository delta imports approved brand canon 1.0.0 under brand/, uses selected checksum-verified copies in production integrations, and introduces a statically exported Next.js and Fumadocs public site under site/. The repository docs/ tree remains the authored documentation authority, with a generated public adaptation served under /docs. Pull requests and default-branch updates validate the export without publishing it; production deployment, Pages configuration, and glitchpad.com DNS remain explicit owner-controlled operations.

The S025 delivery superseded the original imported brand with Glitchpad brand 1.1.0 under ShruggieTech canon 1.2.1 from upstream commit 1681fcd444ff851d5bffc2cf67e23bbcedd753cd. The permanent square identity, pure-sulfur contextual treatment, accessible light and dark tokens, local typography, and verified web, Windows, macOS, Linux, and Android icon suites replace all public copies and distributable foundation icons. brand/manifest.json remains the immutable delivery authority, brand/INTEGRATION.md records project provenance, and automated byte comparisons prevent locally altered derivatives from entering release packages.

The current v0.1.4 delivery adopts the formal Glitchpad brand 1.1.1 kit from BrandBuilder 2.0.3 under ShruggieTech Brand Canon 1.3.0. The pinned brand/enforcement/consumer-contract.json and brand/enforcement/IMPLEMENTATION.md govern consumer copies and conformance. The released kit refreshes Android launcher artwork and supplies separate ordinary and maskable web icons; the approved square identity and previously released Windows and macOS icon binaries remain. The generated React AppFrame is the single web-shell owner. brand/INTEGRATION.json records source and integrated digests, and the bundled BrandBuilder verifiers plus copy checks reject drift.

The unreleased S009 operational delta transferred glitchpad.com from the legacy personal GitHub Pages attachment to the shruggietech/glitchpad workflow deployment. Cloudflare remains authoritative DNS with DNS-only website records, GitHub organization verification protects the apex and immediate subdomains through a persistent challenge, glitchpad.com is canonical, www redirects to the apex, and HTTPS is enforced with certificate coverage for both hosts. The migration committed a sanitized baseline, validated the reviewed main deployment on a temporary preview, applied expected-state guards to every provider mutation, preserved unrelated DNS and account configuration, and proved production over IPv4 and IPv6. Legacy Pages was then disabled with its repository recovery source retained, but this retirement violated its complete-asset-inventory prerequisite: two manifest-declared Android icons were discovered missing after retirement, subsequently restored and verified, so FR-014 and SC-009 remain recorded as not passed. The durable runbook and final evidence live under docs/operations/. Recovery is phase-specific because organization verification must be removed before an exact post-transfer return to a personal-account Pages attachment.