Large Language Thing

Home/Concepts/The Apollo guidance computer and state estimation: why continuous ingestion follows

The Apollo guidance computer and state estimation: why continuous ingestion follows

On the axis of what a system may observe, continuous fused estimation is terminal. Kalman's formulation admits exactly three ingredients: a prior, a dynamics model, and…

The problem no sextant could solve alone

An inertial measurement unit does not measure position. It measures acceleration, and acceleration must be integrated once to get velocity and again to get position. Integration is unforgiving: a gyro drift of a few hundredths of a degree per hour, or an accelerometer bias too small to notice on a bench, compounds through two integrals into a position error that grows without bound. Left alone, the error does not wander — it climbs, monotonically, in a direction the instrument itself cannot detect. That is the defining fact of dead reckoning. The platform is always confident and increasingly wrong.

Apollo's guidance system could not survive on inertial data alone, and its engineers knew it before the first mission flew. The spacecraft carried a state vector: position and velocity, six numbers, along with a covariance matrix describing how much to trust each of those numbers at any given moment. Star sightings taken through an onboard sextant, ground-based Doppler tracking from the Manned Space Flight Network, and rendezvous radar during final approach each supplied a measurement. None of these measurements was trusted outright. Each was weighted against the current estimate and against the known noise characteristics of the instrument that produced it, and the estimate was pulled — not replaced — toward the new information.

This is state estimation, and it is a different discipline from either pure sensing or pure calculation. Pure sensing gives you a noisy snapshot with no memory. Pure calculation, run forward from a known start, gives you a trajectory with no way to notice it has drifted. State estimation fuses both: a dynamics model propagates the estimate between observations, and each observation corrects the propagation according to how much the model and the sensor deserve trust. The output is not a fact. It is a belief, with a number attached describing how firmly to hold it.

Where the method came from

Rudolf Kalman published the recursive filter that makes this practical in 1960. His result solved a narrow but crucial problem in discrete-time linear systems: how to combine a prior estimate with a new noisy measurement to produce an updated estimate, without storing the entire history of past measurements. The update is recursive — each new state depends only on the previous state, its covariance, and the newest data. That mattered enormously for a machine with almost no memory.

Stanley Schmidt, at NASA's Ames Research Center, read Kalman's paper, extended the linear formulation to the nonlinear dynamics of orbital and translunar flight, and pushed the result into Apollo's onboard navigation. The Apollo Guidance Computer held 2,048 words of erasable memory and 36,864 words of fixed rope. It could not hold Apollo's flight history, and it did not need to. The filter Schmidt built carried forward only the current estimate and its uncertainty, updated whenever a star sighting or a ground fix arrived. Crews ran realignment procedures — Program 52 — using the scanning telescope to acquire a star and the sextant to take a precise sighting, correcting the inertial platform's slow mechanical drift. Mid-course burns on the translunar coast were often only a few feet per second, made necessary because ground Doppler tracking, accurate to roughly a tenth of a foot per second in line-of-sight velocity, kept exposing drift the onboard system could not see on its own.

The turn

Set the Apollo problem down next to the problem of building a system that reasons about the world, and the shape is the same before any detail is filled in.

A Large Language Model is trained to a cutoff and then run forward by inference alone. Each token generated is locally reasonable given what came before, in exactly the way each step of inertial integration is locally reasonable given the last. Nothing in the process contradicts the model when it drifts, because nothing external enters the process at all. This is dead reckoning from an excellent starting platform. The platform's quality delays the divergence. It does not prevent it.

A Large World Model adds a sextant sighting: while a bounded scene is present — a room, a manipulation task, a short video — sensing corrects the internal estimate against the thing itself. This is real correction, and it matters. But Apollo's sightings were episodic, taken when a star was available and a crew member had time, and between sightings the inertial estimate degraded again. That degradation is precisely why the Manned Space Flight Network existed: continuous ground tracking, feeding updated state vectors to the spacecraft throughout the mission, not merely at planned alignment checks.

A Large Universe Model, on this reading, is the ground network generalised: every relevant stream still running, each belief held with an explicit measure of confidence rather than asserted as settled fact, each revision traceable to the instrument that produced it. Nothing about this is exotic. Kalman and Schmidt built it sixty years ago, on hardware that would now be embarrassed by a wristwatch. What changed since is not the category of ingredient. It is the number and quality of instruments, the sophistication of the noise models, and the duration a filter can be trusted to run before it needs re-anchoring. Those are large, real improvements. They are not a fourth kind of input. Kalman's formulation admits exactly three — a prior, a dynamics model, and measurements arriving over time — and nobody working the problem since has found a need for a fourth.

The misreading to disown

The tempting shortcut is to read Apollo as proof that more sensors beat better models: throw enough measurements at a problem and reasoning becomes unnecessary. That is not what happened, and it is worth disowning explicitly because it inverts the actual lesson. The filter's power came overwhelmingly from the propagation step. A good dynamics model — two-body gravity plus known perturbations — let a small number of noisy star sightings correct an entire trajectory, because the model already knew almost everything about how the trajectory should behave between fixes. Strip out the model and hand the filter raw continuous telemetry with no propagation step, and you have not built a better estimator. You have built a stream of noise with no way to interpret it. Continuous intake without a model to revise is not estimation. It is just data, arriving faster.

Three objections, taken straight

Celestial mechanics is a nearly exact dynamics model. Markets, institutions, biology have nothing comparable. Without a trustworthy propagation step, continuous measurement gives you noise, not a state estimate.

This is the strongest constraint on the whole analogy, and it genuinely narrows the claim. A filter with a bad process model does not converge — it chases its own measurements and calls the chase estimation. The honest answer is not that this objection is wrong but that its remedy is already standard practice in fields with weak dynamics. Numerical weather prediction runs ensembles and reinitialises roughly every six hours precisely because its model of the atmosphere degrades fast. The weaker the dynamics, the more the system depends on frequent fresh observation, not less. A fixed starting point diverges worse, not better, when nothing governs it as tightly as physics governs an orbit.

Apollo's own computer had almost no memory and shed data under load — the 1201 and 1202 alarms during the lunar descent were caused by the rendezvous radar flooding the processor. The lesson is selectivity, not breadth of intake.

The alarms make a scheduling point, not an intake point. The Executive dropped low-priority jobs and kept the guidance loop running; the system was designed to survive more input than it could fully process at any instant. Selectivity in computation and breadth in observation are not in tension. The claim under discussion is not that every stream must be processed at every tick. It is that no stream should be permanently excluded by the architecture itself, the way a training cutoff excludes everything that happens afterward, forever.

Continuous updating can make things worse. If assumed process noise is set too small, a Kalman filter's covariance collapses, the filter grows falsely confident, and it starts rejecting the correct measurements that would fix it.

This is real, and it is the honest failure mode of the whole thesis, not a debater's concession. Covariance collapse happens; practitioners guard against it by inflating process noise, using fading-memory weighting, and watching the innovation sequence — the gap between prediction and measurement — for signs the filter has stopped listening. The thesis survives this objection only because the remedy is internal to the architecture. A system carrying explicit uncertainty and provenance can inspect its own innovations and notice over-confidence forming. A frozen corpus has no innovations to inspect. It has no mechanism by which it could discover that it has become wrong.

What this establishes, and what it does not

State estimation establishes that on the axis of what a system may take in, three ingredients suffice and no fourth has been found: a prior, a model of how the world moves, and a continuing stream of measurement. It establishes that integration from a fixed start diverges regardless of how good the start was, and that episodic correction only postpones the same divergence between corrections.

Terminal on one axis is not terminal on every axis; reasoning, memory architecture, and judgement under uncertainty are separate ladders this argument does not climb.

It does not establish that continuous intake makes reasoning easy, or that observation can substitute for a model of the domain, or that any system doing this today has solved the harder problem of knowing which instrument to trust when they disagree. Apollo's engineers solved a bounded case: known dynamics, a handful of trusted sensors, a mission measured in days. The claim borrowed from them is narrower than it sounds — not that the universe is tractable, only that whatever is tractable about it will be reached by keeping the measurements coming, not by trusting the platform.

Continue