Shared Engine With Service-Owned Storage

Context

Bulk work spans several record owners, each responsible for its persistence and save rules.

Decision and Origin

Adopting services execute the shared engine against eight local tables and their own domain operations. The origin recorded above supplies the authority for this choice; implementation evidence supplies the limits described here.

Alternative Comparison

Central execution with per-record service calls: Remote calls cannot commit a domain change and its local receipt together.

Independent bulk implementations in each service: Separate implementations would duplicate version capture, receipts, batching and recovery behavior.

Consequences

The owner can commit the record, receipt, history and producer mapping together.

Job listings remain service-local; the current console reads CRM jobs.

The cited release decision requires adopters to use the same engine version.

Adoption requires local tables, operation routes and execution infrastructure; Membership has declarations but lacks runnable storage.