GAB OS
completedmedium priorityEnterprise Identity / Brand Architecture / Design System

GAB Identity, Naming & Design System Re-architecture

FRAMING SET BY CEO 2026-09-04 — READ THIS BEFORE ANY OTHER FIELD. WHAT THIS INITIATIVE IS. GAB has run a deliberate lineage of enterprise-improvement initiatives aimed at the OS itself: Project Baobab (discover and reveal the enterprise architecture exactly as it exists), Project Canopy (turn that discovered knowledge into a maintained Enterprise Map and Architecture Atlas), and the follow-on agent context and operating-telemetry work. That lineage overhauls and improves the OS in terms of ARCHITECTURE AND CODE. The Design Initiative is the counterpart arc aimed at REDESIGN. It is the same kind of undertaking, applied to the design estate rather than the architectural one. WHAT THIS INITIATIVE IS NOT. It is not a defect-repair project and must not be recorded as one. Type, logo and naming all have documented canon; divergence from canon is not the justification. The OS is continuous and things are built on things — accumulation is the normal condition of a working system, not a failure. The CEO's stated reason is forward-looking: the old design does not serve what he wants the company to BE and to GO. Agents drafting against this initiative must stop producing defect narratives; three were produced and rejected on 2026-09-04. METHOD DISCIPLINE — CEO INSTRUCTION 2026-09-04. Do not ask the CEO to restate things already established in the OS. Where an answer exists in a prior initiative, project, pack or contract, read that artifact and cite it. Asking the CEO to re-express a settled position produces a near-identical restatement, and those restatements ARE the duplicates the enterprise work keeps finding. This is a standing rule for this initiative, not a one-off correction. The CEO pointed to Baobab and Canopy for exactly this reason. AUTHORITATIVE SOURCES FOR COMPANY DEFINITION AND DIVISIONS. Project Canopy (pm_project 0f8556af-dc41-43dc-98d2-0a0afe7c445f, closed 2026-07-12, nine approved packs) and Project Baobab (8780744b-2ef4-4ff7-ab00-1be3043d4089). Specifically WP2 Enterprise Entity and Capability Map (pack 27681357-aa05-4008-83d1-78e8db700c1f), WP3 Source-of-Truth and Governance Atlas (e68817e9-8751-4c37-ae12-f6ad4b24de81), WP4 Product-Service-Module Relationship Map (bd5bdf40-f072-41c1-9c63-31cf3de3c6b6), WP5 Agent Navigation and Operating Map (bf205228-1dac-4432-929f-8cdfe7f62f88), and the Pre-G5 Independent Strategic Review and Future Direction (1967c19b-dcd7-41f9-b824-aea72cf91568). Company definition and division taxonomy are settled there. Code-level lists (lib/company.ts, scripts/gab-wakeup.mjs strategic_canon, lib/voice/persona.ts, finance division arrays) are downstream copies of varying age and are NOT the definitional source; an earlier draft of this analysis wrongly treated them as such and the resulting claim that GAB has no single authoritative company definition is WITHDRAWN as incorrect. TARGET SHAPE OF THE OUTCOME. Canopy is the model for what good looks like: not a document but a maintained, canonical, navigable map that both humans and agents operate from. The design outcome should take the same form — a maintained design source that every surface derives from — rather than a static guide that surfaces copy from by hand. ORIGINAL INTAKE SIGNAL (CEO direct, 2026-09-01) retained for record. Daniel Nsowah raised that the GAB palette has become common and overused, that website, media outputs and the OS interface all derive from the same green/gold system, and that design capability has advanced enough to warrant an uplift. Stated intent is company-wide rebrand and reorganisation at rebrand level, explicitly including decomposition of how GAB OS itself is organised, so the company meets emerging standards. Recommendation: Review charter v1.0 for G2. Preserve the established full brief; approve the delivery undertaking separately from visual direction selection. Reconcile capacity before promotion; complete G3 baseline before delivery execution. Expected benefits: CEO-confirmed fresh and distinctive design across GAB; coherent variation; full interface, motion, static and document coverage; clear naming and brand relationships; one maintained versioned design source with synchronized generation and QA. No unsupported conversion or revenue promise. Promoted from Portfolio & Business Analysis initiative d6ed5f3e-bbc3-4b83-91aa-8fd201f4d85d.

Owner: Daniel Nsowah
Overall Progress96%

Initiative to Operations Spine

Trace the work from Portfolio justification through Project delivery and operational handover.

portfolio baGate closedfull governance

G0-G2

Portfolio & BA

converted

G3

Plan / baseline

Passed or pending

G4

Execute, monitor & control

Pending or passed

G5

Acceptance / release

Pending or passed

G6

Closure / benefits

closed

Source initiative

GAB Identity, Naming & Design System Re-architecture

d6ed5f3e-bbc3-4b83-91aa-8fd201f4d85d • project module • G3

Review charter v1.0 for G2. Preserve the established full brief; approve the delivery undertaking separately from visual direction selection. Reconcile capacity before promotion; complete G3 baseline before delivery execution.

Record Project Gate

Use for G3 baseline approval, G4 execution/control completion, G5 acceptance, and G6 closure or benefits review decisions.

Gate History

Portfolio G0-G2 and Project G3-G6 decisions in one view.

G0 — go

Portfolio & BA • Daniel Nsowah • 4 Sept 2026

1. G1 must produce a current-state identity baseline across every live surface before any direction exploration. The founder signal ("colours are common and overused", "design and look of website and media outputs all based on the same palette") is confirmed as genuine CEO intent but is not yet evidenced, and Canopy s Pre-G5 review set the precedent that an unmeasured pain point must be baselined before ROI or solution choice. 2. Root-cause analysis at G1 must explicitly separate four candidate causes before any is accepted: identity system, positioning, surface coverage, and composition rigidity. If the cause is not the identity system, the finding is routed to the correct owner and this initiative is revised or stopped at G1. 3. No token, palette, naming or contract change may ship from analysis work. G1 is analysis only. 4. Scope confirmed by CEO 2026-09-01: the registered legal name GAB Climate Smart Investments Ltd is OUT of scope, because changing it requires action at the Office of the Registrar of Companies. The GAB OS internal interface is IN scope and is a stated principal driver. 5. Non-duplication is binding. Baobab, Canopy and ACOI outputs are consumed as evidence, never re-derived.

G1 — go

Portfolio & BA • Daniel Nsowah • 6 Sept 2026

Scope is design and how the company looks, outside and inside — every external surface and the GAB OS interface. Nothing removed; all eight G0 success metrics stand, including brand governed as an OS capability with its own module contract. Company definition and division taxonomy are NOT reopened: they are settled in Baobab and Canopy and must be read from those artefacts rather than restated. Next step is charter basis toward G2. Effort and duration to be estimated at charter preparation, now that E1 has established the true surface count. STANDING CONSTRAINTS UNCHANGED: no token change ships until CLICOM's active 20-theme series can be version-pinned to the outgoing system and the visionQA judgment path migrates in the same change as generation; Blue Carbon client handover and onboarding materials settled against the delivered report; promotion to a Project held until capacity is reconciled against 5 active projects and 28 overdue tasks; registered legal name fixed at the Registrar, trading identity and expression in scope.

G2 — go

Portfolio & BA • Daniel Nsowah • 6 Sept 2026

Charter v1.0 approved. Preserve the full documented design scope. Visual direction selection remains a separate WP2 decision; G3 delivery baseline is required before execution. The charter's explicit capacity-allocation condition before promotion remains unresolved: approval does not specify which delivery/review capacity is allocated or pause existing work. CLICOM version pinning, generation/QA alignment and Blue Carbon handover constraints remain.

G3 — go

Project • Daniel Nsowah • 13 Sept 2026

G5 — go

Project • Daniel Nsowah • 15 Sept 2026

G6 — go

Project • Daniel Nsowah • 15 Sept 2026

BA Documents Carried Forward

The pre-project logic that should govern delivery decisions.

Business case

Portfolio & BA artifact

Business case: CEO-confirmed 2026-09-06: fresh company-wide design and visuals because current colours and much of the aesthetic have become too commonplace. Use the documented brief; do not restart discovery or require proof of business harm. Spatial specificity and restrained/accent palette are prior agent suggestions, not approved creative requirements. G1 is approved; prepare G2 charter. Full original scope and eight success metrics remain. Registered legal name fixed; trading identity and expression in scope. CLICOM outgoing-version pinning and synchronized generation/visual-QA migration are required before token changes ship. Blue Carbon handover must match its delivered report and be

Benefits plan

Portfolio & BA artifact

Primary benefit: CEO-confirmed fresh, distinctive and authentic design across GAB. Supporting benefits: coherent variety; motion/static/document/interface coverage; maintained versioned source; reliable generation and judgment; sustainable operation. Review against the existing baseline 30 days after accepted rollout. No conversion/revenue uplift claim without an adequate measurement basis.

Charter

Portfolio & BA artifact

# GAB Identity, Naming & Design System Re-architecture ## Charter basis v1.0 — draft for Daniel's G2 review Prepared 6 September 2026. Portfolio initiative d6ed5f3e-bbc3-4b83-91aa-8fd201f4d85d. Full governance. G1 is approved; this document does not record G2 approval, select a visual direction, authorize spending or start implementation. ## 1. Purpose and authority Give GAB a fresh company-wide design and visual identity because its current colours and much of its aesthetic have become too commonplace to express the distinctiveness Daniel wants. The outcome should express the company as established and where Daniel wants it to go, across external surfaces and his everyday experience of GAB

Transition plan

Portfolio & BA artifact

Use charter v1.0 section 7. Maintain a per-surface register of owner, old/new identity versions, dependencies, tests, approval, release order and rollback. Pin CLICOM's ongoing series before shipping new tokens; synchronize generation and visual QA. Confirm Blue Carbon handover with its owner and retain the delivered report's identity. Pilot in internal/staging contexts, then release approved surface batches. At G6 hand over source, assets, adapters, contract, operational ownership and benefits review.

Transition to Operations

Define where the project output lives after delivery.

Identity upkeep transfers to the Brand module

brand • planned

Operational handover from Portfolio transition plan

Enterprise Identity / Brand Architecture / Design System • planned • Daniel Nsowah

Use charter v1.0 section 7. Maintain a per-surface register of owner, old/new identity versions, dependencies, tests, approval, release order and rollback. Pin CLICOM's ongoing series before shipping new tokens; synchronize generation and visual QA. Confirm Blue Carbon handover with its owner and retain the delivered report's identity. Pilot in internal/staging contexts, then release approved surface batches. At G6 hand over source, assets, adapters, contract, operational ownership and benefits review.

Requirements Traceability

BR-001: The registered legal name "GAB Climate Smart Investments Ltd" must remain unchanged. All identity work operates on trading identity, mark, naming of sub-brands and products, and expression, never on the registered entity.

linked • planning • scope • task linked • quality linked

No deliverable proposes, implies or depends on a change to the registered legal name. The plural "Investments" rule in lib/company.ts remains enforced everywhere.

BR-002: The GAB OS internal interface must be treated as a first-class in-scope surface, on equal footing with public surfaces.

linked • planning • scope • task linked • quality linked

The current-state baseline covers the OS interface at the same depth as public surfaces, and any proposed system specifies its treatment explicitly rather than leaving it as internal tooling outside the identity.

BR-003: Prior enterprise-architecture evidence must be consumed, never re-derived. Baobab, Canopy and ACOI outputs are inputs to this initiative.

linked • planning • scope • task linked • quality linked

Every structural claim about modules, products, capabilities or source-of-truth cites the relevant Baobab or Canopy pack rather than re-deriving it. No deliverable re-baselines enterprise architecture, rebuilds the Atlas, or revisits agent context and tool scoping.

BR-004: Use the existing G1 baseline and recorded analysis to inform delivery of the CEO-confirmed fresh company-wide design brief. Preserve evidence limits; do not reopen the renewal decision or restart discovery. Visual direction is selected separately during authorized delivery.

linked • planning • scope • task linked • quality linked

The charter and delivery brief reference E1–E6 and CEO amendments, preserve known evidence/coverage limits, and contain no new justification interview or predetermined visual theme. G1 approval remains in gate history; G2, G3 and visual direction decisions remain distinct.

BR-005: Identity values must resolve to a single versioned source that every consuming surface reads, replacing values currently duplicated across repositories, style bibles and prompt strings.

linked • planning • scope • task linked • quality linked

Changing an identity value in one place propagates to every surface. brand_audit reports no drift between surfaces. Individual surfaces can be pinned to a specific identity version, which is what allows an in-flight series to finish on the outgoing system.

BR-006: Generation and judgment must migrate in the same change. Any identity change updates the visual QA criteria at the same time as the generation prompts.

linked • planning • scope • task linked • quality linked

No change ships in which generation and judgment reference different identity versions. Preferably visionQA derives its criteria from the versioned source rather than restating them, so the failure mode cannot recur.

BR-007: In-flight production series must be able to finish coherently on the outgoing identity. CLICOM must be pinnable to the current system for the remainder of its 20-theme run.

linked • planning • scope • task linked • quality linked

A transition plan states, per surface, which identity version it runs and when it migrates. CLICOM completes its current series on one consistent system. Depictive colour (vegetation rendered green because vegetation is green) is separated from brand colour, so a palette change does not force unnecessary reworking of claymation and 2D frames.

BR-008: Delivered client work must stay internally consistent. Blue Carbon handover and onboarding materials are produced in the identity of the report already delivered.

linked • planning • scope • task linked • quality linked

Blue Carbon handover and onboarding materials match the delivered report. The transition plan records how any other in-flight client engagement is treated.

BR-009: Brand should become a governed OS capability with its own module contract, owning identity tokens, assets, naming rules, versioning and audit.

linked • planning • scope • task linked • quality linked

A brand module contract exists meeting CONTRACT_STANDARD.md, with named Lane A tools, a stated source of truth, and a Lane B repair boundary. brand_audit checks live surfaces against the governed source. The module appears in the registry and MCP_TOOL_MAP, with any declared tool verified as callable in route.ts, not merely listed.