Type: ADR RegisterStatus: ActiveOwner: Cloudberrie StudioVersion: 4.2.0Updated: 2026-07-17
ADR-001 — Use Cloudflare Pages
| Decision | Use Cloudflare Pages for static sites and appropriate web applications. |
| Reasons | Git integration, CDN, SSL, simple deployment, DNS alignment, and cost efficiency. |
| Consequences | DNS changes must preserve Workspace email; Firebase rules deploy separately. |
| Status | Accepted |
ADR-002 — One Workspace User with Aliases
| Decision | Keep admin@ as the licensed account and use role aliases for public and departmental communication. |
| Reasons | Lower cost, consistent branding, simple management. |
| Consequences | Aliases cannot log in and require Send Mail As, labels, and filters. |
| Status | Accepted |
ADR-003 — No Sample Data in Production
| Decision | Production mode displays only records from production Firestore. |
| Reasons | Trust, data integrity, accurate reporting, and professional client experience. |
| Status | Accepted |
Current Architecture Decision Records
| ID | Decision | Rationale | Status |
|---|
| ADR-001 | Use a GitHub organization named cloudberrie-studio | Company ownership separate from personal repositories | Accepted |
| ADR-002 | Use cb-engops as the initial GitHub administrative identity | Separates engineering administration from a founder’s unrelated personal GitHub activity | Accepted |
| ADR-003 | Use engineering@cloudberrie.com for temporary shared commit attribution | Professional company attribution until individual engineers are onboarded | Accepted |
| ADR-004 | Use accounts@cloudberrie.com as Cloudflare owner | Places billing, recovery, and platform continuity under a business function | Accepted |
| ADR-005 | Delete the empty Google-connected Cloudflare profile and start clean | No resources existed, allowing a clean ownership model without migration risk | Accepted |
| ADR-006 | Use Cloudflare Pages for the first corporate website deployment | Git integration, global delivery, SSL, preview deployments, and current scale | Accepted |
| ADR-007 | Use the cb- repository prefix | Consistent organization-wide discovery and naming | Accepted |
| ADR-008 | Standardize local projects under ~/Documents/Cloudberrie/Projects | Predictable onboarding, backup, and command documentation | Accepted |
ADR-009 — Apple Passwords for the 2026 Startup Phase
| Decision | Use Apple Passwords as Cloudberrie’s approved password manager during calendar year 2026. |
| Reasons | End-to-end encrypted Apple ecosystem integration, no additional subscription, appropriate for the current small administrator group, and a clear migration path. |
| Constraints | No secrets in documents, email, chat, screenshots or source control. Keep one controlled encrypted offline recovery copy. |
| Review | January 2027, or earlier when three or more employees need shared credential access, audit logs, role-based vaults or centralized offboarding. |
| Status | Accepted |