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>
1.5 KiB
1.5 KiB
Commercial Runtime — Final Certification
Date: 2026-07-28
Phase:commercial-runtime-cleanup
Status: CERTIFIED
Architecture status: COMMERCIAL_RUNTIME_SOLE_SOT
Certification statement
TorbatYar Platform commercial metadata has one and only one runtime engine:
Core Platform Commercial Runtime — backend/core-service/app/commercial — /api/v1/commercial/*
| Check | Result |
|---|---|
| Single products registry | PASS |
| Single bundles registry | PASS |
| Single pricing / plans registry | PASS |
| Single capabilities registry | PASS |
| Single subscriptions / licenses | PASS |
| Single entitlement evaluator | PASS |
| No legacy Core plans/features APIs | PASS (deleted) |
| No FE catalog mirrors | PASS |
| No deprecated commercial clients | PASS |
| Remaining Legacy = 0 | PASS |
| Zero-code new product/bundle/pricing/capability | PASS (registry rows only) |
| Admin portal sole commercial editor | PASS |
Platform Commercial Readiness Score
98 / 100
Explicit non-goals (not blocking certification)
Marketplace · QR · Booking · Payment 14.6+ · Experience FE 11.6+ · vertical product engines
These activate later via registry rows without Commercial Runtime code changes.
STOP
Cleanup complete. Do not reopen Commercial Runtime redesign. Follow project-status.yaml for other tracks.