Skip to main content

Launchpad Workload and Progression

Plan 92–138 focused hours before conditional repairs. These are author planning estimates, not measured beginner completion times. The old three-week arc describes sequence, not a deadline. At 10 focused hours/week, plan roughly 10–14 weeks; at 20, 5–7. Actual practice, accessibility needs and waiting for a collaborator can extend elapsed time.

Non-overlapping allocation​

  • Initial readiness diagnostic and record: 1 hour.
  • Study systems: 15–22 hours — lessons/selective reading 4–6; process design/observation analysis 5–7; retrieval/review 3–5; assessment and repair 3–4. Require SS1–SS3; the optional extended observation route adds time. Reuse Module 6 observations and charge underlying technical tasks only to their original modules.
  • Development environment: 18–26 hours, including shell/editor practice, file operations, debugging setup problems and module assessment.
  • Git fundamentals: 15–22 hours, including commits, branches, merge/conflict recovery, collaboration practice and module assessment.
  • Reading, Reasoning and Evidence: 6–9 hours — lessons 2–3; claim/passage lab 2–3; assessment and repair 2–3.
  • Communication, Help-Seeking and Feedback: 6–9 hours — lessons 2–3; explanation/review lab 2–3; assessment and repair 2–3.
  • Sustainable Study and Recovery: 5–8 hours — lessons 1–2; plan/observations/recovery lab 2–3; assessment and repair 2–3.
  • Digital Systems, Safety and Recovery: 8–12 hours — lessons 3–4; cluster practice 2–3; restore lab 2–3; assessment and repair 1–2.
  • AI for Learning and Everyday Work: 6–9 hours — lessons 2–3; cluster practice 1–2; candidate-audit lab 2–3; assessment and repair 1.
  • Integration: 12–20 hours — portfolio assembly, clean setup and exam-fixture preparation 4–7; cumulative review 2–3; checkpoint 1–2; practical exam 2; one bounded repair 3–6.

Original modules total 48–70; transferred support adds 17–26; new digital/AI modules add 14–21: all modules total 79–117. Integration adds 12–20; diagnostic adds 1, giving 92–138. The transfer removes the same 17–26 hours from Semester 00. Combined Launchpad plus Semester 00 is 302–447 hours before conditional repair; this reorganization adds only 14–21 new hours. Module practice creates the project evidence. Integration assembles, checks and defends it instead of recreating it. Habit observations can span several calendar weeks; count only active work, not every elapsed hour. Full external books/courses, repeated repairs and optional advanced tooling are outside these estimates.

Conditional repair, counted once​

Use the readiness record. Computer basics: 2–4 hours; arithmetic: 3–5; technical reading: 2–3; algebra: 4–6. These include reassessment. All four add 11–18 hours, giving 103–156 hours if every repair is needed. If only algebra is deferred, record its 4–6 hours once in your overall plan, not in both stages. School-math repair may exceed these provisional ranges.

Readiness computer/arithmetic/reading gates must pass before Semester 00. Algebra can run alongside Semester 00 but must pass before Semester 01. Diagnostic failure means repair in that domain, not exclusion from computing.

One advancement rule​

All conditions must hold:

  1. Computer, arithmetic and technical-reading readiness tasks pass on explainable fresh work.
  2. Study, environment and Git checkpoint evidence is demonstrated; at least 12 of the 15 checkpoint prompts (80%) are correct and independent, with no critical missing skill.
  3. The practical exam meets 75% overall and at least 70% in each of its four sections, preserving its original stricter thresholds and weights (25/35/25/15).
  4. The project contains the required setup, study/recovery and Git/collaboration evidence and can be inspected or reproduced.
  5. SS1–SS3, R1–R3, C1–C3, S1–S3, DS1–DS3 and AL1–AL3 each reach 2/2 under the preparation module criteria, including actual session observations and a content-checked restore.
  6. Module 2 reaches at least 18/20 on its quiz and all required practical checks; Module 3 reaches at least 21/23 and all required practical checks. Inspect their beginner routes; a quiz score alone is insufficient.
  7. Cumulative review is complete; its corrections identify repairs rather than another weighted score.
  8. Assistance is disclosed and required repairs are demonstrated on fresh cases.

Timing labels are practice estimates, not automatic failure cutoffs. Documentation and accessibility tools remain permitted where the assessment allows them; generated answers do not establish independent skill. A conditional pass means repair is still open and does not authorize final advancement. A score cannot compensate for missing recovery or Git competence.

Evidence and calibration​

The shared pilot record provides a blank index for this purpose; it adds no new assessment. Use one index linking readiness results, module work, project, checkpoint, exam section scores, assistance and repairs. Follow the integrated route to reuse the calendar, setup README, source audit and help request. Inspect completed module assessments within the existing checkpoint; do not repeat their full practical exams there. Preserve actual collaborator feedback when required; a second local clone demonstrates mechanics but is not evidence of another person's review. Label self-assessment and independent review separately.

Example: exam sections 80/80/80/60 produce 77% overall (0.25×80 + 0.35×80 + 0.25×80 + 0.15×60). This is repair required, because section D is below 70. Four section scores of 75 meet the numerical exam rule, but missing recovery evidence still blocks advancement.

After each module record reading, practice, assessment and repair time separately. Reforecast from remaining work. Read the rubric, exam and checkpoint with this allocation; estimates do not override outcomes.