Read-only records under inactive definitions

Context

Retiring a category must stop maintenance without making existing references and history unreadable.

Decision

Ordinary custom-record changes require an active category, while retained records under inactive definitions remain readable by identity and removable through applicable cascades.

Alternatives Considered

Hiding every inactive-category record: References and retained historical navigation would lose their readable targets. Continuing direct writes after retirement: Archival would cease to be an effective boundary for ordinary maintenance. Stopping cascades at inactive categories: Owner deletion could violate the continuing ownership policy and leave dependants behind.

Consequences

Record writes hold a shared parent lock while checking active status. Screens retain readable identity views and suppress unavailable mutations.