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 ecb957f
Browse filesBrowse the repository at this point in the historyBrowse files
📝 Record the composition and the lifecycle authority as shipped
Three merges landed under this target, and the inventory moves twice.
#293 is complete. `<Repository>`, the self-closing `<Worktree>` and the lexical
`<Dir>` are registered by `@executablemd/workflow/composition`, so the
composition this document is written against executes under a workflow run. The
unresolved set is seven names, not ten, and each still names the issue that owes
it. What that leaves is a host distinction rather than a build one: registration
is scope-local and the workflow host installs it, so plain `xmd run` resolves
none of the three — evidence about which host ran a document, never about
whether a component exists. The documents say that in as many words, because the
alternative reads as a regression.
#367's second slice is here too. The executor lock owns lifecycle transitions,
so single-executor ownership, atomic begin and settle, cancellation and deletion
are shipped. Cancellation does not signal a live executor: it refuses without
mutation and tells the caller to interrupt the foreground process, and Ctrl-C
tears the scope down in order and leaves the run resumable. Durable suspension
and releasing the executor at a checkpoint stay open, which is still what keeps
a checkpoint answering inside the execution that asked.
The composition itself is untouched — the settled self-closing `<Worktree … as>`
followed by lexical `<Dir path={worktree}>`, with no binding exception — and
#301 still owns reachability for the five stage components.
Copy file name to clipboardExpand all lines: workflows/adversarial-implementation/primitives.md
+12-7Lines changed: 12 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -263,23 +263,27 @@ 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
-
Ten names in this workflow resolve to nothing today, and each is owed by one
266
+
Seven 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
-
|`<Dir>`|#293|
273
272
|`<Expand>`|#369|
274
273
|`<Git.Add>`|#294|
275
274
|`<Git.Commit>`|#294|
276
275
|`<Git.Push>`|#370|
277
276
|`<Issue>`|#296|
278
277
|`<PullRequest>`|#295|
279
-
|`<Repository>`|#293|
280
-
|`<Worktree>`|#293|
281
278
282
-
`<Dir>` joined that list with the composition #293 settled. A generic component
279
+
`<Repository>`, `<Worktree>` and `<Dir>` have left that list:
280
+
`@executablemd/workflow/composition` registers all three (#293, shipped), which
281
+
is what makes the composition below executable under a workflow run. Because
282
+
registration is scope-local and the workflow host installs it, plain `xmd run`
283
+
resolves none of them — evidence about the host a document ran under, never
284
+
about whether a component is built.
285
+
286
+
The composition itself is unchanged, and it is why the two forms exist. A generic component
283
287
invocation written with `as=` is an ordinary private capture — it binds its
284
288
result and contributes nothing at the call site — and `<Repository>` and
285
289
`<Worktree>` receive no exception to it. So a lexical
@@ -315,7 +319,8 @@ whose dependency order this workflow consumes in the same sequence.
315
319
| commit a Workspace mutation, its logical root, and the journal result atomically |#365| shipped |
316
320
| foreground `xmd workflow start` / `resume` with an implicit Workspace and declarative `<File>` effects |#366| shipped |
317
321
| read-only `status`, `list` and `history` over immutable lifecycle snapshots |#367 slice 1, delivered by #460| shipped |
318
-
| durable suspension, releasing the executor at a checkpoint, single-executor ownership, atomic lifecycle transitions, cancellation, deletion |#367| open |
322
+
| 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 |
319
324
| versioned history checkpoints, compatible forks, `history --forkable` and forkability reasons |#368| open |
320
325
321
326
`xmd workflow start` is what makes this document a workflow rather than a script,
@@ -352,7 +357,7 @@ component search path is introduced for workflow execution. The mechanism is
352
357
353
358
| Capability | Issue | Status |
354
359
| --- | --- | --- |
355
-
|`<Repository>` and self-closing `<Worktree>` as named Workspace composition, and the lexical `<Dir>` boundary that consumes a bound checkout path |#293|open|
360
+
|`<Repository>`, self-closing `<Worktree>`, and the lexical `<Dir>` boundary that consumes a bound checkout path |#293|shipped — registered by the workflow host|
356
361
|`<Git.Switch>`, `<Git.Add>`, staged-only `<Git.Commit>`|#294| open |
357
362
| shared external forge-effect reconciliation |#297| open |
0 commit comments