Shared Configuration Protection

Context

System or migrated configuration can require protection. The current wire and persistence paths expose protection without a complete staff management experience.

Decision

Configuration protection uses the shared lock level to block updates, deletion or both according to the retained level.

Alternatives Considered

Add a separate Commerce protection flag. Shared system metadata already supplies the level and write checks.

Consequences

A client can set protection, but a full lock blocks the route that would remove it. Built configuration screens do not expose protection controls or state.