Regional Placement

What It Models

Placement is the regional value staff see on a person or organization. Staff can choose it directly, or Regions can calculate it from geographic coverage. The record-level override protects a deliberate exception from later matching and recalculation.

Identity and Attributes

The owning record supplies identity. Its regional facet holds the current region, override and remembered address fingerprint. That fingerprint includes the deciding source and recognized address fields. It distinguishes unchanged input from a removed address and from a record for which no address has ever been decided.

Relationships

Entities owns the person or organization and stores the placement fields. Regions supplies automatic decisions through the record owner’s persistence functions. Contacts can resolve deciding addresses through effective affiliations; organization changes therefore need a separate linked-contact reaction.

Invariants

Record locking prevents concurrent record writes from interleaving with a decision. Repeated input is skipped, overrides remain protected, and fingerprint-only maintenance preserves the version. The record lock does not freeze policy reads or a linked organization’s address. Those concurrency limits qualify the convergence claim.

How It Is Stored and Shared

Placement remains on the contact or organization and is available through its record surfaces. Regions keeps no duplicate table. Ordinary saves omit the fingerprint, leaving regional processing responsible for its maintenance. Changed regions enter the record’s normal change and history mechanisms.

Open Design Questions

Affiliation expiry alone produces no regional reconciliation. A later organization-address event or recalculation can update a placement whose linked input stopped resolving. Policy read consistency and the reported inactive-choice display gap also remain open.