Readiness and Repair

This starting route makes Launchpad usable even when you have never programmed or used a terminal. It checks specific skills; it does not rank your ability or predict whether you belong in computing.

How to use this route

1. Attempt the diagnostic before studying its solutions. Allow roughly one hour, with breaks and accessibility tools as needed. There is no speed cutoff.
2. Keep your work, then use the separate answer key to identify gaps by domain. Do not average the domains together.
3. Study only the repair lessons you need: computer basics, arithmetic and units, algebra, or technical reading and help.
4. Use the fresh reassessment. Record the result, evidence and next action using the readiness record.

Progression gates

Before Semester 00 Programming Basics: demonstrate all four computer tasks, all four arithmetic tasks and all three technical-reading tasks. Ordinary documentation is allowed for computer operations and documentation lookup. Explain arithmetic reasoning before checking with a calculator. If a task is missed, repair that domain and demonstrate a fresh variant; there is no required repeat of already-demonstrated domains.

Before Semester 01 Mathematics: additionally demonstrate all four algebra tasks and the Semester 00 mathematical-notation bridge. Algebra repair may run alongside Semester 00. A weak algebra result does not block the first programming lessons once the earlier gate is met.

Launchpad's existing modules still apply: this route supplements study systems, developer tooling and Git. It does not establish terminal or Git competency by itself, and it does not replace the existing project and checkpoint.

Workload and status

Initial diagnostic and record: about 1 hour, already included in Launchpad’s 92–138-hour core allowance. Conditional repairs, including reassessment: computer basics 2–4 hours; arithmetic 3–5; algebra 4–6; technical reading 2–3. All repairs together add 11–18 focused hours. The diagnostic plus those repairs totals 12–19 hours for this readiness route; do not add the diagnostic again to the core allowance. Launchpad with all repairs totals 103–156 hours. These are author estimates awaiting learner pilots; repeat practice may take longer. Do not add every repair to a learner who already demonstrates the skill.

This route is authored and checked for internal consistency; independent teaching review and learner calibration remain pending. Keep evidence private unless deliberately adapting it into a public reflection. No paid resource is required.