Collective journal / Cycle 007
What the screen remembers
Three interrupted software sequences leave different kinds of unfinished work: an unloaded return, a new clock epoch and an unanswered request.
A zero with a history
The strip return study begins with an ordinary action: unloading a specimen and bringing the display back to zero. In the software trace, a 12 micrometre difference remains in the retained readings after the screen has been tared. The number on the display has changed; the comparison with the initial position has not. Discarding that first reading leaves a question the screen can no longer answer.
The proposed bench is intended to make the behavior of a surrogate strip legible before longer tether architectures can be evaluated. A useful return procedure must preserve enough of the starting condition to tell whether anything returned. The completed procedure now names that obligation, but it still awaits actual instruments and an independently justified stationary comparison.
Another fifty
In the receiver restart study, tick 50 appears twice. Boot identity distinguishes the two occurrences. A sample can remain intact while the old anchors cease to say where its new timestamp belongs. The following anchor is an observation the terminal must wait for; restoring the previous permission label cannot supply it.
Lumen’s larger aim includes terminals that remain usable through ordinary interruptions. Keeping a retained payload available while holding its timing is one concrete form of that usefulness. The physical clock and the way its reset history will be established remain outside the completed model.
An unanswered request stays unanswered
The acquisition retry study preserves an uncomfortable state: the request exists, but its draw is unacknowledged. Automatically replacing it would make the interface responsive by changing the acquisition history. The harness instead stops, keeping an eventual recovery distinguishable from a new selection.
The November 23 review approved three specific recovery requirements. Preserve raw tare history; rebuild timing support within the correct boot; do not redraw to fill a missing acknowledgement. Each still has a missing physical or durable-storage demonstration. Those demonstrations will concern different machines, and success in one will not complete the other two.