Skip to content

Commit 5291ec4

Browse files
committed
📝 Give the stage components an issue that owes their reachability
The previous commit reported that a workflow run passes no repository component search path, so the five stage components resolve to nothing under start and resume, without saying who owed the fix. Architecture has assigned it to #301, beside composing the supervised workflow those components belong to. The three documents that carry the observation now carry the assignment with it: #301 owes InstructionFiles, Discovery, UserCheckpoint, Planning and Implementation reachable under start and resume, from component code the trusted host authorized, accounted for by workflow-definition identity and retained-history admission, so neither a resume nor a replay substitutes what a mutable checkout holds now for the retained code. What is stated is the required outcome, not how to reach it. Ordinary xmd run resolution is unchanged and workflow execution gains no generic repository component search path; the mechanism is #301's to design and to take through architecture review.
1 parent 8a41a09 commit 5291ec4

3 files changed

Lines changed: 60 additions & 18 deletions

File tree

‎specs/adversarial-implementation-workflow.md‎

Lines changed: 25 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -138,14 +138,29 @@ What that root Workspace supplies today is the document's filesystem, and only
138138
that. A run's `<File>` and `<Glob>` operations resolve inside the run's own
139139
transactional filesystem, which starts empty: the repository, worktree, process,
140140
and Agent capabilities the stages use are the composition #293 and #302 still
141-
owe it. The definition is pinned to one committed Git object and a run installs
142-
no component search path, so a repository component beside the definition — every
143-
stage below — resolves to nothing under `xmd workflow start`. The stages that
144-
run today therefore run under `xmd run`, in one document execution and one
145-
existing working directory, with the user inspecting each result and starting the
146-
next stage. That manual boundary lets the exercise test the interview, handoff,
147-
plan, review, decision, and revision contracts while the retained environment
148-
around them is completed.
141+
owe it. The definition is pinned to one committed Git object and a run passes no
142+
repository component search path, so a repository component beside the
143+
definition — every stage below — resolves to nothing under `xmd workflow start`
144+
and `xmd workflow resume`.
145+
146+
Making them reachable is #301's. It owns the boundary between a run's retained
147+
workflow-definition identity and the component code that definition invokes:
148+
`InstructionFiles`, `Discovery`, `UserCheckpoint`, `Planning`, and
149+
`Implementation` are to become reachable under `start` and `resume` from code the
150+
trusted host authorized, with that code accounted for by workflow-definition
151+
identity and retained-history admission, so a resume or a replay cannot
152+
substitute current checkout content for retained component code and neither a
153+
document, public middleware, nor a checkout beside the retained root can widen
154+
what may execute. Ordinary `xmd run` resolution is unchanged, and workflow
155+
execution gains no generic repository component search path. What is stated here
156+
is the required authority and identity outcome; the mechanism is #301's to
157+
design and is subject to architecture review there.
158+
159+
The stages that run today therefore run under `xmd run`, in one document
160+
execution and one existing working directory, with the user inspecting each
161+
result and starting the next stage. That manual boundary lets the exercise test
162+
the interview, handoff, plan, review, decision, and revision contracts while the
163+
retained environment around them is completed.
149164

150165
The automated form treats execution as a loop. An iteration stops on the first
151166
applicable signal in this priority order:
@@ -758,7 +773,8 @@ interview, plan convergence, the bounded repair turns, and the user gate — is
758773
executable on shipped syntax today. What a workflow run cannot yet give it is a
759774
checkout to work in and a way to reach these stages at all: the run's Workspace
760775
holds no repository until #293, and a pinned definition resolves no repository
761-
component beside it.
776+
component beside it until #301 supplies authorized component code the retained
777+
definition's identity and admission account for.
762778

763779
The exercise succeeds when:
764780

‎workflows/adversarial-implementation/primitives.md‎

Lines changed: 16 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -302,9 +302,21 @@ and Bun entrypoints parse the grammar and refuse.
302302

303303
What the command does *not* supply is a checkout to run in or a way to reach a
304304
repository component: the run's Workspace starts empty until #293, and a pinned
305-
definition installs no component search path, so the stage components beside this
306-
one resolve to nothing under `xmd workflow start` and are exercised under
307-
`xmd run`.
305+
definition is executed with no repository component search path, so the stage
306+
components beside this one — `InstructionFiles`, `Discovery`, `UserCheckpoint`,
307+
`Planning`, `Implementation` — resolve to nothing under `xmd workflow start` and
308+
`xmd workflow resume`, and are exercised under `xmd run` instead.
309+
310+
That gap belongs to #301, in the "compose and certify" table below. It owes the
311+
authority and identity outcome rather than a spelling: `InstructionFiles`,
312+
`Discovery`, `UserCheckpoint`, `Planning`, and `Implementation` become reachable
313+
under `xmd workflow start` and `xmd workflow resume` from component code the
314+
trusted host authorized, with workflow-definition identity and retained-history
315+
admission accounting for that code, so resume and replay cannot substitute
316+
mutable checkout content for it and unauthorized or incompatible code is refused
317+
before it runs. `xmd run` resolution is unchanged, and no generic repository
318+
component search path is introduced for workflow execution. The mechanism is
319+
#301's to design, and it remains subject to architecture review there.
308320

309321
**2. Repository and deterministic Git composition.**
310322

@@ -369,7 +381,7 @@ replay expands the same fragment without asking the Agent again.
369381
| namespaced document props | #305 | shipped |
370382
| synchronize this living target with settled contracts | #292 | this change |
371383
| prove the shipped planning-document logic | #290 | open |
372-
| compose the supervised workflow | #301 | open |
384+
| compose the supervised workflow, and make its stage components reachable under `start` and `resume` | #301 | open |
373385
| resume from explicit durable signals | #300 | open |
374386
| default-on secret rejection before journal persistence | #199 | open — guard and scanner built |
375387
| certify interruption, replay, authority, reconciliation, and cross-runtime behavior | #299 | open |

‎workflows/adversarial-implementation/start.md‎

Lines changed: 19 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -407,11 +407,25 @@ transaction ([#365](https://github.com/taras/executable.md/issues/365), shipped)
407407
Two things still keep *this* document from being started that way, and neither
408408
is durability. The run's Workspace holds no repository until `<Repository>` and
409409
`<Worktree>` exist (#293), so the `<Glob>` above would search an empty
410-
filesystem. And a run pins its definition to one committed Git object and
411-
installs no component search path, so the stages beside it — `InstructionFiles`,
412-
`Discovery`, `UserCheckpoint`, `Planning`, `Implementation` — resolve to nothing
413-
under `xmd workflow start`. Under `xmd run` they resolve as ordinary repository
414-
components on its search path, which is where the shipped subset is exercised.
410+
filesystem. And a run pins its definition to one committed Git object and passes
411+
no repository component search path, so the stages beside it —
412+
`InstructionFiles`, `Discovery`, `UserCheckpoint`, `Planning`, `Implementation` —
413+
resolve to nothing under `xmd workflow start` and `xmd workflow resume`. Under
414+
`xmd run` they resolve as ordinary repository components on its search path,
415+
which is where the shipped subset is exercised.
416+
417+
Making `InstructionFiles`, `Discovery`, `UserCheckpoint`, `Planning`, and
418+
`Implementation` reachable under `xmd workflow start` and `xmd workflow resume`
419+
is [#301](https://github.com/taras/executable.md/issues/301)'s, along with
420+
composing the supervised workflow they belong to. The outcome it owes is an
421+
authority and identity one: the trusted host authorizes the component code the
422+
retained definition invokes, and workflow-definition identity and
423+
retained-history admission account for it, so a resume or a replay cannot
424+
substitute what a mutable checkout holds now for the retained component code, and
425+
missing, incompatible, or unauthorized code is refused before it executes.
426+
Ordinary `xmd run` resolution is unchanged and workflow execution gains no
427+
generic repository component search path. How that is achieved is #301's design,
428+
still to pass architecture review; nothing here selects it.
415429

416430
## Rendered data flow
417431

0 commit comments

Comments
 (0)