## In scope Whatever is required from AutoFlow for the CD work is in scope of the MVC. - [ ] https://gitlab.com/groups/gitlab-org/-/work_items/22238+ - [ ] https://gitlab.com/groups/gitlab-org/-/work_items/22239+ - [ ] https://gitlab.com/groups/gitlab-org/-/work_items/22240+ - [ ] https://gitlab.com/groups/gitlab-org/-/work_items/22241+ - [ ] https://gitlab.com/groups/gitlab-org/-/work_items/22242+ - [ ] https://gitlab.com/groups/gitlab-org/-/work_items/22243+ - [ ] User-facing documentation for GitLab instance admin - [ ] How will namespaces work? ## Success Metrics | Metric | Target | |--------|--------| | Replay correctness | Workflow resumes correctly after crash at any step; 0 data loss or duplicate side effects | | Engine durability | 0 silent workflow failures across all MVC test scenarios | ## Non-Goals - To support the CD work, we don't need the Events Platform (we are going to use channels/signals to deliver events point-to-point) so we can postpone subscribe/send implementation. ## Dependencies ## Weights We are using this *weights* description table for estimations: https://handbook.gitlab.com/handbook/engineering/devops/runner/environments/#issue-weighting We can roughly guess "timeframes" for the weights: | Weight | Timeframe | |--------|-----------| | 1 | 1 day | | 2 | 1-3 days | | 3 | ~1 week | | 5 | 1-2 weeks with "big" uncertainty |