Shared Table Reads and Durable Migration Handovers

Context

Catalogue consumers need data at different moments. The reversible session choice stores special-price handover context in a table.

Decision

Shared readers consume common product tables within workspace policy, while durable migration handovers retain Commerce realization context without proving an implemented consumer.

Alternatives Considered

Add separate read operations or events for every consumer. The cited architecture already permits shared-table reads while reserving writes for owners.

Emit a migration message for every former special price. A handover table preserves context without requiring an active message consumer during migration.

Consequences

Shared schema changes can affect every reader. A realization timestamp does not establish retry safety, alerts or queue delivery.