Software capability is not authority

Trap: software wording such as “owns,” “responsible,” “maintainer,” or a user’s ability to bypass a registry looks like organizational control because it describes who or what can act. Fix: treat implementation boundaries and product capabilities as non-institutional unless the source explicitly grants decision rights such as approve, merge, appoint, veto, budget, or strategy authority.