דילוג לתוכן
מרכז התיעוד
לאתר LinkNodes Energy
LinkNodesENERGYתיעוד

טוענים את החיפוש…

    חיפוש גם בתוך המאמרים ↑ ↓ לניווט Esc לסגירה

    לאתר החברה

    מוצר ויכולות

    מקורות Product System

    מקורות המפרט, תוצרי היצוא ותהליך שינוי מערכת המוצר.

    בעמוד הזה

    The Product System is an executable reference specification, not a claim that all product capabilities are live. It connects B2C and fleet journeys to domain rules, roles, commercial proposals, data, service operations, measurement and release evidence.

    Sources and outputs#

    • lib/product-system/spec.json: canonical versioned specification, with stable IDs.
    • lib/product-system/catalog.ts: navigation, cross-references and local teaching simulators. Permissions derive from the existing domain can() function. Charging simulation validates against existing assertTransition().
    • lib/product-system/event-contract.ts: strict event envelope and property/type validation only. It performs no telemetry transmission. An allowlist/type validator is not a semantic PII detector: producers must still use approved non-sensitive code values and pseudonymization.
    • /product-system: Hebrew RTL interactive library, 14 chapters, search, cross-links, maturity/domain filters, journey explorer, state workbench, proposed entitlement simulator and single-session savings example.
    • docs/product-system/handbook.md: generated complete handbook.
    • public/product-system/handbook.md and product-system.json: downloadable copies generated from the canonical file. They contain specifications, never customer records, tokens or live analytics.

    Run pnpm product:generate after editing the canonical JSON. Generated files are committed so deployment requires no network or build-time generation. Tests reject stale JSON exports, handbook divergence, orphan IDs, missing evidence files and state/role drift.

    What changed#

    Additive product reference route and one navigation link; no redesign of approved driver/fleet screens. No authentication, database, payment, charger, package limit or production permission changes. No messages sent. No new PostHog event emission. Baseline 90d2981 is the rollback reference.

    Maturity is explicit: local demo, source foundation not cloud-verified, or specified/not implemented. All eight production release gates are blocked until actual evidence is recorded. The proposed four plans have no invented prices, quotas or SLA. Monitoring/security are baseline platform requirements across all plans. Future support and refund roles do not silently acquire current admin privileges.

    The specification identifies a real current gap: charging has no requested/authorized -> reconciliation_required transition. This is recorded as D11 and a live-charging release dependency; this task does not modify the operational state machine without a provider contract and migration review.

    Change process#

    Change stable IDs, affected journeys/rules/states, acceptance criteria and release evidence together. Proposed business policy stays separate from implemented behavior. Updating this reference never silently deploys new business rules. Physical charging, payment collection, financial documents and privacy decisions require the corresponding engineering/integration work described in the delivery backlog.

    Verification scope#

    The role table uses current LinkNodes Energy permissions; generated role data is checked for drift. State tests exhaustively compare the charging specification with all runtime state pairs. Contract tests verify unique references, dependency order, reachability, source evidence, export parity, strict event types and rejection of unlisted fields. Browser tests cover search/deep links, back navigation, maturity filtering, guarded transitions, terminal states, plan/role/readiness intersections, negative savings, downloads and all 14 chapters at 390/320px. This validates the product library, not unimplemented payment or charging integrations.