Semester 8 Checkpoint Gate
Required Output Classification
| Required output | Classification | Public/private guidance |
|---|---|---|
| Closed-book prompts, self-assessment answers, and skills matrices | Practice artifact | Use for honest calibration; do not publish raw answers unless rewritten as a study guide. |
| Required evidence gate items, sign-off checklist, and readiness decision | Checkpoint evidence | Keep as private progression evidence; share only sanitized summaries with mentors or reviewers. |
| Repair artifacts produced after a weak checkpoint, such as corrected solutions, diagrams, traces, benchmarks, or runbooks | Checkpoint evidence | Store beside the checkpoint so the remediation trail is inspectable without making mistakes public. |
| Reviewer notes or mentor feedback that materially improve a project artifact | Portfolio candidate | Convert into public-safe acknowledgements or changelog entries only after removing private feedback context. |
Self-assessment before Semester 9 (Cloud, DevOps, and Production Operations). The skills below are the floor, not the ceiling. Answer honestly and remediate every "N" before starting the next semester -- this gate is the point where being a strong implementer stops being enough.
Skills Verification Matrix
| Skill | Can you do this without looking it up? | Evidence (link / note) | Pass (Y/N) |
|---|---|---|---|
| Facilitate a 45-minute design discussion on an unfamiliar prompt: frame requirements, estimate, reach a stress-tested high-level design, and name explicit tradeoffs. | |||
| Take a rough feature description for a monolith and produce a service-decomposition sketch with boundaries, data ownership, a publishable contract, and at least one ADR naming the rejected alternative. | |||
| Walk a trip-lifecycle-style event flow end to end, including at least one saga with compensating actions, and name the failure modes that are easier and harder than the synchronous version. | |||
| Read a P99 latency chart and a utilization dashboard, form a hypothesis about the bottleneck, and state the capacity or scaling action you would take -- with numbers, not adjectives. | |||
| Draft a one-page engineering strategy memo using diagnosis / guiding policy / coherent action, and an ADR for a concrete decision in your own project, without looking up the templates. |
Explain-From-Memory Prompts
- In under five minutes and without notes, walk a teammate through the main diagram of your RideHail Dispatch design doc: the services, the data each one owns, the hot-path flow, and the place most likely to fail first under 10x load.
- State three failure modes of your design, the user-visible effect of each, and the mitigation you chose -- including one mitigation you deliberately did not take, and why.
Remediation Plan
If any row above is "N", name the specific module, readings, or artifact to redo. The remediation is always an artifact you produce (design, ADR, memo, estimate), not just a chapter you re-read.
| Gap | Remediation |
|---|---|
| Cannot frame and estimate an unfamiliar prompt in 10 minutes with numbers | Redo Module 1, Clusters 1-2. Produce two fresh framing artifacts and estimation sheets on prompts you have not seen before; time yourself. |
Sign-Off
- Date completed: Fill in once every row above is "Y" and the explain-from-memory prompts have been answered aloud to a partner or recorded.
- Ready for Semester 9: Y/N -- record the answer as a single sentence that names the weakest area you are still carrying in, so the Semester 9 plan can start from that reality rather than assume a clean slate.
Mastery Rubric
| Level | Evidence |
|---|---|
| Beginner pass | Can answer direct questions and complete familiar exercises with light notes. |
| Solid pass | Can solve new variants, explain choices, and connect the work to Semester 7 Architecture and DDD. |
| Strong pass | Can defend tradeoffs, identify failure modes, and produce clean evidence in the portfolio artifact. |
| Not ready | Relies on copied solutions, cannot explain mistakes, or lacks durable artifacts. |
Retake and Repair Rule
If a section is weak, do not only reread. Repair it by producing new evidence: a corrected solution, a fresh implementation, a rewritten proof, a benchmark, a diagram, a runbook, or a short teaching note.
Answer-Quality Examples
Use these examples when grading written answers or spoken explanations.
| Quality | Example pattern |
|---|---|
| Weak | Names a concept but gives no example, constraint, or failure case. |
| Acceptable | Defines the concept and applies it to a familiar exercise. |
| Strong | Applies the concept to a new variant and explains why an alternative would fail. |
| Portfolio-ready | Connects the concept to Semester 7 Architecture and DDD, current project evidence, and a future capstone decision. |
Interleaving Prompt
For any missed answer, add one sentence starting with: This depends on an earlier skill because...
Calibration Materials
Use these learner-visible calibration materials before self-grading or requesting review: