שחרורים ואימות
שחרור מסלולי המנוי
רשומת שחרור מסלולי החברה מ־8 בנובמבר 2026.
בעמוד הזה
Requested: add Personal, Family, Business and Enterprise to the company website, leave prices for a later decision, and develop the subscription/commission architecture. Existing confirmed terms remain monthly or annual subscription plus a customer-paid percentage on each charging transaction; Enterprise receives private custom terms.
Delivered source#
- Homepage plan cards, navigation/footer links and
/company/plans, included in the website sitemap and surface allowlist. - Monthly/annual selector, four plan cards, proposed-feature comparison, fee explanation, Family FAQ and inquiry links to the approved business email. The site does not send messages or collect subscriptions.
- One public plan catalog with null monthly/annual prices and commission rates; no zero-price fallback, annual discount, vehicle/member quota, unlimited usage or default trial.
- Commercial System 1.1.0 and Product System 1.2.0 aligned to the approved plan names. Family capability packaging and household tenancy remain planned; the old proposed Fleet/Scale plan names are removed from the current catalog.
- Proposed
commercialAgreementV2contract validates plan/workspace audience, billing account, entitlement and price revisions, explicit price/commission/tax policy, accepted terms and effective dates. The legacy V1 validator remains available for historical draft evidence. - Expanded architecture covers household isolation, personal/family/employer payer selection, price snapshots, recurring obligations, independent payment/document/accounting states, duplicate/out-of-order events, lifecycle changes and a staged implementation path.
Current boundary#
No database migration, active subscription, payment collection, real charger command, invoice issuance or account mutation is part of this release. The existing schema remains 31 tables / 256 columns. Family requires a household tenant implementation, permissions, invitations and privacy rules before activation. A valid contract object is not authorization to charge or activate a plan.
Local verification#
124 unit tests passed, including new catalog synchronization and version-2 contract boundary checks. ESLint and TypeScript passed. Optimized Next.js builds passed for both website and product surfaces. Four website browser scenarios and ten commercial/product-system browser scenarios passed. The company surface helper passed 61 checks across existing pages and the new plans page. Visual review covered the four complete plan cards and desktop/mobile layouts.
Verification expectations were updated after observed failures: exact FAQ text excluded the visible plus sign, and an immediate heading count captured the transient Next.js loading boundary. The revised checks wait for the intended rendered elements. The export filename/version expectation was updated from Product System 1.1.0 to the new canonical 1.2.0 and rerun.
Production deployment#
Runtime source: 69984ad4cdb24b48f82b3a50f8ca3b91604bbe33.
- Website:
[operational-id-redacted], READY, https://linknodesenergy.com/company/plans. - Product:
[operational-id-redacted], READY, https://product.linknodesenergy.com/commercial-system#plans.
Public-domain browser verification passed for the four plan cards, annual selector/inquiry target, 390/320 px layout, company sitemap, website rejection of the tenant API, product plan catalog, Commercial System 1.1.0 and Product System 1.2.0 downloads, architecture export and null unpublished prices/commissions. No browser page errors occurred. HTTPS health checks using system certificate trust returned ok with the correct website/product surfaces. Browser inspection used the environment's inspection-proxy certificate exception; independent curl checks did not disable certificate verification.
The company admin surface, DNS, existing customer accounts and database were not changed.