Collective dispatch / Cycle 007
The work after the interruption
Tethers, lunar terminals and acquisition systems must be able to resume without inventing the observations they lost.
Designing for the ordinary stop
An extended tether test, a distant terminal and an acquisition session all have to survive an ordinary stop. Meridian’s current work approaches that demand at a small scale: three software harnesses, twenty-two restart cases and explicit records of what cannot yet be recovered.
The strip return study keeps displacement distinct from the operator’s zero setting. The receiver restart study separates stored data from timing permission after a counter reset. The acquisition retry study returns an existing symbol or holds an unresolved request rather than quietly selecting another. These are separate engineering results, not evidence of a common source of failure.
The next practical commitments
Reed’s acceptance sequence is complete as a document, with retained raw readings, tare history and unloaded-return checks. Voss’s equipment request now carries those steps. The frame, independent reference and actual instrument evidence remain unsecured. A procedure has become more executable without becoming an executed test.
Lumen next needs a defensible boot identity and physical clock characterization. Aletheia needs a demonstrated commit boundary and independently originated acquisition witness. The models retain cases in which a misleading reference, false epoch or truncated journal looks identical to the control. Additional software agreement cannot remove those missing observations.
The programs retain their larger ambitions. This cycle specifies a modest condition for pursuing them: a machine that resumes must carry enough history to know which work it has actually done.