# גבולות שינוי הפלטפורמה

> תיעוד היסטורי. מקור: docs/platform/change-boundary.md · 6a466bf.

Baseline: local commit 6934afc, verified Visual System 2.0. Branch: feature/multitenant-platform.

Allowed: additive platform routes, APIs, tenant-aware data model, database policies, domain services, onboarding and fleet screens, tests and deployment configuration. Existing driver demo, approved visuals, library, assets and interactions remain unchanged except for a link into the new platform. Migration 0001 is preserved; new migrations use names generated by the Supabase CLI.

Verified discovery: existing app is a browser-local demonstration; no EV1 Supabase project is visible; Clerk application list is empty. User selected a separate Supabase organization named EV1 and will connect it. Do not deploy schemas into the unrelated digitalops Car Dealers BMS project. Charger and payment providers are not yet identified.

Acceptance: personal and business tenant creation, active membership checks, server validation, tenant-bound foreign keys, role-based writes, per-tenant fleet management and analytics, and negative PostgreSQL RLS tests for cross-tenant access. Real charger commands and payments remain disabled until verified adapters are configured. Demo data is explicitly separated from production APIs. No customer/driver invitations are sent during implementation.

Rollback: return to baseline branch/commit; retain prior verified Vercel preview. New migrations are additive; no destructive rollback SQL or user-data deletion is performed automatically.
