// PATTERN B · OPERATIONS DASHBOARD · NOTEBOOK
Notebook Checkpoints
Sprint-aligned engineering notebook milestones. Every bot moves through the same six checkpoints from concept-lock through comp-ready. This page tracks where each bot is in that pipeline and what's blocking the next step.
Last updated: 2026-05-12 · Sprint Week 2 of 42 · Owner: Notebook lead + per-bot Notebook owner
Active bots tracked
4
Skimmer, Pelican, Osprey, Spoonbill
Current checkpoint
CP-2
CAD freeze
On track
3 / 4
bots at CP-2 or ahead
At risk
1
Spoonbill (see grid)
01The six notebook checkpoints
Every bot goes through these six checkpoints, in order. A checkpoint isn't done until its notebook artifacts are filed. Skipping a checkpoint's notebook work guarantees a weaker judge interview later.
-
CP-1 · Concept Lock
The bot's mechanical architecture is committed. No more "what if we tried six-bar instead." The team has picked a path and is going to defend it through CAD.
Notebook artifacts: brainstorm matrix, decision matrix slide (with scoring), 1-2 sketches of the chosen architecture, written rationale (3-5 sentences) for why this picks over the alternatives.
-
CP-2 · CAD Freeze
OnShape model is complete enough that the BOM is final. The team can order parts. Subsequent CAD changes need a written change-order with reason.
Notebook artifacts: isometric + side-view CAD screenshots, BOM table with line items + cost, dimensional analyses for novel parts, variable list showing parametric design intent.
-
CP-3 · First Build Complete
The bot exists physically and can be driven for a 90-second match without falling apart. Doesn't need to score well, just needs to run end-to-end.
Notebook artifacts: build photos (raw + assembled), discrepancies between CAD and physical (always present), first-drive video reference (URL only in notebook), early failure list.
-
CP-4 · Bench Test Pass
Mechanism-by-mechanism, the bot meets the spec on the bench. Intake captures both elements. Lift hits all three goal heights. Drivetrain runs full speed under load.
Notebook artifacts: bench-test protocol (see
/phase-a-bench-tests), pass/fail per protocol, repair log if anything failed and was fixed, retest signoff.
-
CP-5 · Field Test Pass
Driver-controlled match cycles on a real (or rebuilt) field. AWP-eligible autonomous routines run successfully 80%+ of the time. Match-cycle timings hit targets.
Notebook artifacts: field test logs with cycle timings, auton routine specs + pass rates, driver-noted failure modes, design-of-experiments table if comparing two configurations.
-
CP-6 · Comp Ready
Bot has passed inspection rehearsal. Notebook is event-ready. Interview team has rehearsed. T-14 day of comp prep checklist begins.
Notebook artifacts: R1-R30 inspection-readiness signoff, judge-interview prep notes, event packing list (engineer-owned), printed notebook draft.
02Per-bot checkpoint status
At-a-glance: where is each bot in the pipeline? Color tells the story.
| Bot |
CP-1 Concept |
CP-2 CAD |
CP-3 Build |
CP-4 Bench |
CP-5 Field |
CP-6 Comp |
| Skimmer (2822A) |
DONE |
DONE |
WIP |
TODO |
TODO |
TODO |
| Pelican (2822C) |
DONE |
DONE |
DONE |
WIP |
TODO |
TODO |
| Osprey (2822E) |
DONE |
DONE |
DONE |
WIP |
TODO |
TODO |
| Spoonbill (2822B) |
DONE |
WIP |
TODO |
TODO |
TODO |
TODO |
| Heron / Crane / Stork / Falcon |
CONCEPT |
— |
— |
— |
— |
— |
Legend: DONE = notebook artifacts filed · WIP = mechanically in progress · TODO = not started · CONCEPT = concept fleet, not yet active · — = N/A
At-risk callout for Spoonbill (2822B): CP-2 (CAD freeze) is WIP but sliding behind the other bots. Decision needed by 2026-05-20: keep building or move team to a different concept bot (Heron / Crane). Tracked in
/season-hq as decision item.
03Notebook submission queue (this week)
Notebook artifacts due this week. Each item maps to a checkpoint above.
| Artifact |
Bot |
Checkpoint |
Owner |
Due |
Status |
| BOM table with cost |
Spoonbill |
CP-2 CAD |
Engineer-B + Notebook |
2026-05-15 |
IN PROGRESS |
| Bench-test protocol pass entries |
Skimmer, Pelican, Osprey |
CP-4 Bench |
Notebook (each bot's owner) |
2026-05-16 |
IN PROGRESS |
| First-build photos + discrepancy log |
Pelican |
CP-3 Build (retroactive) |
Notebook-C |
2026-05-14 |
PHOTOS TAKEN |
| Decision matrix update (Override mid-season) |
Cross-fleet |
CP-1 retrospective |
Strategist + Notebook lead |
2026-05-19 |
READY |
04Judging criteria mapping
Which checkpoints feed which judging criteria. Use this to spot-check before each event: does the notebook show all this evidence?
| Judging criterion |
Primary checkpoint source |
Secondary source |
| Engineering Design Process (EDP) |
CP-1 (brainstorm + decision matrix) |
CP-4, CP-5 (iteration cycles) |
| Mechanical excellence |
CP-2 (CAD + dimensional analysis) |
CP-3 (build quality photos) |
| Programming sophistication |
CP-5 (auton routine specs) |
CP-4 (sensor calibration entries) |
| Innovation |
CP-1 (decision matrix — why this over the obvious choice) |
CP-2 (novel CAD approaches) |
| Documentation quality |
All CPs (consistency, completeness, dated entries) |
CP-6 (final binding) |
| Iteration / improvement |
CP-4 → CP-5 (bench → field rebuild loop) |
match-analysis (post-event) |
| Team awards (Excellence) |
All CPs combined; plus interview rehearsals |
mission-control readiness |
05Workflow
How an artifact moves from happening-in-the-shop to filed-in-the-notebook:
- Event happens (CAD freeze meeting, first build, bench test) → whoever's there captures raw data: photos, notes, timings.
- Within 48 hours → the bot's Notebook owner converts raw data into the notebook entry per the template in /notebook-operations.
- Notebook lead reviews → spot-checks EDP coverage and writing quality.
- Entry filed → the corresponding cell in the per-bot grid (section 02) flips to DONE.
- Coach signs off on full checkpoint completion when all the checkpoint's artifacts are filed AND the bot has visibly moved past that stage mechanically.
Anti-pattern to avoid: "we'll backfill the notebook before the event." Notebook entries written from memory two weeks after the work happened are obviously worse than entries written within 48 hours. Judges can tell. The checkpoint grid exists to prevent backfill mode.
06For general notebook pedagogy