BEGINNER PILOT - PRIVATE PROGRESS RECORD
Leave results blank until observed. Blank does not mean zero or pass.
Status: not started / active / repair needed / pending observation / demonstrated.
Use pending observation when a scheduled observation or delayed check has not occurred.
Keep self-assessment versus independent review separate from task status.

BASELINE
Start date:
Curriculum version or saved page snapshot/date:
Prior programming, terminal and Git experience:
Available focused hours per week:
Relevant OS / shell / editor / Python version (when installed):
Optional access/workflow adjustments (no personal disclosure required):
Evidence folder or private index:
Reviewer: self / independent (scope and date if applicable):
Current route stage and next action:

SESSION - repeat this block for actual sessions
Session ID / date / page and task:
Prediction or intended result before execution/answer reveal:
First independent attempt and evidence location:
Observed result and explanation:
Help: none / documentation / human hint / generated material (describe):
Active minutes: reading __ / practice __ / investigation __ / assessment __
Active minutes: repair __ / record and review __
Waiting time separately:
Unclear instruction or missing prerequisite:
Evidence reused for other dimensions (do not count time twice):
Next smallest action:

READINESS - score domains independently, preserve first and fresh attempts
A computer basics: __/4; status __; evidence __
B arithmetic and units: __/4; status __; evidence __
C algebra: __/4; status __; evidence __; deferred repair plan __
D technical reading: __/3; status __; evidence __
Missed items, repair and fresh reassessment links:
Optional readiness follow-up date/result:

LAUNCHPAD EVIDENCE INDEX - record each dimension separately, not a group total
Study systems: SS1 __/2; SS2 __/2; SS3 __/2; status/evidence __
Reading: R1 __/2; R2 __/2; R3 __/2; status/evidence __
Communication: C1 __/2; C2 __/2; C3 __/2; status/evidence __
Sustainable study: S1 __/2; S2 __/2; S3 __/2; status/evidence __
Digital systems: DS1 __/2; DS2 __/2; DS3 __/2; status/evidence __
AI learning: AL1 __/2; AL2 __/2; AL3 __/2; status/evidence __
One calendar and two actual session IDs/dates:
Study review/revision and actual or simulated interruption recovery:
Environment quiz __/20 (at least 18); all required practical checks __; evidence __
Git quiz __/23 (at least 21); all required practical checks __; evidence __
Collaboration evidence type: actual feedback / labeled local rehearsal:
Source audit and explanation/help/revision links:
Actual restored file, content check and limits:
AI initial attempt, candidate audit, fresh transfer and assistance:
Required practice completion and open repairs:
Foundation project required artifacts: status __; index __
Cumulative review: status __; evidence __
Checkpoint prompt scores (each 0 or 1):
1 __; 2 __; 3 __; 4 __; 5 __; 6 __; 7 __; 8 __; 9 __; 10 __;
11 __; 12 __; 13 __; 14 __; 15 __
Checkpoint: __/15 (at least 12); independent evidence/reasons __; critical gaps __
Exam criterion-level scores and explanations link:
Exam normalized section percentages: A __; B __; C __; D __
Exam weighted total = 0.25*A + 0.35*B + 0.25*C + 0.15*D: __%
Exam: total >=75 AND every section >=70; assess before rounding: __
Launchpad decision: pending / repair / provisionally demonstrated:
All gates checked, including each dimension at 2 and checkpoint >=12/15 and Module 2/3 quiz plus practical gates:
Next permitted step and any algebra dependency before Semester 01:

PROGRAMMING BASICS - immediate results do not close delayed evidence
Entry file-navigation/arithmetic check:
Python preflight: OS/shell __; command/version __; setup repair if needed __
First saved script prediction, execution and explanation:
Project, tests, debugging note and assistance links:
Original reading-page transfer and first-over-budget clinic links:
Immediate Behavior __/2; Testing __/2; Explanation __/2; Evidence __/2
Immediate Transfer evidence __/2; delayed Transfer evidence status __
Immediate requirements decision and open repairs:
Reviewer: self / independent; reviewed scope/date:
Anchor date = first demonstration of all immediate requirements:
About +7 days: planned __; actual __; actual interval __ days
Package-capacity attempt, explanation, tests and help:
Result / repair / fresh reassessment link:
About +28 days from SAME anchor: planned __; actual __; interval __ days
Changed-reading-rule attempt, explanation, tests and help:
Result / repair / fresh reassessment link:
Final rubric: Behavior __/2; Testing __/2; Explanation __/2;
Transfer __/2 (including delayed checks); Evidence __/2
Final programming readiness: pending / repair / demonstrated:
Do not mark final 10/10 while delayed checks or repairs remain open.

ISSUE AND RETEST - repeat only when useful
Page/task and version:
Expected versus actual behavior; smallest reproduction:
Relevant environment and help (redact secrets):
Possible cause / evidence for or against it:
Instruction or prerequisite repair; new version/date:
Fresh retest evidence and remaining uncertainty:

REVIEW - update at stage boundaries
Actual focused hours by module; separate extra repair and optional work:
Observed difficulty versus estimate (one learner, not a general average):
Demonstrated / open / not-yet-due requirements:
Evidence limits: author check / self-assessment / independent review:
Next permitted action and scheduled follow-up: