Project scoring and appeals

This page describes the earlier fourteen-week layout and is being rewritten; where it differs, the syllabus applies.

The project is individual: there is no contribution adjustment, and your project score is your own 0–20.

Your ci-dashboard project is scored individually across five milestones: M0 2, M1 6, M2 6, M3 3 and M4 3, for 20 points. The public project rubric defines the evidence, whole- or half-point partial credit and zero-credit boundaries. Your open-source contributions, C1 and C2, are scored with the contributions rubric and use the same review and appeals process.

The teaching team records the score from your submitted revision and evidence IDs. A second calibrated reviewer checks the evidence mapping, arithmetic and boundary decisions. Keep an unresolved or contradictory item pending while it is reviewed; missing future work is not silently turned into zero.

Appeals follow the assessment and appeals process. Submit the revision, evidence IDs, a short explanation of the disputed criterion and the specific check that supports your request. Do not include keys, raw participant material or private code.

The project score is not inferred from code volume, commit count, model-finding count, rankings, awards or oral-defense evidence. M3 measures runnable verification evidence, support for each conclusion, clear uncertainty boundaries and one self-check; the number or severity of model findings does not determine that score.