Skip to content

Course project pull request template

Explain gate

What changed?

TODO

(One paragraph: what behavior does this PR add, remove or change? Link the related spec or issue.)

Why?

TODO

(Explain the reasoning: why this approach over another, and which assumptions it depends on. Write it so that a reader who has not seen the code can follow it. Give an approved model enough context to review this diff in a fresh context. Mark each finding confirmed, refuted or cannot tell with your own evidence and record it under ## Review evidence below; if model review is unavailable, ask a TA.)

Which inputs are most likely to fail?

TODO

(List 2-3 boundary or adversarial inputs and how you expect them to behave.)

What did you personally verify?

TODO

(Tests, commands or manual checks you personally ran; agent-generated verification does not count.)

Complete when permissions or data change

  • Assets, trust boundaries, likely abuse or failure paths and mitigations (omit if not applicable):
  • Data categories, PII/key risks, redaction, access and retention (omit if not applicable):

Review evidence

  • Approved model review (fresh context) or TA review, review scope and evidence links:
  • Your outcome for each finding (confirmed, refuted or cannot tell) and its evidence; for cannot tell, what is missing:
  • Unresolved risks and open questions:

Respond to review feedback in the existing thread and reference revisions and re-verification results; no separate feedback form is required. Student PRs do not contain teacher pilot, hint-ladder or teaching-design records.

AI-use note

Reference the existing description and evidence ID for this assignment or milestone. Update that same description only when the purpose changes; do not repeat disclosure. Submit detailed trajectories according to the assignment or milestone's learning objectives; per-commit Assisted-by trailers are optional.