Proto-Engineering

This course is an apprenticeship in the engineering design loop — define the problem, set the constraints, build the rough thing, test it, read the failure, build it again — learned by running it with the hands rather than reading theory off a page, and then run a second time in a material you cannot hold. Part I is atoms. Its units move through force and the simple machines, structures and load paths, the arch, materials and composites, measurement and tolerances, and failure analysis, with Rome as the recurring touchstone: the treadwheel crane, the voussoir arch and the Pantheon dome, pozzolana concrete, the surveyed road. Every unit ends by running that unit's idea through the full loop in a real build — a paper tower that must hold a weight, a craft-stick lifter with measurable mechanical advantage, a newspaper bridge loaded to failure, a cardboard arch that stands when the form is pulled away — using only what is already in the house. No kits, no specialty purchases, and any step needing an adult's hands or eye protection is flagged in the teacher note.

Part II is bits. The wall that once demanded a year of programming syntax has come down: a student can now build working software by describing what he wants clearly enough, and the course treats that as a lathe rather than a magic wand. The loop is the same one — with a single station added, and that station is the reason the half exists. When a student builds a paper tower he built it; when a code-generation assistant returns thirty working lines in four seconds he put none of them there, so a step goes in between prototyping and testing whose only job is to find out what he actually has. From there the units run specification, verification, iteration and the tool's honest limits, and the student ships a working thing a stranger could open. One law governs throughout: unverified output is unfinished work. The tool sounds exactly as confident when it is wrong as when it is right, and the difference between a builder and a passenger is that the builder finds out which. Lesson prose names categories of tool rather than brands, so the moves survive the products.

There are two capstones, one per material. Unit 8 is Define, Build, Defend: the student chooses a real problem, writes the statement and constraints, prototypes, tests through at least two documented iterations, and presents a defense. Unit 14 is Ship It: the whole loop run on a problem he chose, delivered as a working artifact plus a builder's brief accounting for what he specified, what the tool contributed, and what he verified and fixed. Both end the same way, because a defense is what this course means by finished — not a working object, but a working object the builder can stand up and explain.

The full course opens September 1. Founding Families watch the ladder fill in — at a price that never moves.