What a write left IN FLIGHT — undefined when the store committed within the call, the
landing's promise when it did not.
It exists because a row's ANSWER is composed by re-reading the one store, and a store whose
door is asynchronous has not moved yet at that instant. Task #79, on the rig: PATCH /patch/input/input/4 with one endpoint removed answered the PRE-write pair while the GET a
moment later was already right, so every surface — a surface adopts its own reply, that is
what a reply is for — painted the stale value back and the operator read "the unpatch did
nothing". The write was never the defect; the ORDER of the answer was.
So the signal is carried, not remembered: a door that suspends hands its promise up through
PatchOutcome and import('./resource-registry.js').ResourceRegistry waits on it
before it reads the state that becomes the reply, the broadcast and the projection's input.
A store with nothing in flight answers undefined and nothing waits. There is no per-row list
of "rows that need this" and there cannot be one: the pipeline that composes every answer is
the same pipeline for every row.
A settlement never REJECTS. The station attaches the door's refusal logging (an engine refusal
lands late and is reported the moment it arrives — CONTRIBUTING §3), so what reaches the
pipeline is a promise that resolves once the store has stopped moving.
What a write left IN FLIGHT —
undefinedwhen the store committed within the call, the landing's promise when it did not.It exists because a row's ANSWER is composed by re-reading the one store, and a store whose door is asynchronous has not moved yet at that instant. Task #79, on the rig:
PATCH /patch/input/input/4with one endpoint removed answered the PRE-write pair while the GET a moment later was already right, so every surface — a surface adopts its own reply, that is what a reply is for — painted the stale value back and the operator read "the unpatch did nothing". The write was never the defect; the ORDER of the answer was.So the signal is carried, not remembered: a door that suspends hands its promise up through PatchOutcome and import('./resource-registry.js').ResourceRegistry waits on it before it reads the state that becomes the reply, the broadcast and the projection's input. A store with nothing in flight answers
undefinedand nothing waits. There is no per-row list of "rows that need this" and there cannot be one: the pipeline that composes every answer is the same pipeline for every row.A settlement never REJECTS. The station attaches the door's refusal logging (an engine refusal lands late and is reported the moment it arrives — CONTRIBUTING §3), so what reaches the pipeline is a promise that resolves once the store has stopped moving.