Skip to content

Commit abb535e

Browse files
committed
πŸ“ Say what an unanswered <Elicit> does under a workflow run
"Answered inside the execution that asked it" reads as a settled outcome, and it is not one. The workflow host installs the same WebForm provider `xmd run` does β€” the gate is `!mode.testing`, and the workflow path passes `testing: false` β€” so an unanswered `<Elicit>` opens a loopback browser form and blocks the run. A probe against a committed workflow root says so directly. `workflow start` on a root with an unanswered `<Elicit>` printed a form URL and was still running when the probe killed it at twenty-five seconds; its status stayed `running`, its history recorded no suspension request, and it never settled `suspended` or gave the executor lock back. The same root with an authored `<Answers>` value completed normally. So the four documents now say that: `<Elicit>` is ordinary live elicitation, distinct from `suspendFor()`; `xmd run` and the workflow host both install WebForm; an `<Answers>` region answers without a person; and an unanswered one blocks rather than suspending, publishing neither a validated answer nor a suspension request. The target stays explicit β€” #301's supervised composition must consume `suspendFor()` without inventing a v1 Markdown spelling. The sweep now forbids "answered inside the execution" and requires the provider, the blocking, and the absent `suspended` settlement in its place.
1 parent 900f89e commit abb535e

4 files changed

Lines changed: 24 additions & 9 deletions

File tree

β€Žspecs/adversarial-implementation-workflow.mdβ€Ž

Lines changed: 6 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -192,8 +192,12 @@ would have been used without detecting or prioritizing them.
192192
Signal 3 has a shipped in-run form. `<Elicit>` asks a person a schema-validated
193193
question during execution and binds the validated answer, and `xmd run` composes
194194
the WebForm provider so that question opens a loopback browser form. Under
195-
`xmd workflow` that same question is still `<Elicit>`, answered inside the
196-
execution that asked it. A durable suspension is a different mechanism, and its
195+
`xmd workflow` that same question is still `<Elicit>`, and the same WebForm
196+
provider is installed β€” so an unanswered one opens a loopback form and the run
197+
blocks on it, staying `running`. It publishes no validated answer and no
198+
suspension request, never settles `suspended`, and never gives the executor lock
199+
back. An authored `<Answers>` region answers it without any of that. A durable
200+
suspension is a different mechanism, and its
197201
substrate is shipped: `suspendFor()` waits and gives the executor lock back
198202
(#367), the lock's ownership decides who may continue (#466), and a typed answer
199203
can be delivered to a waiting run (#300). None of that is reached from Markdown

β€Žworkflows/adversarial-implementation/UserCheckpoint.mdβ€Ž

Lines changed: 6 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -208,8 +208,12 @@ that already knows the answer β€” a test, a demo, a non-interactive region β€” w
208208
this component in an `<Answers>` region and supplies it with `<Answer>` matchers,
209209
which changes who answers without changing this file.
210210

211-
Under `xmd workflow` this stays an `<Elicit>`, answered inside the execution that
212-
asked it. A resume restores its journaled answer rather than asking again
211+
Under `xmd workflow` this stays an `<Elicit>`. The workflow host installs the
212+
same WebForm provider `xmd run` does, so an unanswered question opens a loopback
213+
browser form and blocks the run: it stays `running`, publishes no validated
214+
answer and no suspension request, never settles `suspended`, and never gives the
215+
executor lock back. The `<Answers>` region above is how a document answers it
216+
without a person. A resume restores a journaled answer rather than asking again
213217
(#366).
214218

215219
The durable wait this checkpoint is eventually meant to become is a different

β€Žworkflows/adversarial-implementation/runtime.mdβ€Ž

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -183,8 +183,10 @@ An automated iteration stops on the first applicable signal:
183183

184184
Signal 3 has a shipped in-run form: `<Elicit>` asks a person a schema-validated
185185
question during execution, and under `xmd run` the WebForm provider answers it
186-
in a browser. Under `xmd workflow` it is the same `<Elicit>`, answered inside the
187-
execution that asked it.
186+
in a browser. Under `xmd workflow` it is the same `<Elicit>` and the same
187+
provider: an unanswered question opens a loopback form and blocks the run, which
188+
stays `running`, settles nothing as `suspended`, records no suspension request,
189+
and keeps its executor lock. An authored `<Answers>` region answers it instead.
188190

189191
A durable suspension is a different mechanism, and it is shipped as substrate:
190192
`suspendFor()` suspends a run and gives its executor lock back (#367), and a

β€Žworkflows/adversarial-implementation/start.mdβ€Ž

Lines changed: 8 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -357,9 +357,14 @@ suspends a run durably and gives its executor lock back (#367), and a typed
357357
answer can be delivered to it (#300, non-executing).
358358

359359
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
360+
document calls nothing that suspends, and no scheduler resumes a run. A
361+
checkpoint asked today is an ordinary `<Elicit>`: the workflow host installs the
362+
same WebForm provider `xmd run` does, so an unanswered question opens a loopback
363+
form and blocks the run, which stays `running` rather than settling `suspended`
364+
and never gives its executor lock back. An authored `<Answers>` region answers it
365+
instead. Reaching the suspension substrate belongs to #301's supervised
366+
composition, which must consume `suspendFor()` without inventing a v1 Markdown
367+
spelling for it. Gating is expressed by nesting, which
363368
prevents the remaining stages from running but does not stop the document
364369
execution: it still reaches the final-gate report inside the root's `<Output>`
365370
and completes.

0 commit comments

Comments
Β (0)