Project Baobab — GAB Enterprise Architecture & Institutional Map
Founder-directed initiative to discover, classify, document, and govern the enterprise architecture that already exists across GAB Climate Smart Investments Ltd, GAB OS, module contracts, products, service lines, source-of-truth systems, evidence workflows, HITL governance, and future agent/plugin enablement. Current instruction: reveal the architecture exactly as it exists before proposing redesigns or building a plugin. Recommendation: Proceed to Daniel G2 review. The proposed G2 decision is to authorize structured Enterprise Architecture analysis only, with explicit constraints against implementation, plugin build, code changes, restructuring, public positioning, or contract rewrites unless later approved. Expected benefits: If G1 is accepted, GAB gains an evidence-backed basis for enterprise architecture analysis: clearer understanding of why Project Baobab is necessary, what current maturity exists, what organic growth has created, and what business risks arise if architecture remains implicit. Promoted from Portfolio & Business Analysis initiative 9959ecdb-0456-4e87-901e-3e8ff3a1d77d.
Initiative to Operations Spine
Trace the work from Portfolio justification through Project delivery and operational handover.
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
Project Baobab — GAB Enterprise Architecture & Institutional Map
9959ecdb-0456-4e87-901e-3e8ff3a1d77d • project module • G3
Proceed to Daniel G2 review. The proposed G2 decision is to authorize structured Enterprise Architecture analysis only, with explicit constraints against implementation, plugin build, code changes, restructuring, public positioning, or contract rewrites unless later approved.
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 • 7 Jul 2026
Proceed to structured needs assessment. Maintain discovery-only discipline: no redesign, no plugin build, no project promotion, no public narrative, and no architectural recommendations until evidence is sufficient and the relevant gate approves progression.
G1 — go
Portfolio & BA • Daniel Nsowah • 7 Jul 2026
Proceed to structured Enterprise Architecture analysis. This approval does not authorize plugin build, code changes, module restructuring, public positioning, contract rewrites, or Project promotion. Continue to separate observations, implications, and recommendations.
G2 — go
Portfolio & BA • Daniel Nsowah • 7 Jul 2026
Authorize structured Enterprise Architecture analysis and promotion into Projects for controlled execution. This G2 decision does not authorize plugin build, code changes, module/folder restructuring, public positioning, contract rewrites, product/service renaming, or any implementation beyond producing the approved analysis deliverables.
G3 — go
Project • Daniel Nsowah • 7 Jul 2026
Commence controlled execution with WP1: Evidence Inventory. WP1 must remain evidence collection, not premature analysis, and must capture metadata for source, module, repository location, evidence type, confidence, date captured, and related deliverables where available.
G5 — go
Project • Daniel Nsowah • 10 Jul 2026
Proceed to WP5: Prepare Gate Review Pack and Lessons. WP5 must clearly distinguish what Project Baobab has demonstrated from what it merely suggests, and must separate established knowledge, open questions, and future opportunities.
G6 — go
Project • Daniel Nsowah • 10 Jul 2026
Close Project Baobab discovery phase. Preserve the Baobab methodology as the foundation for future enterprise initiatives: evidence before action; separate demonstrated knowledge from suggestions; distinguish established knowledge, open questions, and future opportunities; preserve independent-review challengeability from recorded evidence; do not treat closure as authorization for implementation, plugin build, public positioning, restructuring, or principle promotion.
BA Documents Carried Forward
The pre-project logic that should govern delivery decisions.
Needs assessment
Portfolio & BA artifact
# Project Baobab — G1 Forensic Enterprise Assessment **Portfolio stage:** G1 Needs Assessment **Initiative:** Project Baobab — GAB Enterprise Architecture & Institutional Map **Decision question:** Is there sufficient evidence that Project Baobab is necessary now? **Working rule:** This assessment does not propose solutions, redesign architecture, build a plugin, or recommend implementation scope. It tests whether the evidence justifies progressing to deeper Portfolio & BA analysis. --- ## 1. Executive Summary Project Baobab was prompted by an observed mismatch between the maturity of GAB OS as implemented and the degree to which GAB's enterprise architecture is explicitly document
Charter
Portfolio & BA artifact
# Project Baobab — G2 Charter Basis **Portfolio stage:** G2 Charter Basis **Initiative:** Project Baobab — GAB Enterprise Architecture & Institutional Map **Decision question:** Should GAB authorize structured Enterprise Architecture analysis as a governed initiative? **Boundary:** This charter basis authorizes analysis only. It does not authorize implementation, plugin build, code changes, restructuring, public positioning, or contract rewrites. --- ## 1. Purpose Project Baobab exists to discover, classify, and document the enterprise architecture that already exists across GAB Climate Smart Investments Ltd and GAB OS. The G2 purpose is to authorize a structured Enterprise Archit
Transition to Operations
Define where the project output lives after delivery.
No operational handover recorded.
Requirements Traceability
No requirement trace links recorded.