The Build, End to End

The transit app that Unit 1 swept as a user's experience returns as an engineering project — every phase, role, pattern, and test this unit named, applied in order, with the licensing question the platform itself lives by.

A city commissions the bus app from video 0035, and this time the camera faces the builders. The four Ps (0472) set the approach: a civic problem, a fixed budget, a small team, a public product — pointing away from heavyweight prescription toward agility (0478). The work still fits the generic framework (0474): inception scopes rider needs, elaboration designs, construction builds, deployment ships — but as sprints (0480), each one running the arithmetic of video 0500. The architecture leans on patterns (0495, 0496): a recognizable style at the top, and underneath it the microservices choice inserted back at video 0069 — routes, payments, and positions as independent services, deployable separately, so a fare-rule change never reships the map. Construction is guarded the whole way: refactoring (0484) keeps the design clean without touching behavior — the regression suite (0491) standing witness — while continuous integration (0486) merges daily and the testing ladder (0489) climbs from one arrival-time function to the interfaces to the whole system, before riders run acceptance on the real thing (0490). Above it all, the enterprise framework (0497) keeps the app aligned with the city's larger strategy — this system is one blueprint layer among many. And one last decision echoes closest to home: the team ships the code open-source (0492), license attached, source public — liberty, not price (0493) — the same licensing philosophy under the course teaching it. The app from Unit 1 was a half-second of magic; this unit's claim is that the magic was managed.