Tools & Artifacts

Countdown to Core

Three sets of initials in the core. The names are mine. The habits came off a launch pad.

Go poking around in the core of Cairn and you will hit three sets of initials that look like arbitrary software house-style: VBM, GFC, RC. The initials are mine; I made them up. The habits they stand for are not. I took those from how the Apollo countdown actually ran - specifically from The Terminal Countdown Sequencer: The Relay Logic That Timed Saturn V's Launch, a video by Apollo11Space that convinced me the countdown had already solved the problem I was building around - how to do irreversible things carefully. Three of those habits went into the core and have been buried there ever since. I hardly ever notice them. They just work.

The Apollo 8 Saturn V an instant after ignition at dawn, engines lit and venting, still beside the launch tower, with a thin crescent moon in the sky. — Apollo 8, an instant after ignition on December 21, 1968 - the first crewed Saturn V. The Terminal Countdown Sequencer has run its chain through to ignition; the engines are lit, the hold-downs are about to release, and from here there is no calling it back. Photo: NASA.

That chain - cleared by one last human go/no-go, then run gate by gate in fixed order - is the method Cairn borrowed. The three habits below are how Cairn runs the same idea on a much smaller scale.

VBM · verify before you write

Verify-Before-Modify. Before the AI writes a single file it states exactly what it is about to do and where: creating 20251220-ssl-fix.md in Tracks/p014-blog-migr/tasks/. The countdown did this as the go/no-go poll - before any committing step, the room was polled and the count moved only on an explicit, spoken "go." Nothing irreversible happened on an assumption, which is the whole idea: the cheapest moment to stop a mistake is before it lands.

GFC · never fail silently

Graceful Fallback Chain. When something fails, the system steps down a visible chain instead of dying quietly: if the write fails, try a download; if that fails, show the content directly; and whatever happens, report where it landed. The countdown's version was its redlines - hard limits that, when crossed, tripped a hold and stopped the clock rather than letting trouble slide by unseen. A failure you can see is one you can work; the silent one is the dangerous one.

RC · record the why

Rationale Capture. Every entry carries its reason: not "on hold" but "on hold, waiting on the vendor's credentials since the 14th"; not "fixed the SSL chain" but "fixed the SSL chain - the certs were expiring." Apollo ran on mission rules, decisions worked out in advance with the reasoning written beside each one, and on flight logs that kept the why, not just the what - so that under pressure no one had to reconstruct why a given limit meant stop. It is also, exactly, what a cairn is: a stone set down so the next traveler knows why.

The through line

So when you find VBM, GFC, and RC in the core looking like some private software dialect, that is only half the story. The initials are mine. The habits are the countdown's, borrowed on purpose and then buried so thoroughly I forget they are there. Not a rocket. Just three good habits that came off a launch pad.