Final Checkpoint -- Degree-Level Readiness
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. |
This is the graduation gate. It is a structured, self-administered go/no-go review of the whole degree, anchored against the capstone you shipped in Capstone Project and the modules of Semester 10. You do not pass this gate because the capstone compiles; you pass it because you can point to specific evidence across six readiness dimensions, answer stress-test questions cold, and know exactly what remains if you are not yet ready.
Entry criteria (all must be true before you start this gate):
- Checkpoints for Semesters 0-9 are all marked passed in their respective
checkpoint.mdfiles. - The capstone repository is merged to
mainand the deploy pipeline is green on the latest commit. - Modules 1-5 of Semester 10 are each marked complete, with their completion-standard criteria honestly met.
- The final exam in Final Exam & Feynman Challenge has been attempted and self-graded at least at the Pass band.
- The degree cumulative review in Semester 10 Cumulative Review has been completed and weak areas carried into Anki.
If any entry criterion is not met, do not start this gate -- finish the missing item first. Running this gate with incomplete entry criteria produces a false pass and you will feel it in the defense.
Evaluation artifacts you must have on hand (print, pin, or tab them open before you start):
- the capstone repository URL
- the deployed environment URL, or a recorded demo video if the deploy is paused for cost
- the set of ADRs (at least three)
- the deployment runbook and at least one operational-scenario walkthrough
- the capstone design doc and C4 diagram set
- the portfolio page with the capstone case study
- the 12-month specialization plan from Module 5
Readiness Dimensions
For each dimension, write the concrete evidence in one line and mark Y/N. A single N means you are not yet ready to graduate; follow the remediation path below.
| Dimension | Evidence you can point to | Met? (Y/N) |
|---|---|---|
| Build | A non-trivial system you shipped end-to-end: repo link, working deploy, vertical slice demoable in under five minutes, test pyramid present. The capstone itself -- not a prior-semester project -- is the evidence. | |
| Design | At least three ADRs with context / decision / alternatives / consequences; the capstone design doc (4-8 pages); the C4 diagram set (Context, Container, Component); one fitness function running in CI. You can narrate any ADR from memory. | |
| Operate | Deployment runbook rehearsed with a timer; at least one SLO with a numeric target and a dashboard backing it; at least one alert with a written rationale; one operational scenario (bad deploy, dependency outage, or forced failure) walked through in writing. An on-call mindset, not just logs existing. | |
| Secure | One-page threat model (STRIDE or similar) with realistic threats and mitigations; dependency scan clean or exceptions documented; secrets out of the repo and in a real secrets store; IAM least-privilege for the deploy role; OIDC in CI rather than long-lived keys. | |
| Collaborate | README orients a new reader in under five minutes; commit messages and PR descriptions are review-quality; the capstone case study in the portfolio is written in a voice you would show an engineer you respect; Feynman notes cover your weakest five degree topics. | |
| Learn | A visible habit of closing gaps when stuck: journal entries show specific "I was blocked on X, I read Y, I now understand Z" moves; Anki reviews have been consistent for at least the last four weeks; you can name today the one topic you were worst at in Semester 3 and how you have since fixed it. |
Stress-Test Questions (No Notes)
Answer all three aloud (or in writing), without referencing your repo, design doc, or notes. Pass requires a confident answer in under three minutes each. These are the written form of what a sharp reviewer will ask in the defense.
- Failure and rollback under pressure. "Your capstone went live this morning. Thirty minutes in, error rate jumps from baseline to 4%. Walk me through exactly what you do in the next fifteen minutes -- detection, decision, rollback trigger, comms, verification, and the single line you write in the runbook afterwards. Now change one thing: the bad deploy also included a non-backward-compatible database migration. What changes in your answer?"
- Scope discipline under deadline. "You have one week less than you had. Which of the six mandatory capabilities would you cut first, second, and third, and what specifically would you protect at all costs? Use the scope-cut rules you wrote in Module 1 -- did you actually follow them, or did you rationalize around them? Name one time you did each."
- Architectural defensibility. "Pick any ADR from your set. Argue against your own decision as persuasively as you can -- give the best case for the rejected alternative. Then argue back. Does the ADR survive? If yes, you understand the decision; if no, you need to rewrite it before you graduate. Which ADR did you pick, and why that one?"
Add a fourth question for yourself if one of the first three felt too easy: the point of this section is to find the weakest joint in your understanding before a reviewer does.
External Bar (Optional)
A purely-internal review is powerful but can drift into self-flattery. Before calling yourself production-ready, pick at least one external bar and pass it:
- a mock system-design interview with a working engineer (60-90 minutes, novel scenario, their feedback written down)
- a code/architecture review of your capstone by a peer or mentor, with their comments addressed or explicitly declined in a reply
- a recorded 10-minute defense shown to someone you respect, followed by 15 minutes of hostile questions
- a written mentor sign-off: one paragraph from a senior engineer confirming that the capstone and its documentation hold up to scrutiny
Record which bar you picked, who the reviewer was, and the single piece of feedback you found most uncomfortable. That feedback is the most valuable artifact of this section.
Remediation
If any Readiness Dimension is "N", or any Stress-Test question could not be answered in under three minutes, you are not yet ready. That is not a failure -- it is the gate doing its job. Before graduating, close the gap with the plan below. Do not re-run the gate until the plan is complete.
| Gap | Plan |
|---|---|
| A Readiness Dimension is marked N | Re-open the corresponding Semester 10 module: Build -> Module 2, Design -> Module 1, Operate -> Module 4, Secure -> Module 4, Collaborate -> Module 5, Learn -> revisit the relevant prior-semester cumulative review. Produce one new concrete artifact that would flip the answer to Y, and log it in this table before re-checking. |
| A Stress-Test question could not be answered cold | Write the full answer as a new Feynman note, rehearse it aloud twice, wait 48 hours, and re-attempt closed-book. If it still fails, the underlying concept -- not the question -- is the gap; find the semester that owns it and re-run that semester's exam. |
| Entry criterion unmet (e.g., checkpoint N-1 failed in hindsight, exam self-graded below Pass) | Fix the upstream item before anything else. A shaky S7 checkpoint or a below-Pass exam is a structural problem; patching it at S10 is cheaper than letting it surface in the defense. |
Added Capstone Evidence Gate
Before sign-off, confirm the capstone includes:
- tests at multiple levels and a documented quality gate
- deployed environment evidence and rollback rehearsal
- architecture notes, at least three ADRs, and a current diagram
- runbook, SLO or health target, and observability screenshot
- security review covering secrets, dependencies, permissions, and data handling
- portfolio narrative with screenshots, diagrams, tradeoffs, ethics/accountability note, and known limitations
Sign-Off
Complete this only after every Readiness Dimension is Y and every Stress-Test question has been answered cold.
- Date completed: the date you attempted this gate with all entry criteria met, in
YYYY-MM-DD. - Statement: one paragraph, in your own voice, answering: Am I comfortable calling myself production-ready at the scope of this degree? A strong statement names the one area you are still weakest in, the one area you are strongest in, what you would say if asked "are you a software engineer?" at a dinner party, and what your first concrete action is in the 12-month specialization plan. A weak statement asserts readiness without naming any weakness -- if yours reads that way, re-read the Readiness Dimensions and be honest.
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 9 Cloud and DevOps. |
| 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 9 Cloud and DevOps, 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: