Term project alpha and task backlog
Purpose
Use this record for the week 7 alpha. Demonstrate one minimal path from input to outcome and make the remaining work visible and verifiable.
Records
Alpha revision and core path
- Revision:
- Core scenario:
- Run command:
- Observed result:
- Known limitation:
Link the acceptance case, output and any regression result. The alpha must run end to end on synthetic or otherwise permitted data.
Repository instructions and hook gate
- Instruction file path and purpose:
- Hook path and rule:
- A change the hook blocks:
- A valid change the hook permits:
- Commands and observed results for both:
Task backlog
| ID | Remaining task | Evidence of need | Acceptance check | Priority | Owner |
|---|---|---|---|---|---|
| T-__ |
Keep tasks bounded and traceable to the specification. Do not add features without a requirement or evidence that changes the decision.
Verification record
List the revision, commands, test results, mutation configuration and any surviving mutants. Explain what you changed after inspecting a failure.
AI-use note
State the tool and purpose, or state that no AI was used. Reuse the existing note ID.
Review
Confirm that the alpha path is reproducible, the instruction file and hook are active, and every backlog item has an acceptance check. Record the decision: accept, narrow, re-check or stop, with evidence links.