Skip to content

Commit 969f8af

Browse files
committed
πŸ”’ Stop presenting an Agent a directory the ceiling denies it
Two paragraphs in each of three documents contradicted each other. One named a third enforcement layer β€” "registered Workspace paths are presented as read-only filesystem views" β€” and the next denied that any path is registered at all. The third layer was the stale half: #302 settles that a workflow Agent receives no checkout, no materialization of one, no Workspace or host path as cwd, and no `additionalDirectories` over ACP, so there is nothing to present read-only. Two layers enforce the ceiling, and the reason there is no third is now the sentence that used to be the third. The data-flow table said `worktree` is consumed by "every stage that registers a directory with an Agent". No stage does. It is consumed by `<Dir>`, and through `<Dir>` by XMD's own file and Git effects. The executable inventory disagreed with its own classification. It said four names in the loop body resolve to nothing and named the three components that reach a remote or a forge β€” but only `<Expand>` and `<Issue>` resolve to nothing. What blocks the stage is now separated by kind: two unresolved names, one unbuilt engine capability (#301's omission of an expression prop evaluating to `undefined`, which the seeded pull-request number needs), and two components that are shipped and merely out of reach behind them. A shipped component behind an unbuilt prerequisite is unreachable, which is not the same claim as unbuilt, and the sweeps now hold that distinction open in both directions: the exact stale sentences fail, and the corrected denials pass.
1 parent a7b9b03 commit 969f8af

4 files changed

Lines changed: 46 additions & 26 deletions

File tree

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

Lines changed: 7 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -668,12 +668,14 @@ because its contents still enter model context.
668668

669669
### Agent authority and generated XMD
670670

671-
Under `xmd workflow` an Agent is mandatorily read-only. Enforcement has three
671+
Under `xmd workflow` an Agent is mandatorily read-only. Enforcement has two
672672
layers: the provider permission bridge allows only read and search operations,
673-
the provider runs in its native read-only sandbox, and registered Workspace paths
674-
are presented as read-only filesystem views. `<ApproveAll>`, repository `.codex`
675-
or `.claude` configuration, and prompt content cannot exceed that host ceiling,
676-
and a provider that cannot enforce it fails before Prompt execution (#302).
673+
and the provider runs in its native read-only sandbox. There is no third layer
674+
presenting Workspace paths as read-only filesystem views, because no Workspace
675+
path is registered with an Agent in the first place. `<ApproveAll>`, repository
676+
`.codex` or `.claude` configuration, and prompt content cannot exceed that host
677+
ceiling, and a provider that cannot enforce it fails before Prompt execution
678+
(#302).
677679

678680
The ceiling is therefore the host's, not the document's. There is no `<Sandbox>`
679681
component and no document prop that grants an Agent write access; earlier

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

Lines changed: 13 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -637,10 +637,19 @@ revision turn, or acceptance.
637637
| the forge read that returns reviews, comments and checks | `<Fetch>` (#456) | shipped β€” this stage does not write it yet |
638638

639639
The agent, parsing, capture, and control-flow syntax runs today, and so do the
640-
local Git effects: `<Git.Add>` and `<Git.Commit>` are built. The loop body above
641-
still does not expand, because four names in it resolve to nothing β€” the
642-
constrained evaluator and the three components that reach a remote or a forge. Until those land, the effects they stand for remain explicit
643-
user-run steps between manual stages.
640+
Git effects: `<Git.Add>`, `<Git.Commit>`, `<Git.Push>` and `<PullRequest>` are
641+
all built and registered by the workflow host.
642+
643+
The loop body above still does not expand, and it is worth separating the two
644+
reasons. **Two names resolve to nothing** β€” `<Expand>` (#369) and `<Issue>`
645+
(#296) β€” and one **engine capability is unbuilt**: omitting an expression prop
646+
that evaluates to `undefined` (#301), which the seeded `number={pullRequest.number}`
647+
needs on its first pass. Neither of those is a statement about `<Git.Push>` or
648+
`<PullRequest>`: those are shipped, and this stage still cannot reach them,
649+
because the `<Expand>` that would produce the change to stage and commit comes
650+
first. A shipped component behind an unbuilt prerequisite is unreachable here,
651+
not unbuilt. Until the prerequisites land, the effects this stage stands for
652+
remain explicit user-run steps between manual stages.
644653

645654
Props are namespaced throughout (#305). `proposal`, `commit`, `pullRequest`,
646655
`verdict`, `checkpointMaterial`, and `reviewCheckpoint` are authored bindings and

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

Lines changed: 7 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -67,12 +67,13 @@ isolation, not a security boundary.
6767

6868
## The Agent ceiling is the host's, not the document's
6969

70-
Workflow Agents are mandatorily read-only, enforced in three places: the
71-
provider permission bridge allows only read and search operations, the provider
72-
runs in its native read-only sandbox, and registered Workspace paths are
73-
presented as read-only filesystem views. `<ApproveAll>`, repository `.codex` or
74-
`.claude` configuration, and prompt content cannot raise that ceiling, and a
75-
provider that cannot enforce it fails before Prompt execution (#302).
70+
Workflow Agents are mandatorily read-only, enforced in two places: the provider
71+
permission bridge allows only read and search operations, and the provider runs
72+
in its native read-only sandbox. No third place presents Workspace paths as
73+
read-only filesystem views, because none is registered with an Agent at all.
74+
`<ApproveAll>`, repository `.codex` or `.claude` configuration, and prompt
75+
content cannot raise that ceiling, and a provider that cannot enforce it fails
76+
before Prompt execution (#302).
7677

7778
There is therefore no `<Sandbox>` component in this workflow, and no document
7879
prop that grants an Agent write access. Earlier drafts of this document declared

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

Lines changed: 19 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -248,9 +248,10 @@ agent's benefit.
248248
## Agents inspect; XMD mutates
249249

250250
Under `xmd workflow` an Agent is read-only, and the host enforces that ceiling
251-
in its permission bridge, its provider-native sandbox, and the filesystem view
252-
it presents. A document cannot raise it, so there is no `<Sandbox>` component to
253-
write: the command selects the environment and the ceiling comes with it (#302).
251+
in its permission bridge and its provider-native sandbox. There is no filesystem
252+
view to enforce it in: an Agent is given no path to see. A document cannot raise
253+
the ceiling either, so there is no `<Sandbox>` component to write β€” the command
254+
selects the environment and the ceiling comes with it (#302).
254255

255256
An implementor that cannot write files proposes changes instead. It returns an
256257
XMD fragment, and a constrained evaluator preflights the whole fragment and
@@ -482,13 +483,20 @@ path as cwd, and no registered directory, so there is no component here to
482483
build. What is still missing is the forge component that files a deferred
483484
finding, and the public component that expands generated XMD.
484485

485-
So what remains non-executable is the implementation stage's remote and forge
486-
effects; the named checkouts the Workspace is composed from, and the local Git
487-
effects inside them, are here. What can be exercised today is discovery through plan convergence and
488-
the user gates around them, running in one document execution and one existing
489-
working directory, with commits, pushes, pull requests, and issues performed as
490-
explicit user-run steps between manual stages. Proving that shipped subset is
491-
#290.
486+
So what remains non-executable is the implementation stage β€” but not because its
487+
Git and forge effects are missing. The named checkouts the Workspace is composed
488+
from are here, and so are the local Git effects, the push and the pull request.
489+
What the stage waits on is what comes *before* them: `<Expand>` (#369) to
490+
produce the change at all, `<Issue>` (#296) to file a deferred finding, and
491+
#301's omission of an expression prop that evaluates to `undefined`, which the
492+
pull-request loop's seeded `number` depends on. `<Git.Push>` and `<PullRequest>`
493+
are shipped and simply out of reach behind those, which is a different thing
494+
from unbuilt.
495+
496+
What can be exercised today is discovery through plan convergence and the user
497+
gates around them, running in one document execution and one existing working
498+
directory, with commits, pushes, pull requests, and issues performed as explicit
499+
user-run steps between manual stages. Proving that shipped subset is #290.
492500

493501
The command and the foundation underneath it are built.
494502
`xmd workflow start [--id] [--props-*] <definition>` and
@@ -536,7 +544,7 @@ does not make the workflow run.
536544

537545
| Captured value | Produced by | Consumed by |
538546
| ---------------------- | -------------------------- | --------------------------------------------------- |
539-
| `worktree` | self-closing `Worktree` (Workspace-relative path) | `Dir`, which makes it cwd for the flow; and every stage that registers a directory with an Agent |
547+
| `worktree` | self-closing `Worktree` (Workspace-relative path) | `Dir`, which makes it cwd for the flow, and through it XMD's own file and Git effects. No stage takes it, and no Agent is given it |
540548
| `instructionPaths` | `Glob` (`string[]`) | `InstructionFiles` |
541549
| `instructions` | `InstructionFiles` (text) | every agent prompt |
542550
| `handoff` | `Discovery` (text) | handoff `UserCheckpoint`, `Planning` |

0 commit comments

Comments
Β (0)