Mortezakoohjani 091b33a638 feat(platform): finalize commercial runtime, platform shell and hospitality production frontend

Co-authored-by: Cursor <cursoragent@cursor.com>

2026-07-28 20:39:10 +03:30

Boundary Rules

Hard constraints for every implementation phase. Violations block completion.

Canonical ownership: module-boundaries.md. Process mandate: ADR-018.

Service & Module Boundaries

Never implement responsibilities owned by another service.
Never duplicate business logic that already lives in an owning service — consume it.
Never access another service’s database (no cross-DB queries, FKs, or shared schemas).
Integrate only through versioned HTTP APIs, domain/integration Events, and Provider interfaces.
Never import another service’s models, repositories, or private modules.

Never move functionality from future phases into the current phase.
Never silently expand Scope into adjacent modules “while we’re here.”
Out of Scope is binding — document exclusions and respect them.
High-level roadmap text authorizes deriving production engineering for the current phase (definition-of-done.md, enterprise-phase-discovery.md), not pulling next-phase product features forward.

Allowed	Forbidden
External ID / ref fields (`*_ref`)	Cross-service foreign keys
HTTP clients to published APIs	Reading foreign ORM models
Outbox → event bus → consumers	Dual-writing the same journal/aggregate in two services
Provider adapters in the owning service	Implementing SMS/payment/etc. inside a non-owning vertical
Shared-lib envelopes/exceptions/JWT helpers	Shared-lib business workflows

Journal entries only via Accounting Posting Engine (ADR-010).
Messaging providers only inside Communication (ADR-012).
Product AI remains optional and independent (ai-architecture.md).
Public-surface cross-service attachments use publish_id only (ADR-022) — never Experience/vertical internal tables as the integration key.