Verify Stage / SRE Stable Counterparts

As a follow up to a conversation @AnthonySandoval and I had a couple weeks ago, I wanted to create this issue to capture ideas and discussion related to supporting stable counterparts between SRE and the Verify stage. There are likely a number of approaches we could take which I will document below as they are discussed. @AnthonySandoval, if you are aware of exiting models in place, please feel free to add them below.

In this relationship, I think there are two sources of work, SRE initiated and Development initiated, each of which would have a different process.

SRE initiated

In this situation, SRE discovers something that requires engagement from engineers in development. This could be related to an incident, or some other issue.

What are our processes here outside of the ~infradev workflow? https://gitlab.com/gitlab-org/gitlab/-/issues?scope=all&utf8=%E2%9C%93&state=opened&label_name[]=infradev&label_name[]=devops%3A%3Averify

Development initiated

In this situation, Development would benefit from some form of consultation with SRE in regards to the impact of an upcoming feature or architecture change. In reviewing the SRE Engagement Model, I think a process could be developed to provide engineers a channel to engage with SRE during the development process. Perhaps a new issue based on some template (with some set of labels) would be a reasonable MVC.

What am I missing? Are there already processes for this I am unaware of?