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.8 KiB
1.8 KiB
Phase Handover — Commercial Runtime Backend
Workstream: Commercial Runtime Backend
Phase ID: commercial-runtime-backend
Date: 2026-07-28
Status: Complete
Architecture status: COMMERCIAL_RUNTIME_BACKEND_COMPLETE
Service: Core Platform (backend/core-service)
Objective
Implement the complete Commercial Runtime Backend as the single SoT for commercial metadata — unlimited registries, discovery, engines, resolvers, events, OpenAPI, docs, green tests.
Delivered
- Universal
CommercialRegistryObject+CommercialRegistryKindmeta-registry - Built-in registry CRUD +
/registries/{kind}+GET /catalog - Recommendation / assessment / bundle / plan / license / policy engines
- Notification templates registry
- Subscription + license + activation tables (commercial lifecycle, not Payment ledger)
- Outbox events; Alembic
0007_commercial_runtime; seed script - Tests:
app/tests/test_commercial_runtime.py— 9 passed - Docs: final report, architecture report, snapshot, project-status
Explicitly unchanged
- No edits to CRM, Payment, Delivery, Experience, Hospitality, Healthcare, Beauty, Accounting, Communication, Identity business modules
- No Marketplace / QR / Booking / Payment 14.6+ product engines
Deploy notes
- Migrate Core: Alembic upgrade including
0007_commercial_runtime - Run
scripts/seed_commercial_runtime.py(idempotent) - Verify
GET /api/v1/commercial/healthand/catalog - FE commercial adapters light up against live registries
Next
Follow docs/project-status.yaml execution_priority / critical_path (Payment 14.6+, Hospitality 12.9+, …).
Future products: insert registry rows only.
STOP
Do not start Marketplace, QR, Booking, Payment 14.6+, or CRM from this handover.