Internal documentation for the whole GoBuild platform. Every page is grounded in
the actual code and carries an honest status badge:
🟢 Live · 🟡 WIP / config-gated · ⚪ Dormant · ❌ Dead-end / vaporware
House terminology (enforced everywhere): a unit of work is a Job; the
customer is a Client. Flag any screen that says "Project" or "Customer".
One app serving staff + clients + prospects. Nav = ⌂ Home + 5 command centers.
Client / proposal / bid / invoice / sub / landing portals + booking.
The Keystone AI bar + provider architecture (DeepSeek / Gemini) + retrieval.
Prospect mock-site viewer + feedback (showcase.gobuild.ca).
ops (atlas + fleet), provisioning, multi-tenancy, credential wall-off, impersonation.
Fleet topology, Compose, Caddy, deploy, DNS, backups, go-live.
All 15 integrations with per-integration status + the credential wall-off model.
Known Risks & Tech Debt — the consolidated security / ops /
privacy register uncovered while documenting. Several critical items
(fleet god-mode is password-only, no offsite backups, invoice portal has no auth
gate). Read it.
Roadmap & To-Build — the prioritized build backlog of everything
decided while documenting, gated by the first-real-tenant milestone.
Command centers are sold à la carte — a client may buy only Marketing, or only
Jobs. So every CC is documented as self-contained, with cross-CC dependencies called
out explicitly. Nothing is "secondary".
This instance is demo/prospecting-first — no real production tenant yet. Many
money/integration features are real but config-gated (empty keys ⇒ soft-fail).
Pages mark what actually works vs. what needs credentials or is still WIP.