Regions Decides Placement; Entities Stores It

Context

A regional value belongs on a person or organization, while geographic coverage belongs to the regional module. The ownership boundary must preserve ordinary record editing and automatic decisions.

Decision

Automatic processing calls the record owner’s persistence functions for reads and writes within its transaction. Entities owns the stored region, override and fingerprint, and ordinary saves omit the fingerprint.

Alternatives Considered

Store placement in an independent regional table. Record reads, exports and history would need another storage boundary, and existing record-version checks would no longer protect the visible region directly.

Calculate geographic placement during Entities saving. This would bring regional matching into every record write and conflict with the recorded asynchronous placement choice.

Consequences

Regional values remain accessible with their owning records through ordinary record surfaces. Persistence functions provide an in-process ownership boundary rather than a separate public placement endpoint. Ordinary record saves cannot replace the fingerprint maintained by regional processing.