Architecture: Is the platform ready for space builders to manage their end...

Documentation for Sessions

🏗️ Architecture: Is the platform ready for space builders to manage their end...

Date: 2026-03-19
Time: 21:21:05 UTC
Session: gspace1-241.2
Agent: architecture
Confidence: 93%
Status: ✅ Documented

📋 Decision Context

Question:

Is the platform ready for space builders to manage their end customers (L4) as a business platform, including sending notifications and communications?

Task: Assess L4 customer management readiness for business platform promise

🎯 Decision Made

Chosen:

Not ready. L4 customer management is a skeleton with 5 P0 gaps: self-registration throws NotImplementedException, password reset throws NotImplementedException, no phone field on PlatformUser, bulk invite never delivers credentials, slug→ID resolution missing. The notification/communication specs (2026-03-19-platform-notification-system-design.md and 2026-03-19-business-communications-system-design.md) are architecturally sound but depend on this foundation. Implementation order: P0 foundation → Spec 1 (platform notifications) → Spec 2 Phase 1 (business communications email) → customer management UI.

Options Considered:

💭 Reasoning

Deep audit verified every claim by reading source code. PlatformUser schema has all the right fields (2FA, analytics, lockout, metadata) but service layer has critical stubs. The notification infrastructure (ProactiveDispatcher, ChannelGateway, messaging-core) is production-quality for Vitto→developer alerts but not designed for B2B2C business communications. The specs correctly identify this and route business comms through backend-api directly using messaging-core. BYOT credential model works but stores creds unencrypted — acceptable risk for now, needs field-level encryption before production B2B2C launch.

📁 Files Involved

🔗 Related

Auto-generated by MCP Smart Consolidation