<!-- YYYY-MM-DD-[TeamID]-SprintNote.md -->

# Sprint Note: Sprint [N], [Team Name]

<!-- One page maximum. Each numbered section is graded pass/fail (20 points each).
     The evidence may be AI-generated from your repo history and board.
     Two things must be human-written: section 5, and the "shipped" sentence
     in each contribution line. Those are the parts anyone reads. -->

**Team:** | **Sprint dates:** | **Date submitted:**

## 1. Working Software Evidence

A URL, tagged release, or demo video link, plus a link to the CI run. If nothing works yet, say so plainly and say why.
For a sprint with no live demo slot, the video is one file, timestamped, one segment per student.

- Deployed URL / release tag / demo video:
- Video timestamps (one per student), if applicable:
- CI run:

## 2. What Got Done

Everything the team finished this sprint. Each item concrete (someone could go look at it) and consequential
(the project is meaningfully further along). It does not have to be code; non-code work counts when it landed in the repository as a written PR someone can open. Activity without a result does not
belong here: "worked on the API" and "researched options" are not done things.

- Board link:
- Done this sprint:
-
-

## 3. Top Risk and One Decision Needed

The single biggest threat to your Definition of Shipped, and one concrete decision the team needs from the partner, the staff, or itself.

- Top risk:
- Decision needed (from whom, by when):

## 4. Contribution Lines

One line per student, three parts:
  (a) the PR(s) you owned this sprint, by title or ID (NDA teams: IDs only);
  (b) whose work you reviewed and the one change you asked for, named specifically ("LGTM" is not a review);
  (c) one human-written sentence: the most consequential thing you shipped, and how the team knows it works.
If a student has no PR this sprint, say why on their line. Mechanical changes (formatter runs, lockfile bumps,
generated files, bulk renames) are normal work but are not evidence; leave them out.

**[Student 1]**
- owned:
- reviewed:
- shipped:

**[Student 2]**
- owned:
- reviewed:
- shipped:

**[Student 3]**
- owned:
- reviewed:
- shipped:

**[Student 4]**
- owned:
- reviewed:
- shipped:

**Decision chaired this sprint:** who drove which decision to a conclusion. Over a term everyone should appear here at least once.

-

## 5. Judgment Layer (human-written, about five lines)

What the team learned this sprint and what it changes about the plan. Not a status recap: the insight, the surprise, the course correction.