# Architecture Decision — Prototype

**Status:** accepted for implementation planning.

## Prototype stack
Laravel + Blade/Bootstrap + MySQL. Deploy as a modular monolith on shared cPanel using a single PHP application entry point.

## Multi-tenancy
Preferred: a platform database and separate tenant databases if hosting quotas permit. Fallback for demo use only: tenant-scoped shared tables with mandatory tenant context, authorization and isolation tests.

Never assume that database-per-tenant by itself supplies compliance, private compute or independent tenant-level restore.

## Evolution to production
The production target is Vue 3 staff web, React Native patient mobile, Laravel microservices, PostgreSQL, a message broker and managed cloud infrastructure. Share concepts, API contracts, validation semantics and acceptance tests where feasible; do not promise migration without adaptation.

## Prototype limitations
No clinical offline synchronization, cross-tenant health information exchange, clinical AI inference, or dependency on always-running workers. No real patient records.