EF-009 — Enterprise Architecture
Document ID: EFType: GuideStatus: ApprovedOwner: Cloudberrie StudioVersion: 1.0Updated: 2026-07-17
Target Architecture
Team / Clients→Google Workspace Identity→GitHub Source→Cloudflare DNS & Delivery→Firebase Backend where required→Cloudberrie Products
Layer Responsibilities
| Layer | Responsibility |
|---|---|
| Identity | Workspace users, aliases, recovery, communication, role ownership |
| Source | GitHub organization, repositories, history, reviews |
| Edge & Hosting | Cloudflare DNS, SSL, Pages, security, Access where required |
| Application Backend | Firebase Authentication, Firestore, Storage, security rules |
| Products | Website, Studio Board, EventLumi, AIFA, and future systems |
| Governance | Registers, standards, approvals, documentation, audit and reviews |
Separation Principles
- One Firebase project per product is preferred when data, billing, security, and lifecycle need isolation.
- Cloudflare frontend deployment does not deploy Firestore rules.
- Staging and production behavior must be explicitly separated.
- The company domain DNS and Workspace email records are shared dependencies and have a broad blast radius.