Shipped dark

For nine days before Maple Grove, the cheer feature is in production and no spectator on earth can see it.

That sounds like a contradiction and is actually the era’s best trick. deploymentConcept · lights on your mapdeploymentGetting code onto the production servers, running: a technical act, performed by the pipeline, possibly many times a day. Deployed code can be entirely invisible, since deployment moves bytes, not experiences. moved the bytes onto production machines. releaseConcept · lights on your mapreleaseMaking a feature available to users: a product act, often done by flipping a flag, no deploy required. A decision about people and timing, decoupled from the engineering of shipping code. is the separate act of letting people see, and Traversal split the two on purpose. Engineers deploy on Tuesdays; Dana releases on race mornings. Different acts, different owners, different adrenaline.

The hinge between them is a feature flagConcept · lights on your mapfeature flagA configuration switch wrapped around a feature: on shows it, off behaves as before. Flags decouple release from deployment, allow gradual and targeted rollouts, and, crucially, allow instant off with no redeploy.: one switch, wrapped around the whole feature, off by default. Shipped dark, the engineers say, and the phrase deserves its small shiver. The code is out there, running, waiting behind a light-switch.

Race morning, week ten

Saturday, 7:40 a.m., Maple Grove. Dana, with a coffee in one hand and Priya on a call in the other, flips the flag for five percent of the morning’s spectators, watches the charts breathe for twelve minutes, and only then widens it. Not everyone. Five percent. Releasing to a small real slice first and widening on evidence is a canary releaseRecognition — just know it existscanary releaseReleasing to a small slice of real traffic first, the coal-mine canary, watching the signals, then widening. The flag’s gradual-rollout idea, formalised., named for the coal-mine bird, and the canary sings: cheers flow, nothing smokes, the slice widens to everyone by 8:15. Somewhere in the morning, four hundred strangers cheer four thousand runners through a 10K, and a feature that was a whiteboard box in week one is simply true.

And one more thing runs at Maple Grove that no one sees at all. The projected-finish model, Finn’s spike grown into a prototype, runs in shadow modeRecognition — just know it existsshadow modeRunning new code on real production traffic while showing users only the old behaviour: the new version performs invisibly, its answers logged and compared offstage. The ultimate dress rehearsal, beloved for AI features.: fed every real split, predicting every real finish, showing nobody anything. Its guesses are logged next to what actually happened, to be judged in private. The ultimate rehearsal, for the feature with the least room to be embarrassing.

One more recognition word rounds out the family: blue-green deploymentRecognition — just know it existsblue-green deploymentRunning two identical production environments, blue current and green new, and switching traffic between them at the load balancer. Instant cutover, instant revert., two identical productions with a traffic switch between them, instant cutover, instant retreat. Traversal keeps the pattern in its back pocket for race weekends.

Maple Grove works. Down at the finish line, meanwhile, an older and stranger piece of the operation has been running all morning on a folding table.