Redesign

CLAUDE.md

@@ -91,17 +91,16 @@ Canonical sources only — avoid duplication:
 
 ## Architecture Context for AI
 
-### Hybrid Platform Architecture
-**MotoVaultPro uses a hybrid architecture:** MVP Platform Services are true microservices, while the application is a modular monolith containing feature capsules. Application features in `backend/src/features/[name]/` are self-contained modules within a single service that consumes platform services via HTTP APIs.
+### Simplified 6-Container Architecture
+**MotoVaultPro uses a simplified architecture:** A single-tenant application with 6 containers - Traefik, Frontend, Backend, PostgreSQL, Redis, and integrated Platform service. Application features in `backend/src/features/[name]/` are self-contained modules within the backend service.
 
 ### Key Principles for AI Understanding
 - **Production-Only**: All services use production builds and configuration
 - **Docker-First**: All development in containers, no local installs
-- **Platform Service Independence**: Platform services are independent microservices
-- **Feature Capsule Organization**: Application features are self-contained modules within a monolith
-- **Hybrid Deployment**: Platform services deploy independently, application features deploy together
-- **Service Boundaries**: Clear separation between platform microservices and application monolith
+- **Feature Capsule Organization**: Application features are self-contained modules within the backend
+- **Single-Tenant**: All data belongs to a single user/tenant
 - **User-Scoped Data**: All application data isolated by user_id
+- **Integrated Platform**: Platform capabilities integrated into main backend service
 
 ### Common AI Tasks
 See `Makefile` for authoritative commands and `docs/README.md` for navigation.