Term project final checklist
Purpose
Use this checklist for the week 12 final. Point every claim at a reproducible artifact, command and revision. A polished interface without engineering evidence is incomplete.
Records
Delivered scope
- Final revision:
- Core scenario and expected outcome:
- Requirements delivered:
- Known limitations and out-of-scope items:
Verification
| Evidence | Revision | Command or configuration | Expected result | Observed result |
|---|---|---|---|---|
| Regression and test suite | ||||
| Mutation run and survivor review | ||||
| Evaluation script, including a wrong candidate | ||||
| Security scan and each finding's disposition | ||||
| Hook gate: blocked and allowed change |
Explain any difference between expected and observed results. Include the mutation configuration and result, the evaluation denominator and inputs, and the scan scope.
README check
Link the README. Run its setup, usage and verification commands against the final revision, or mark a command as unavailable with the reason and next check.
AI-use note
State the tool and purpose, or state that no AI was used. Reuse the existing note ID.
Submission and decision
List the submitted artifacts and their links. Record the decision: accept, narrow, re-check or stop, with the evidence supporting it.
Review
Read the final diff against the specification. Confirm that tests, mutation results, evaluation, security disposition and README commands identify their revision and can be reproduced. Note unresolved risks and the check that would address each one.