Source Inputs & System Heritage

vibrant-platform consolidates and modernizes software previously scattered across multiple repositories.

This document summarizes what was carried forward and what was intentionally retired.

---

What Came From Where

1. holding_co_ops (Operations & Invoicing)

• Carried Forward: dbmate SQL migrations, local Docker compose stack conventions, Keycloak auth patterns, and early invoicing/receipt workflows.
• Modernized: Rewritten from scratch with formal SQL domain schemas, strong typed RPC contracts, and isolated background workers.

2. Vibrant.Platform (Legacy .NET Monolith)

• Carried Forward: Core domain concepts for accounts, sites, physical zones, hardware devices, firmware versions, and provisioning workflows.
• Retired: Legacy .NET runtime, Supabase-specific dependencies, and broad public schema table coupling.

3. vibrant-infra (Deployment & Infrastructure)

• Separation of Concerns: Production Kubernetes cluster manifests, Helm releases, external secrets (OpenBao/AWS Secrets Manager), and edge ingress configs live strictly in ../vibrant-infra.
• Platform Ownership: This repository owns application code, database migrations, SQL schemas, and local development configurations.