The App, Complete

One transit app has carried the course from its first unit to its last — experienced, analyzed, built, deployed, and defended — and its final pass runs the rider's half-second through everything at once.

The rider taps a stop, and this time nothing is hidden. The tap wakes a process (0327's referee at work) whose executable the loader placed in memory, whose threads split interface from computation, whose every hardware request crosses the kernel boundary. The screen's request leaves as a small encrypted exchange (0575's production trace) — HTTPS wrapping the wire, the single-page application asking for arrival times and nothing more. It lands on a microservice (0069) in a container, one of a fleet the orchestrator has been scaling since the morning rush, running on rented platform layers in a hybrid cloud whose sensitive side holds the fare records. The service's answer is Unit 3's whole curriculum in a few milliseconds (0169): the city as a graph, the question as shortest path, the algorithm greedy-with-a-proof, the structures underneath chosen by contract and priced by growth. The numbers it computes travel as bits under declared types (0270's decoding lesson), through pipelines and caches and registers, on processors whose every design choice Unit 5 named. The database records the trip as a transaction with its guarantees paid for (0449's two record-keeping lives), and the security posture around all of it answers threat by named threat (0645). The build itself was managed — sprints, tests, patterns, an open-source license (0505). Count what the half-second used: every unit, no exceptions. The app was never the subject; it was the proof that the subjects connect.