Governance

Keep the brand system connected to the real codebase.

Governance is what keeps `brand.gensudo.com`, the marketing site, and the product app from drifting apart. This section documents where decisions belong and how shared changes should be implemented.

Source of truth rules

Put tokens, theme values, brand assets, and shared CSS foundations in `packages/brand`.

Put reusable React primitives in `packages/ui`.

Keep route files focused on composition, content, and local layout only.

Update docs examples in the same implementation pass when shared tokens or components change.

Anti-drift guardrails

Live examples must import real shared components.

Do not patch the docs site with alternate component styling when the goal is a shared system change.

Use layer variables, sanctioned variants, and usage guidance before forking a component.

Call out bypasses and route-local drift when they are discovered during implementation.

Decision order

1. Reuse an existing token.
2. Reuse an existing shared class or component.
3. Extend a shared primitive if the pattern is already repeated.
4. Add a new semantic token or primitive if the pattern is becoming shared.
5. Add page-local styling only when the pattern is truly one-off.

Changelog

v0.1.0 · 2026-04-16

Initial launch of the brand system site scaffold and governance model.

  • Added `apps/brand` as a dedicated workspace app for `brand.gensudo.com`.
  • Established first-class routes for foundations, marketing, app, components, patterns, assets, and governance.
  • Rendered shared previews from `@gensudo/ui` and asset references from `@gensudo/brand`.
  • Documented anti-drift rules so docs stay coupled to the real shared source of truth.

Release checklist

  • Shared changes land in `packages/brand` or `packages/ui` before docs-only polish is considered.
  • Docs examples are updated in the same change when a shared token or primitive changes.
  • `npm run build:brand` and `npm run typecheck` pass before release.
  • Critical routes are reviewed for hierarchy and cross-surface consistency before publishing.

Legacy alignment

Legacy inventory

See how legacy guide sections map to current coverage, missing docs, historical references, and future candidates.

Promotion path

Follow the decision path for turning a legacy-only pattern into shared system truth safely.