Final examination & D3: one day, two proofs
420-302-VA · WEEK 13 · FALL 2026

Stage 5 of 6 · The first proof · on paper

Exam day

The final is a paper exam in the room you have worked in all semester, on the system you built with your own hands. Treat it as Week 7's midterm with a larger domain: the same kit, the same craft, one upgrade to the strategy, and the same governing rule, the outline and the announcement that comes with the paper decide every logistical fact.

What governs the paper

The outline governs

Coverage, duration, structure, permitted materials and marking come from the Fall 2026 course outline on Omnivox and the rules announced with the paper, exactly as at the midterm. This hub's review follows the course's own arc, the post-midterm weeks in depth with Week 7 standing for the foundations, and claims nothing beyond that. If an announcement and any page here ever differ, the announcement wins.

The kit and the room

The Week 7 kit, unchanged: pens and a pencil, student ID, and a simple calculator for the arithmetic the equation card practises, unless told otherwise; notes and devices per the usual exam rules announced in class. Arrive with margin, D-221 at 14:30 means seated and settled, not arriving. One addition specific to this day: bring the full bench kit too, packed the night before, because D3's demonstration follows the paper, and the one thing the reset break should not contain is a search for a cable.

Working the paper: the Week 7 craft, plus one upgrade

The craft from Week 7's exam page carries over whole: read the entire paper first (two minutes, and your background memory starts on the later questions early), budget by points at roughly points-to-minutes, answer what you know first, attempt everything, and show the working, because method earns marks even when arithmetic slips. The final-exam upgrade is a habit this hub has been building all week: place the question on the journey before answering it. Nearly every question lives at a hop of the story, and five seconds of "this is the broker, Week 9, retained semantics" retrieves the right neighbourhood of facts before you write, the way the equation map gives each formula an address. Questions that resist placement are usually method questions, Week 12's territory: integration order, half-splitting, services.

Anatomy of an application question

Knowing how questions are built is itself review, because the parts map exactly onto this hub's pages:

A worked exam question dissected into three labelled parts. The scenario: a node publishes once a second; the dashboard polls every two seconds; a student reports the page's number is sometimes three seconds old and concludes the bridge must be losing messages. The task: evaluate the conclusion. Three answer arrows lead from the question: the trap answer, agree, the bridge is buggy, marked as the misconception that something must be broken; the correct route, the staleness bound T pub plus T poll equals about three seconds, so the observation is the design working, marked with the equation card; and the discriminator, a strong answer also states what reading would indicate a real fault, staleness growing beyond the bound, and names the probe, curl the API and compare, marked clinic plus half-splitting. The scenario, with its numbers "A node publishes about once a second; the dashboard polls every 2 s. A student notices the page's number is sometimes ~3 s old and concludes the bridge is losing messages. Evaluate the conclusion." The trap "Agree: the bridge drops data." The pull: a symptom must mean a fault. The clinic's business. The route staleness ≤ Tpub + Tpoll ≈ 3 s: the observation is the design, working. The card's business. The discriminator What would indicate a real fault (staleness growing past the bound) and the probe: curl, then compare. Full marks live in the right two boxes together: the bound applied, and the falsifying observation named.
Scenario, trap, route, discriminator. Distractors are the clinic's misconceptions wearing exam clothes; routes are the equation card; discriminators reward the engineer's reflex of naming what evidence would change your answer. Week 7 said it first: exams exist to distinguish shed misconceptions from held ones.

The last 24 hours

  1. Sunday, daylight: the final circuit lap, clinic pass included; patch nothing new after it, only consolidate.
  2. Sunday evening: one last end-to-end run of D3's rung (it was tagged days ago; this is confirmation, not work), pack both kits, exam and bench, and stop. Sleep is consolidation; the research Week 7 cited has not changed.
  3. Monday morning: nothing new. The equation card over breakfast if it calms you; the journey narrated once on the way in.
  4. 14:30: seated, kit out, the Week 7 craft, plus the placement habit. The second proof comes after; let it wait its turn.

Checklist for this stage