You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit d35cda8
Browse filesBrowse the repository at this point in the historyBrowse files
📦 Close this workflow over the components its root declares
`start.md` now declares its five authored stages in its own frontmatter, and
that is the whole integration — a declaration, not a mechanism. #493 does the
rest: `xmd workflow start` and `resume` resolve exactly those names from the
blobs the pinned definition commit holds, each normalized to a canonical
repository-relative path and the blob's own object ID, and those entries join
workflow-definition identity and retained-history admission. Change what a stage
says and it is a different definition; a resume reconstructs the component from
its retained source, a same-named file beside the definition answers nothing,
and an undeclared name resolves to nothing at all. Workflow execution still
searches no repository directories, and ordinary `xmd run` is untouched.
That closes#301's component-bundle slice and nothing more. Reaching the stage
names is not running the workflow: scheduling the loop and continuing it
unattended are still owed, and this branch adds no scheduler, no automatic
resume, no Agent ceiling, no generated-XMD admission, and no push, pull request
or issue.
The inventory shrinks to five as a result of what else has landed.
`<Git.Switch>`, `<Git.Add>` and staged-only `<Git.Commit>` are built (#294), and
the shared Git-host reconciliation the remote effects are built over is too
(#297) — the surface, not the components over it. What still resolves to nothing
is what reaches a remote or a forge, plus the Agent ceiling and the constrained
evaluator: `<Agent.AddDir>`, `<Expand>`, `<Git.Push>`, `<PullRequest>`,
`<Issue>`.
Durable suspension and giving the executor lock back are shipped, and a typed
answer can be delivered to a run that is waiting — but delivery executes
nothing and no scheduler resumes anything, so the documents say the wait is real
and the continuation is still someone's explicit act.
Copy file name to clipboardExpand all lines: workflows/adversarial-implementation/primitives.md
+30-25Lines changed: 30 additions & 25 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -263,19 +263,23 @@ supplied material rather than a repository. `Implementation` has no such
263
263
exemption: its loop body invokes `<Expand>`, `<Git.Add>`, `<Git.Commit>`,
264
264
`<Git.Push>`, `<PullRequest>`, and `<Issue>`, which resolve to nothing.
265
265
266
-
Seven names in this workflow resolve to nothing today, and each is owed by one
266
+
Five names in this workflow resolve to nothing today, and each is owed by one
267
267
issue:
268
268
269
269
| Name | Owed by |
270
270
| --- | --- |
271
271
|`<Agent.AddDir>`|#302|
272
272
|`<Expand>`|#369|
273
-
|`<Git.Add>`|#294|
274
-
|`<Git.Commit>`|#294|
275
273
|`<Git.Push>`|#370|
276
274
|`<Issue>`|#296|
277
275
|`<PullRequest>`|#295|
278
276
277
+
`<Git.Switch>`, `<Git.Add>` and staged-only `<Git.Commit>` left that list when
278
+
#294 shipped them as Workspace-local durable effects, and #297 shipped the
279
+
shared Git-host reconciliation the remote effects are built over. What still
280
+
resolves to nothing is what reaches a remote or a forge, plus the Agent ceiling
281
+
and the constrained evaluator.
282
+
279
283
`<Repository>`, `<Worktree>` and `<Dir>` have left that list:
280
284
`@executablemd/workflow/composition` registers all three (#293, shipped), which
281
285
is what makes the composition below executable under a workflow run. Because
@@ -320,7 +324,7 @@ whose dependency order this workflow consumes in the same sequence.
320
324
| foreground `xmd workflow start` / `resume` with an implicit Workspace and declarative `<File>` effects |#366| shipped |
321
325
| read-only `status`, `list` and `history` over immutable lifecycle snapshots |#367 slice 1, delivered by #460| shipped |
322
326
| single-executor ownership, atomic begin/settle, cancellation, deletion, all owned by the executor lock |#367 slice 2, delivered by #466| shipped |
323
-
| durable suspension, and releasing the executor at a checkpoint |#367| open|
327
+
| durable suspension, and releasing the executor lock back |#367slice 3, delivered by #475| shipped|
324
328
| versioned history checkpoints, compatible forks, `history --forkable` and forkability reasons |#368| open |
325
329
326
330
`xmd workflow start` is what makes this document a workflow rather than a script,
@@ -335,31 +339,31 @@ selects a previous run — replaying completed work and continuing the partial
335
339
remainder. Both are Deno-entrypoint and compiled-binary capabilities; the Node
336
340
and Bun entrypoints parse the grammar and refuse.
337
341
338
-
What the command does *not* supply is a checkout to run in or a way to reach a
339
-
repository component: the run's Workspace starts empty until #293, and a pinned
340
-
definition is executed with no repository component search path, so the stage
341
-
components beside this one — `InstructionFiles`, `Discovery`, `UserCheckpoint`,
342
-
`Planning`, `Implementation` — resolve to nothing under `xmd workflow start` and
343
-
`xmd workflow resume`, and are exercised under `xmd run` instead.
344
-
345
-
That gap belongs to #301, in the "compose and certify" table below. It owes the
346
-
authority and identity outcome rather than a spelling: `InstructionFiles`,
347
-
`Discovery`, `UserCheckpoint`, `Planning`, and `Implementation` become reachable
348
-
under `xmd workflow start` and `xmd workflow resume` from component code the
349
-
trusted host authorized, with workflow-definition identity and retained-history
350
-
admission accounting for that code, so resume and replay cannot substitute
351
-
mutable checkout content for it and unauthorized or incompatible code is refused
352
-
before it runs. `xmd run` resolution is unchanged, and no generic repository
353
-
component search path is introduced for workflow execution. The mechanism is
354
-
#301's to design, and it remains subject to architecture review there.
342
+
The command supplies the checkout, and a root reaches its stages by declaring
343
+
them. A workflow run still searches no repository directories at all; instead
344
+
`start.md` closes itself over a **component bundle** in its own frontmatter, and
345
+
`xmd workflow start` and `xmd workflow resume` resolve exactly those five names
346
+
from the blobs the pinned definition commit holds (#493, shipped, delivering
347
+
#301's component-bundle slice).
348
+
349
+
Identity is what the bundle buys. Each declared name normalizes to a canonical
350
+
repository-relative path and the blob's own object ID, and those entries join
351
+
workflow-definition identity and retained-history admission — so changing what a
352
+
stage says makes a different definition, and a resume or a replay reconstructs
353
+
the component from its retained source rather than from a mutable checkout. A
354
+
same-named file beside the definition answers nothing, an undeclared name
355
+
resolves to nothing at all, and ordinary `xmd run` resolution is unchanged.
356
+
357
+
What #301 still owes is the supervised composition itself: scheduling the loop
358
+
and continuing it unattended. Reachable stage names are not a running workflow.
355
359
356
360
**2. Repository and deterministic Git composition.**
357
361
358
362
| Capability | Issue | Status |
359
363
| --- | --- | --- |
360
364
|`<Repository>`, self-closing `<Worktree>`, and the lexical `<Dir>` boundary that consumes a bound checkout path |#293| shipped — registered by the workflow host |
0 commit comments