# גבולות שינוי מערכות התיעוד

> תיעוד היסטורי. מקור: docs/systems-change-boundary.md · 6a466bf.
> בגרסה הציבורית הושמטו מזהים תפעוליים ופרטי חשבון אישיים. קובץ המקור נשמר במאגר.

Baseline: f53f930. Branch: feature/architecture-data-systems.
User authorized implementing the production roadmap and explicitly selected the existing ev1 Supabase project in digitalops (Singapore). Charging and payment providers have not been selected.

Deliverables: versioned architecture/data catalogs, searchable product libraries, downloadable handbooks, migration-derived schema dictionary, strict provider/financial contract foundations and tests. Apply the previously locally verified database foundations to the selected empty cloud project and verify RLS/grants. Prepare identity configuration using the existing Clerk application, preserving separate customer and company-staff authorization.

Locked: approved website/product flows and visual identity, existing storage keys, existing tenant roles. No live charging/payment adapter, invented SLA, automatic mail, or customer-data import. Libraries expose design/schema definitions only, never customer data or secret credentials.

Acceptance: generated dictionary matches committed migrations; catalog references resolve; invalid cross-tenant and financial contract examples are rejected; browser search/filter/deep links/downloads and mobile layout work; all three deployment surface boundaries remain enforced. Cloud database evidence is distinct from actual JWT authentication acceptance.

Recovery: previous Vercel product deployment \[operational-id-redacted]. Database was verified empty before applying legacy_driver_foundation and platform_foundation; both succeeded. Future schema corrections must be additive migrations. Do not drop customer objects as an automatic rollback.
