Pre-Semester Project: Foundation Setup Portfolio
Build one inspectable learning workspace from the work you already completed. Its audience is you returning after a break, or someone checking your evidence. It prepares you for Semester 00; it does not certify later-degree or professional competence.
Scope and workload
Module practice produces the artifacts. Within the existing integration allowance, use 4–7 hours for assembly, clean setup and exam-fixture preparation. Link original files instead of repeating labs. The remaining integration time covers cumulative review, checkpoint, practical exam and bounded repair; see the workload contract.
Keep the packet private if preferred. A local folder and Git repository are sufficient. Public hosting, a second computer, a real collaborator, automation installers, comprehensive dotfiles and speed improvements are optional. No book purchase, Python program or personality/habit-system agreement is required.
Required packet
1. Study and recovery record
Link one feasible calendar, an observable learning outcome and a start/access plan. Preserve two actual sessions on separate occasions, with intended versus actual work, help received and a learning check. Use the same observations for SS2 and S2; do not count their underlying technical practice twice.
Include one planning-cycle review: what the observations support, what you will change or keep, and why. Add a recovery decision from an actual interruption or a clearly labeled rehearsal. An invented session cannot replace an observation. There is no fixed weekly deadline, daily streak, health disclosure or required cue/craving analysis.
Acceptance: SS1–SS3 and S1–S3 each reach 2/2 under their module criteria. An honest failed technical check can support study-process evidence, but the technical repair remains open.
2. Small reproducible environment
Link your OS/shell/editor description, setup README, isolated configuration fixture and reconstruction checklist from Module 2. Include the shell path/stream/exit-status checks, saved editor change, configuration reload/removal evidence and required process-control work. A transcript or accessible text explanation with observed outputs is acceptable; screenshots are not mandatory.
Inspect the configuration in a clean child shell as taught; do not replace your personal startup files. Identify which settings are session-only and which are saved. Record any platform-specific limitation. Track the prepared harmless configuration and checklist during Module 3.
Acceptance: Module 2 quiz at least 18/20, plus every required practical outcome in its beginner route. A custom alias collection or an elaborate installer is not a substitute.
3. Reviewable Git work
Link the actual local repository/history and evidence for working/staged/committed versions, selective staging, ignored files, branches, an actual merge conflict, recovery and local synchronization. Keep the explanation of what each operation changed. Preserve original proposal, specific review feedback and corrected version. A local solo rehearsal is valid when labeled; it cannot be described as another person's review.
Acceptance: Module 3 quiz at least 21/23, plus every required practical outcome in its beginner route. Hosted pull requests, force pushing, leaked-secret incidents and outside maintainers are not requirements.
4. Preparation evidence
Link existing records for R1–R3, C1–C3, DS1–DS3 and AL1–AL3. Include the passage/source trail and claim audit; explanation, focused question and visible revision; saved-state/trust reasoning and actual content-checked restore with an incomplete negative control; and AI initial attempt, candidate audit and fresh transfer. Label offline authored candidates, generated assistance and independent work accurately. Each dimension must reach 2/2; a group average cannot hide a missing skill.
5. Assessment and handoff index
Use the shared record or your existing equivalent. Link readiness results, module gates, cumulative review, all 15 checkpoint answers, criterion-level exam scores, repairs and assistance. Include one next permitted action and any deferred algebra work. The bridge review explains the transition; Python installation belongs to Programming Basics, not an added Launchpad prerequisite.
Assemble and inspect
- Gather existing artifacts and label actual observations, simulated scenarios and pending evidence.
- Check that each link opens and that another person could locate the relevant version. Reconstruct the small configuration fixture in isolation, retaining any failed check and repair.
- Explain one decision using alternatives and a constraint: for example, a same-device copy is convenient for this practice but cannot establish device-loss recovery.
- Complete the cumulative review, checkpoint and exam. Update this same index after targeted repairs. Do not generate another portfolio or repeat all module assessments.
Acceptance and calibration
The project is complete / repair required / pending observation, not a new weighted exam. All five packet sections must be inspectable and explainable. The earlier component percentages are not extra advancement gates. Use the rubric and all progression conditions together.
A tidy folder with no restore check is incomplete. A technically correct packet with imagined study sessions remains pending. A modest local packet with real evidence and labeled solo review can satisfy this project. Extra features do not offset missing core work.
After preserving your own attempt, inspect the author example packet for the expected level of detail. Its illustrations and technical fixtures are not learner submissions or proof of your competence.