Fallback checklist

Use this checklist if you cannot activate the supplied agent access, obtain the course materials or run an exercise. Follow the safety practices in Week 0 setup.

1. Agent access is missing. Contact the teaching team through the course's published support channel. Do not buy a subscription or API credit to make up for missing course access. While waiting, predict the outputs of the primer's supplied candidate, repair it manually and label your work as manual. This keeps learning moving; it does not count as a real coding-agent session when an assignment explicitly requires one.
2. A command or dependency fails. Keep the command, expected result and a short, inspected error excerpt. Check the exercise's prerequisites and ask for help. Record the operation as not executed until you can run it; do not invent output.
3. You cannot establish the required workspace or network boundary. Stop execution. Trace the primer's checks on paper and mark them as reasoning, then request a supported environment. Do not grant wider permissions to get past the problem.
4. An account, device or accessibility barrier prevents participation. Ask the teaching team for supported access or an approved equivalent arrangement. Keep the affected work pending; an access failure is not evidence of an incorrect algorithm.

Return to generation and verification when access is restored. Keep waiting, help and rework time in your existing work record so the course can plan support from actual use.