Document Brand/UI consolidation and the canonicality containment result

[BunsDev]

Summary

Adds the organization-level audit and execution plan for consolidating OpenCoven's Brand, UI, brand-kit, design-system, and related consumer surfaces, plus a dated resolution addendum for the urgent Brand canonicality hazard.

Recommended end state

• OpenCoven/brand is the sole canonical identity, visual-language, voice, asset, semantic-profile, and generated brand-kit authority.
• OpenCoven/ui is the sole reusable interaction/component implementation layer.
• Product repositories retain production composition and behavior.
• OpenCoven/coven-design-system is feature-frozen, selectively extracted, archived, and retired.
• Private OpenCoven/coven-design is renamed to reflect its actual evaluation-tooling role.
• coven-landing becomes the reference immutable consumer-lock pattern.

Containment update

The audit correctly warned not to merge the original Brand #4 unchanged. That branch was subsequently rewritten on top of the ratified profile and merged as Brand commit 798e2f5f2f1a69f5d156ccc0a9aafc4f7da55fc8.

The merged Brand patch preserves one canonical web/profile.* authority and adds fail-closed validation against parallel stable/canonical manifests and reserved web/tokens.* aliases. The new resolution addendum distinguishes that completed containment from the still-open organization-setting work.

Remaining blocker

brand/main remains unprotected. The addendum records the minimum required review/check/force-push ruleset. The connected GitHub write surface does not expose branch-protection or organization-ruleset mutation, so this remains an administrator setting rather than a repository patch.

Contents

• current-state audit by repository;
• target ownership and profile architecture;
• consumer-lock schema;
• Brand repository and generated brand-kit plan;
• UI integration and release plan;
• design-system extraction matrix and retirement gate;
• PR triage;
• branch/ruleset and agent-readiness governance;
• 0–48 hour, 7-day, 14-day, 30-day, and 45-day execution sequence;
• proposed issue decomposition, success metrics, risks, and rollback strategy;
• September 1 containment resolution addendum.

Validation

Documentation-only change. The original audit is an August 31 evidence snapshot; the addendum is grounded in the exact merged Brand revision and live protection state on September 1.

[Copilot]

Pull request overview

Adds an organization-level audit report and execution plan describing how to consolidate OpenCoven’s Brand, UI, brand-kit, and design-system surfaces into two canonical upstream repositories (Brand + UI) with explicit product-consumer boundaries.

Changes:

• Introduces a comprehensive current-state audit across Brand, UI, coven-design-system, and key consumers.
• Defines a target ownership architecture, consumer-lock schema, and profile layering model.
• Provides a phased execution plan with triage, governance, extraction/retirement, and success metrics.

Suppressed comments (3)

docs/brand-ui-consolidation-audit-2026-08-31.md:546

• These bullets refer to “UI #6/#2/#3” without the repository qualifier; in a multi-repo audit document this can be misread. Linking to the exact PRs (OpenCoven/ui#…) also preserves the evidence trail over time.

- **Close UI #6** unless it has a documented purpose; a `noop` draft should not be part of the release graph.
- **Rebase or recreate UI #2 directly on current `main`.** Preserve the visual-receipt work but eliminate its stale base and 76-commit ambiguity.
- **Restack UI #3 on the cleaned #2 or split it into reviewable PRs:** contracts/adapters, components, specimen route, registry output.

docs/brand-ui-consolidation-audit-2026-08-31.md:755

• In the execution checklist, “Brand #4” / “UI #6” is ambiguous without a repo qualifier and can be confused with the current PR number. Use fully-qualified, linked references so readers can jump directly to the referenced PRs.

- [ ] Mark Brand #4 as superseded/rework-required; prevent duplicate profile merge.
- [ ] Close UI #6.

docs/brand-ui-consolidation-audit-2026-08-31.md:785

• This checklist item references “UI #2/#3” without qualifying which repository those PR numbers belong to. In an org-wide plan, prefer fully-qualified, linked PR references for clarity and to keep the audit verifiable.

- [ ] Restack UI #2/#3 into a clean sequence.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.