Release, Production Feedback, and Factory SRE
A review ready pull request is not customer value. Merge, deployment, runtime health, rollback, and outcome confirmation remain separate claims. A factory that stops at code generation can accelerate inventory while ignoring whether the cha
A rapid review of the chapter’s existing Quick Read, principles, definitions, lessons, and review material.
Reconstruct and defend this chapter’s architecture.
Reconstruct the architecture, name each boundary, and defend the tradeoffs.
Open the source exercise
Draw PR through outcome confirmation using an external CI/CD system. Add a stale head SHA, failed canary, irreversible migration, delayed incident, provider webhook replay, and rollback. Name each authoritative record and owner.
3. Enduring Principle
Govern deployment without requiring the factory to perform it
Mission Control may delegate execution to GitHub Actions, Argo CD, Jenkins, Azure DevOps, or another platform. It retains the decision, policy, evidence, approval, lineage, and reconciliation connecting the release to the governed Mission.
Keep release states explicit
Merge, deployed, technically verified, and outcome confirmed must have distinct owners, timestamps, artifacts, and evidence.
Use progressive delivery and reversible control
Risk-proportional release may use feature flags, canaries, limited cohorts, health gates, kill switches, and automated rollback. Irreversible migrations, security boundaries, customer data, and material business impact require human risk acceptance even when automation executes the steps.
Close the loop with production evidence
Observe SLOs, errors, security findings, support signals, usage, and the Mission’s expected customer measure. A default seven-day change-failure window should be configurable by workload. Production facts can invalidate earlier evidence and create corrective WorkOrders.
Operate the factory with SRE discipline
Define SLOs for dispatch availability, claim latency, lease health, event ingestion, evidence freshness, approval latency, provider reconciliation, orphan cleanup, and recovery. Use error budgets to decide whether to increase autonomy or pause feature expansion.
Operator attention is also a budget. Alerts should identify a required decision, risk, affected scope, evidence, safe actions, and what resumes afterward.
8. Notes and lessons learned
“Factory manages the entire lifecycle” must remain an architectural definition, not a claim that Mission Control currently automates every stage. Today’s proven boundary and tomorrow’s operating model must be spoken in different tenses.
9. Interview and discussion questions
- Why is merge not customer value?
- How can the factory govern an external deployment platform?
- Which production decisions must remain human?
- What SLOs should the factory itself have?
- When can production evidence invalidate acceptance?
Review this chapter.
Challenge a claim, boundary, missing failure mode, unclear term, or unsupported evidence statement.
- Claim
- Boundary
- Failure
- Evidence