Sovereign became Operator—and the old name became compatibility

Product naming is infrastructure when it reaches storefronts, routes, bundles, receipts, and customer records.

The current product is Black Label Operator. It is the autonomous desktop and company-operations product. The earlier Sovereign name is no longer a separate active offering.

That sounds like a copy edit until the old name appears in package identifiers, historical receipts, protected downloads, role records, and links that existing customers may still use. Deleting every old identifier would make the public catalog cleaner while creating avoidable breakage underneath it.

The rule is now explicit:

• Operator is the canonical public name.
• operator is the canonical current package identity.
• Sovereign is a legacy compatibility alias.
• Existing customer keys, downloads, bundle identifiers, and historical receipts remain valid.

What changed on the public site

The technology catalog no longer presents Operator and Sovereign as two current products. Operator holds the active identity. The retired catalog can acknowledge the old record without implying that a second product exists.

This is the difference between renaming a heading and migrating a product safely. Public language can become clear immediately. Destructive identifier changes require a separate migration with proof that customers will not lose access.