Sixty Years on Hold

The Webb essay runs fifteen sections and ends in an interactive mission Explorer. It walks you through SNAP-10A, which flew forty-three days in 1965. Then NERVA's twenty-three firings that never reached flight. SP-100 spent a whole decade without producing hardware. JIMO burned $463 million and got cancelled inside two years. DRACO is slated for phase-out in 2025.

None of those programs succeeded in the usual sense. That's the whole point. Webb's thesis is that sixty years of failure was itself a structural accomplishment, held together by a scattered apparatus of senators, civil servants, and engineers who kept the knowledge alive across political cycles that kept yanking the money.

The Explorer at the end lets you build a mission profile against the NSTM-3 tier baseline and see which historical precedent your build resembles. The argument isn't that the memo was the point. The hold was the point. And the memo only worked because the hold held.

Same lens, wider target: the companion essay aims it at the federal state as a whole. The move is to read the government as a portfolio, forty-nine unexercised capabilities, each tagged with a strike condition, a premium, a decay rate, a switchability score, and a reconstitution difficulty. From there it runs a scenario. Amazon buys the warehouse and applies its acquisition playbook. What stays. What goes. What ends up for sale.

There are two things to play with. A Playbook Simulator steps through six acquisition moves, and for each one you watch the inventory degrade along some particular axis. A Portfolio Explorer ranks the forty-nine options by reconstitution and switchability, then shows you how the highest scorers survive acquisition logic, or don't.

What comes out of all this is the argument itself. The most important options are also, disproportionately, the ones you lose first. That's not an accident. The traits that make them valuable, diffuse beneficiaries, prevention rather than product, payoff you can only measure looking backward, are precisely the traits an optimizer can't read.

Read them in whatever order you want. The Webb piece is a dramatized case; the State Keeps piece is the framework that case sits inside. Webb shows you what a sixty-year hold looks like when it actually works. State Keeps shows why that kind of hold almost never happens: it's costly, politically disorganized, and mispriced by any evaluator who only scores the output you can see.

Both are interactive. Both run on the same design system: cream paper ground, ink borders, red and yellow accents, Archivo Black for display, Fraunces serif for the body. And both make the same argument in different keys. The work of holding something together is invisible by design. The memo gets the podium. The thing that built the podium doesn't.