Every Regional Reference Stays Inside Its Workspace

Context

The port requires local regional references and refusal of deletion while a region is used. Captured delivery infrastructure also needs cross-workspace dispatch access.

Decision

Business operations use the signed execution workspace, and composite keys constrain newly written regional and address-type references. Existing contact and organization references can remain unvalidated. Captured event rows are shared dispatcher infrastructure rather than ordinary workspace-readable business records.

Alternatives Considered

Enforce reference ownership only in application checks. Database keys cover write paths beyond one API caller and prevent committing new foreign-workspace references.

Delete referencing records automatically with their region. The recorded port requirement preserves referencing records by refusing removal of a used region.

Consequences

Region removal fails while records or rules still use its definition. New references to missing local regions are refused. Older regional references retained when constraints were introduced remain tolerated.