Skip to content

Commit 92cec28

Browse files
committed
📝 Say the wait is built everywhere the documents mention it
Two passages still described `suspendFor()`'s work as missing, and my sweep let them through because it only recognised the word "unbuilt". They said it another way: "durable suspension, and releasing the executor at a checkpoint, remain #367" in `start.md`, and "What is not built is the wait" in the specification. Both are corrected the same way the rest of the target already reads. The wait is built — a run suspends durably and gives its executor lock back (#367), and a typed answer can be delivered to it (#300). What is not built is anything that reaches or acts on it: no v1 Markdown element spells the operation, this workflow calls nothing that suspends, delivery executes nothing, and no scheduler resumes a run. `start.md`'s "waiting is a suspension" section now says that at the point where a reader would otherwise conclude its checkpoints already suspend. The sweep is broadened to the phrasings it missed — "remain #367", "not built is the wait", "still missing is the wait", and an elicitation that "is to record its pending request" — each self-tested against the sentence that produced it, and each failing against the commit they were found in.
1 parent bd7ad74 commit 92cec28

2 files changed

Lines changed: 27 additions & 15 deletions

File tree

‎specs/adversarial-implementation-workflow.md‎

Lines changed: 7 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -624,9 +624,13 @@ and directs the caller to interrupt the foreground process, while an eligible
624624
retained state transitions to `cancelled` under the exact lock, and a
625625
`completed` or `failed` outcome stays authoritative.
626626

627-
What is not built is the wait. Durable suspension and releasing the executor at
628-
a checkpoint remain #367; versioned history checkpoints, compatible forks,
629-
`history --forkable`, and forkability reasons remain #368.
627+
The wait is built too: `suspendFor()` suspends a run durably and gives its
628+
executor lock back (#367), and a typed answer can be delivered to it (#300).
629+
What is not built is anything that reaches or acts on it — no v1 Markdown
630+
element spells the operation, this workflow calls nothing that suspends,
631+
delivery executes nothing, and no scheduler resumes a run. Versioned history
632+
checkpoints, compatible forks, `history --forkable`, and forkability reasons
633+
remain #368.
630634

631635
**Still missing: who answered.** The journal records the validated decision, the
632636
question fingerprint, and the document execution it belongs to. It does not

‎workflows/adversarial-implementation/start.md‎

Lines changed: 20 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -329,14 +329,18 @@ this root's output.
329329
## Waiting for the user is a suspension, not a stop
330330

331331
A checkpoint that reaches a person is a durable wait, and a durable wait is not
332-
a failure. Under `xmd workflow` the elicitation is to record its pending request
333-
and the Workspace frontier, release the executor, and return control with a run
334-
ID and a stop reason on standard error, so that the process, the Workspace
335-
attachment, and the Agent processes need not stay alive.
336-
`xmd workflow resume <run-id>` already continues the same workflow run once the
337-
answer is available: completed durable effects restore from the journal,
338-
ephemeral attachments rebuild, and partial replay continues at the retained
339-
frontier.
332+
a failure. The mechanism for one exists: `suspendFor()` records a pending
333+
request and the Workspace frontier, gives the executor lock back, and returns
334+
control with a run ID and a stop reason on standard error, so that the process,
335+
the Workspace attachment, and the Agent processes need not stay alive (#367).
336+
`xmd workflow resume <run-id>` continues the same workflow run once the answer
337+
is available: completed durable effects restore from the journal, ephemeral
338+
attachments rebuild, and partial replay continues at the retained frontier.
339+
340+
The checkpoints above do not call it. `suspendFor()` is an Api operation with no
341+
v1 Markdown element, and a suspension is a different mechanism from `<Elicit>`,
342+
which asks inside the execution already running — so nothing here converts one
343+
into the other.
340344

341345
That is what the earlier drafts of this document were reaching for with a
342346
`<Stage>` boundary. The construct was rejected — the root document is the
@@ -348,10 +352,14 @@ retained frontier. Reading a run back is shipped too: `xmd workflow status`,
348352
`list`, and `history` report immutable lifecycle snapshots without advancing
349353
anything (#460). So is the authority underneath: the executor lock owns
350354
lifecycle transitions, so single-executor ownership, atomic begin and settle,
351-
cancellation and deletion are shipped (#466). What is still missing is the wait
352-
itself — durable suspension, and releasing the executor at a checkpoint, remain
353-
#367. So a question asked today is answered inside the document execution that
354-
asked it. Gating is expressed by nesting, which
355+
cancellation and deletion are shipped (#466). So is the wait: `suspendFor()`
356+
suspends a run durably and gives its executor lock back (#367), and a typed
357+
answer can be delivered to it (#300, non-executing).
358+
359+
What is missing is the join. No v1 Markdown element spells `suspendFor()`, this
360+
document calls nothing that suspends, and no scheduler resumes a run — so a
361+
question asked today is answered inside the document execution that asked it,
362+
and reaching that substrate belongs to #301's supervised composition. Gating is expressed by nesting, which
355363
prevents the remaining stages from running but does not stop the document
356364
execution: it still reaches the final-gate report inside the root's `<Output>`
357365
and completes.

0 commit comments

Comments
 (0)