Capstone clean-room release evidence
This required 20–30-hour integrated package strengthens the existing guided labs. Allocation: lessons/predictions 4–6 hours, clean-room/release 10–16, assessment/repair 6–8. Author estimates require learner timing pilots and are included in the semester workload contract. Reuse the same service and evidence; avoid creating a second portfolio.
Prerequisite bridge
Bring the preceding module's implementation, risk record and failure observations. Separate assumptions, model results and actual runtime evidence. Review the specific prerequisite named in each lesson before its exercise. Missing runtime tools leave execution evidence pending; a written prediction is not an executed experiment.
Lesson sequence
- Make the deployment independent of your workstation.
- Prove both sides of a schema transition.
- Close the deployment record with observable outcomes.
Integrated experiment
Perform the original clean-room, trusted pipeline, staged rollback and teardown labs on the capstone. Add a second-operator reproduction record and old/new reader/writer compatibility matrix. Local reproduction is a valid rehearsal; where the existing project requires a real IaC-driven cloud deployment, keep that graduation gate pending until an authorized real run exists. This authoring task does not purchase or deploy infrastructure.
Complete the assessment. Original guided labs, security controls, deployment/testing and peer requirements remain mandatory. Use synthetic data and a disposable local environment where supported; no cloud purchase is required by this extension.