V5RC Override 26—27 · Notebook Rubric v2.0 — 64 pts

Notebook Standard

The official rubric, criterion by criterion, with the bar for a 4 and the concrete things that have to be on our pages to clear it. Score it honestly, check off what's done, and the page totals it.

— / 64

unscored

0 of 0 checklist items done

Entry templates

what every page type must contain

Use these as the skeleton for each entry. If a block is missing, the page is not finished. Every one of them also carries the page furniture: number, date, writer's signature, section tag.

Every page, no exceptions

organization, 16 pts, is the cheapest to max

Page number, same corner, matching the table of contents exactly.
Date of the work — not the date it was typed up. Ranges (7/26–30/26) are fine for multi-day work.
Signature or initials of whoever wrote the page. If two people wrote it, two signatures.
Section tag so a judge lands in the right rubric category without reading the body.
A title that matches its table-of-contents line word for word.

Tag map

our EDP steps → the rubric a judge is holding

The v2.0 rubric names four design-process categories. Our page tags come from our six-step process. This is how they line up — label pages so the judge never has to make the translation themselves.

Our page tag	Rubric section	Criteria it feeds
Identify the Problem	Define	B1 criteria & constraints, B2 strategy
Brainstorm the Solution	Define	B3 brainstorming
Select the Best Solution	Develop Solutions	C4 decisions with evidence
Build the Solution	Develop Solutions + Optimize	C1 prototypes, D1 mechanisms
Program the Solution	Optimize	D2 code
Test the Solution	Develop Solutions	C2 procedures, C3 data
Reflect & Iterate	Reflection and Iteration	E1 reflection, E2 iteration
Team Planning	Organization / Define	A3 season span, B1 external constraints

The three summaries

separate document · not scored · read first

Judges get these alongside the notebook and read them before anything else, so they set the agenda for the interview. They are not scored, but a thin one wastes the only page guaranteed to be read. Check the event page in the Judging section for which ones that event requires and when they are due.

one page

Season Summary

New skills the team learned this season.
Skills that grew — where we were in May versus now.
Robot performance: what it does, what it scores, how it has changed.
Pointers into the notebook — page numbers for every highlight claimed.

one page · skip only if no code

Code Summary

What the code does, in plain language a non-programmer follows.
The order it runs in — init, auton selection, auton, driver control.
How decisions get made: sensor thresholds, PID, the auton selector.
Where each piece lives — one line per file, so a judge can follow the repo.

one page · split in two

Credit Summary

Part one: sources that are physically on the robot or in the code — team designs we built from, libraries, templates, tutorials.
Part two: sources used in the notebook only — research, event data, reference images, scouting feeds.
Each named well enough to find again: team number, video title and channel, event, URL, library and version.
Matches the in-line credits on the pages themselves — nothing in one that is missing from the other.

Pre-event audit

run two weeks out, then again the night before

Shared with the team like everything else. Clear it after each event and run it again.