Bridge Review: Semester 3 Software Design -> Systems Programming -> Semester 5 Operating Systems and Networking
Required Output Classification
| Required output | Classification | Public/private guidance |
|---|---|---|
| Incoming-dependency notes and bridge self-checks | Practice artifact | Keep as working notes unless rewritten into a reusable study guide. |
| Integration task response and forward-bridge plan | Checkpoint evidence | Store as private readiness evidence that shows why you are prepared for the next semester. |
| Any refined diagram, ADR, runbook excerpt, benchmark summary, or capstone thread pulled from the bridge review | Portfolio candidate | Polish and sanitize before publishing; keep raw bridge reasoning private if it exposes weak areas or coursework-only context. |
This review connects the current semester to the roadmap around it. Complete it after the cumulative review and before starting the next semester.
Incoming Dependencies
From Semester 3 Software Design, identify the skills that were required for this semester. For each one, write one example of where it appeared in real work.
Current Semester Spine
The ideas that should now be active:
- memory model
- process model
- debugging evidence
- performance measurement
For each item, write:
- one definition in your own words
- one example from this semester's artifact
- one mistake or edge case that clarified the idea
Forward Bridge
Before entering Semester 5 Operating Systems and Networking, answer:
- What will the next semester assume you can do without warm-up?
- Which current artifact can become input for the next semester?
- Which weak area would create the most friction if ignored?
- What spaced-repetition cards or drills should stay active for four more weeks?
Integration Task
Write a one-page memo titled How Systems Programming changes the way I approach Semester 5 Operating Systems and Networking.
The memo must include:
- one concept carried forward
- one concrete artifact link or path
- one tradeoff you understand better now
- one question you expect the next semester to answer
C input-contract evidence
Require all CI1–CI6 at level 2 or above. Reuse the line-reader lab packet in the existing project: capacity traces, consecutive-line behavior, injected errors, compiler/diagnostic output and a fresh-case defense. No aggregate score waives missing input-contract evidence. Preserve the distinction between bounded storage and bounded running time.
Memory ownership evidence
Require all MP1–MP6 at level 2 or above. Reuse the growable-buffer packet: checked sizing, ownership traces, allocation-failure recovery, cleanup and independent transfer. The 20–30-hour package replaces the former short lab; it is not a complete module workload. Required fuzzing/Rust/mitigation/platform work remains separate.
Performance evidence
Require PE1–PE6 at level 2 or above. Reuse the locality measurement packet: checked sums, raw timings, target assembly, model assumptions and a bounded inference. A speedup or fabricated anomaly is never required. The specialized-platform strand remains separate.
Partial-I/O evidence
Require IO1–IO6 at level 2 or above. Reuse the write-progress packet: exact accepted prefixes, bounded retry traces, descriptor ownership and diagnostic evidence. A complete local write does not imply durability or remote processing.
Lexical interpretation evidence
Require all LI1–LI6 at level 2 or above. Reuse the interpreter packet: frame diagrams, two independent closure instances, evaluation-order tests, caller-scope fault evidence and explicit host/resource limitations. The small evaluator does not replace the original mutation, streams, staging or concurrency requirements. A failed gate remains incomplete regardless of aggregate score.
Integrated progression contract
Use the 440–640-hour workload and advancement contract. All 30 module extension gates and all five safety/platform evidence categories must independently reach level 2, alongside existing checkpoint, exam, project and integrity thresholds. Missing evidence means repair required — incomplete. Reuse module artifacts and record time once; the three-hour written exam and two-hour fresh-case defense are included in integration time.
Preparation for native parallel work
Carry C lifetime, bounded input, pthread create/join and locality evidence into the Semester 05 parallel-work clinic. It adds native partitioning, reduction and measurement work in Semester 05; no extra Semester 04 workload is assigned. Existing native safety/platform gates remain required.