Region Locks Need Dedicated, Audited Actions

Context

The recorded lock policy separates lock management from ordinary editing and requires authorized reversible actions with audit. Regional definitions have not received that surface.

Decision

The product should introduce regional lock and unlock actions with their own authority and stop ordinary requests from managing locks. This records an existing policy obligation and its missing implementation, rather than deciding the policy again.

Alternatives Considered

Continue accepting lock fields through ordinary edits. An updater can create a full lock that ordinary edits cannot remove, or clear a delete lock by omitting it during replacement.

Remove regional lock capability. The recorded shared policy retains customer locks, including protection for integrated configuration.

Consequences

The regional lock plan lists dedicated actions as outstanding. Stored rule locks have no enforced operational behavior until rule-lock applicability is resolved.