Reconcile Geo category maturity conflicts

Why is this change being made?

💡 Provide a detailed answer to the question on why this change is being proposed, in accordance with our value of Transparency.

Please add the details saying why, not just what in this section. Example: We have discussed the topic in Slack - (copy of Slack conversation). The current process is not efficient, this MR makes the description of X more clear, and helps move Y forward.

There are conflicts in Geo's handbook pages regarding the maturity level of its categories:

• Geo Replication
• Disaster Recovery

This MR attempts to fix them by assuming that Category Maturity Updates (!132194 - merged) is correct and aligning to it.

Related (please take a peek at any you haven't seen)

• Category Maturity Updates (!132194 - merged)
• 🌏 Lovable maturity for Geo-replication (gitlab-org&9132)
• 🚨 Disaster Recovery lovable maturity (gitlab-org&4988)
• https://handbook.gitlab.com/handbook/product/ux/category-maturity/category-maturity-scorecards/
• https://about.gitlab.com/direction/geo/

To Do

If this MR gets merged with its proposed changes as of 2025-10-13, then we need to:

• Rename epic 🌏 Lovable maturity for Geo-replication (gitlab-org&9132) from Lovable to Competitive because of 2 reasons, Geo Replication got downgraded, and the maturity levels were renamed.
• Rename epic 🚨 Disaster Recovery lovable maturity (gitlab-org&4988) from Lovable to Complete because the maturity levels were renamed.

Author and Reviewer Checklist

Please verify the check list and ensure to tick them off before the MR is merged.

• Provided a concise title for this Merge Request (MR)
• Added a description to this MR explaining the reasons for the proposed change, per say why, not just what
  • Copy/paste the Slack conversation to document it for later, or upload screenshots. Verify that no confidential data is added, and the content is SAFE
• Assign reviewers for this MR to the correct Directly Responsible Individual/s (DRI)
  • If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the Maintained by section on the page being edited
  • If your manager does not have merge rights, please ask someone to merge it AFTER it has been approved by your manager in #mr-buddies
  • The when to get approval handbook section explains the workflow in more detail
• For transparency, share this MR with the audience that will be impacted.
  • Team: For changes that affect your direct team, share in your group Slack channel
  • [-] Department: If the update affects your department, share the MR in your department Slack channel
    • [-] Company: If the update affects all (or the majority of) GitLab team members, post an update in #whats-happening-at-gitlab linking to this MR
      • For high-priority company-wide announcements work with the internal communications team to post the update in #company-fyi and align on a plan to circulate in additional channels like the "While You Were Iterating" Newsletter

Commits

• Reconcile Geo category maturity conflicts

---