Outline Reliability stable counterpart scope of work

Why is this change being made?

We have been piloting the Reliability stable counterpart and continue to see success. At the same time, we continued to refine and improve our Reliability workflow for prioritizing requests from within and outside the infrastructure team. The general workflow is the default process to prioritize work within Reliability.

This MR is another step towards providing more structure for the stable counterpart. The MR outlines the scope of work for a stable counterpart and adequately incentivizes the process. Requests outside the defined scope should use the General workflow for correct prioritization.

The change will also help provide guidance and clarifications for stable counterpart requests from stage teams by providing a checklist and driving fast decision-making.

Current stable counterpart requests

• Analyze:Product Analytics - #16790
• Monitor::Observability - #16789
• ML Ops

Ongoing stable counterparts

• Gitaly - gitlab-com/gl-infra&830 (closed)
• Runner - gitlab-com/gl-infra&804 (closed)
• Fulfillment - #4923

Previous stable counterpart efforts

• Gitaly - gitlab-com/gl-infra&783 (closed)
• Fulfillment - gitlab-com/gl-infra&626 (closed)

Author Checklist

• 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.
• 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
• If the changes affect team members, or warrant an announcement in another way, please consider posting an update in #whats-happening-at-gitlab linking to this MR
  • If this is a change that directly impacts the majority of global team members, it should be a candidate for #company-fyi. Please work with internal communications and check the handbook for examples.

---