Skip to main content

Capstone acceptance and scope 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​

  • CA1 — Claims: Provide three falsifiable acceptance claims with positive controls and precise scope.
  • CA2 — Domain: Retain glossary, context boundaries, aggregate invariants and external dependency contracts.
  • CA3 — Spike: Execute the highest-risk bounded experiment and show how its result changes a decision.
  • CA4 — Views: Reconcile runtime/data/deployment/trust views with the same user path.
  • CA5 — Alternatives: Retain three ADRs and actual reviewer challenge/revision evidence.
  • CA6 — Scope: Apply the capacity-loss card without dropping mandatory graduation evidence; state remaining uncertainty.

Calibration​

Reject-all booking satisfies a no-oversell assertion but fails the positive outcome. A mock external provider does not prove the provider guarantee. A scope cut that removes restore testing is not a valid schedule repair. A justified modular monolith can meet the architecture requirement.

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.