Unify commercial runtime ownership across backend and frontend so platform, experience, and hospitality modules use the shared commercial source of truth. Co-authored-by: Cursor <cursoragent@cursor.com>
3.8 KiB
3.8 KiB
Commercial Runtime Final Report — E2E Completion
Date: 2026-07-28
Phase:commercial-runtime-e2e-wave-3
Architecture status: COMMERCIAL RUNTIME COMPLETE
Certification: CERTIFIED (FE usable end-to-end)
Backend follow-up: COMPLETE — see commercial-runtime-backend-final-report.md
Verdict
Commercial Runtime is fully usable as a metadata-driven SaaS shell:
- Admin Commercial Portal at
/admin/commercialmanages all registry surfaces via Core Commercial APIs (JSON create/update/delete — no FE catalogs). - Tenant surfaces (landing → assessment → recommendations → onboarding → trial → dashboard → apps → billing → domain → entitlements) are connected and API-driven.
- Admin registry changes are consumed by the same tenant adapters — no frontend constants.
Delivered (this continuation)
| Part | Delivery |
|---|---|
| Admin Commercial Panel | Hub + generic registry managers for products, bundles, pricing, plans, trial rules, templates, capabilities, policies, extensions, assets, automation, metadata, business types, recommendation rules (+ simulator), announcements, promotions, coupons, campaigns, regional pricing, taxes, currencies, languages, marketplace visibility, release channels, support levels, subscriptions, licenses, entitlements, activation logs, invoices, transactions |
| Trial management | Admin trial-rules registry; tenant trial banners/usage from APIs |
| Subscription management | Admin plans/templates/subscriptions; tenant billing activate/upgrade/downgrade |
| Tenant activation | Activation pipeline UI + checklist % from commercial APIs |
| Domain policy | Evaluate API → unlock, SSL, DNS instructions, verification state; FeatureLock |
| Commercial dashboard | Plan, trial, usage, capabilities, locked features, recommendations, invoices, licenses, health, registry browsers |
| Product discovery | Registry launch metadata only; entitlement gate on required capabilities |
| Billing | Pricing, invoices, transactions, coupons, upgrade/downgrade — published commercial APIs only (no Payment module edits) |
| Feature locks | Entitlement API + required plan/capability/bundle in UpgradePrompt |
| Recommendations | Tenant recommendation feed panel |
| Notifications | API-only (no coming soon) |
| Setup checklist | API checklist with completion %; product fallback without hardcoding catalogs |
| Admin ↔ Tenant sync | Shared /api/v1/commercial/* adapters |
Quality gates
| Gate | Result |
|---|---|
| No fake UI / placeholders / coming soon | PASS |
| No hardcoded products/plans/bundles | PASS |
| Dynamic dashboard / sidebar / launcher | PASS |
| Dynamic recommendations / billing / subscriptions / trials | PASS |
| Dynamic domain policy / feature locks / notifications | PASS |
| Admin updates visible to tenant (same registries) | PASS |
| End-to-end commercial flow connected | PASS |
Remaining gaps (backend)
Core commercial storage/engines still not implemented. Superseded: Commercial Runtime Backend is complete (commercial-runtime-backend). Deploy Core migration 0007 + seed for live catalogs.
Deployment readiness: FE ready + backend commercial APIs READY_AFTER_CORE_DEPLOY.
Artifacts
- Validation: commercial-runtime-validation.md
- Snapshot: service-snapshots/commercial-runtime-frontend.yaml
- Handover: phase-handover/phase-commercial-runtime-e2e-wave-3.md
STOP
No Hospitality / Payment / Experience / future roadmap foundations.