Two editors target the same named branch version

A fictional editing project uses the documented branch-versioning model with a named version for one task. One editor begins an edit session and obtains the relevant exclusive edit lock. A second person tries to edit that same named version and receives a lock message, while an editor in a separate named version continues working. A colleague proposes deleting repository rows to remove the lock. Another checks active ownership, intended version isolation and supported session handling. This written case acquires no lock, disconnects no user and edits no metadata. It asks why the observed behavior can fit the intended model and how authorized coordination differs from an unsafe direct repository modification.