Skip to main content

Capstone clean-room release evidence — assessment

Score 0 absent/incorrect, 1 prompted/incomplete, 2 independently supported with explicit limits, 3 justified fresh transfer. Every category requires at least 2; a high average cannot hide a missing category.

Required evidence​

  • CD1 — Baseline: Declare and recreate the clean-room boundary without hidden author state.
  • CD2 — Identity: Link reviewed source, tested artifact, signature/provenance policy and running digest.
  • CD3 — Access: Retain scoped short-lived deployment identity and separate runtime privileges with negative tests.
  • CD4 — Migration: Exercise old/new data compatibility and retry-safe migration on real storage.
  • CD5 — Recovery: Inject a regression, measure recovery and verify user/data behavior after rollback.
  • CD6 — Closure: Retain independent reproduction, cost/retention assumptions and complete or explicitly unresolved teardown inventory; label local versus cloud evidence.

Calibration​

A successful clean checkout with a reused database is not an empty-state migration test. Rebuilding during promotion breaks the original artifact chain. A local environment cannot satisfy a claim of actual cloud deployment. A failed inventory query leaves cleanup unresolved.

Delayed transfer and integrity​

After at least 48 hours, have a reviewer change one assumption or select a previously unseen failure. Predict the outcome, collect fresh evidence and explain discrepancies without the calibration text. Preserve mistakes, repairs, collaboration and generated-assistance disclosures. Record unavailable tools or reviewers as pending evidence, never fabricated completion. Author reference checks are not learner runtime experiments.