שחרורים ואימות
גבולות שינוי Product System
תיעוד תחום המפרט ושמירת הממשק וההתנהגות הקיימים.
Requested: end-to-end Product System, connected to existing Design/Visual Systems and B2C/B2B architecture.
Baseline: 90d2981; branch feature/product-system.
Add a versioned, machine-readable product specification, generated handbook/JSON exports, interactive /product-system reference and a navigation link from the existing driver shell. Include audiences, scope, lifecycle journeys, capabilities, tenancy/roles, commercial proposals, policy rules, domain states, metrics/events, service operations, privacy/accessibility, decision register, acceptance criteria, release gates and sequenced delivery.
Preserve approved driver/fleet behavior, visual tokens, authentication, database migrations and provider configuration. The reference library and its simulators do not change live permissions, plans, charging behavior or billing. Existing domain permissions and charging transitions remain authoritative; automated checks detect specification drift.
Verified current state: driver and fleet demo available in Vercel preview; tenant API/schema foundation locally tested; live EV1 Supabase integration and charging/payment providers remain pending as documented in docs/platform/architecture.md. No new cloud configuration is required for this task.
Acceptance: every capability has an owner role, acceptance criteria and maturity/evidence; all journeys link to rules/capabilities/metrics; every transition endpoint exists; commercial proposals have no invented price commitments; release blockers and evidence are explicit; search, filtering, deep links, simulators and exports work on desktop/mobile. No secrets or tenant data in exports. Rollback: previous preview/source baseline; no destructive database changes.