Recent feedback in T240943#5820996 as well as feedback given in various meetings with SRE indicates a need for greater refinement of the Seakeeper proposal.

1. Removal of orthogonal sections such as that on compute resourcing.
2. Scenarios detailing specific developer workflows from conception to production, using broadly illustrative examples such as:
   1. Service development
   2. MediaWiki development
   3. Debian packaging
3. Threat modeling for such scenarios that includes specific roles (patchset author, merger, artifact deployer, etc.), process flow, and data flow.
4. Details on how workflows can be sequestered based on such source event payloads and use of k8s annotations, including both physical (node level) and logical (namespace) segmentation.
5. Give examples on how artifacts might be promoted.
6. Clarify what is in and out of scope for this proposal (Seakeeper CI platform vs. future Deployment Pipeline that runs on CI)

Draft proposal: https://www.mediawiki.org/wiki/Draft:Wikimedia_Release_Engineering_Team/Seakeeper_proposal_(FY2019-20Q4_rework)