Skip to content

Commit 46ebbf9

Browse files
committed
📝 Say what this workflow does, now that it does it
The living workflow, its two specifications and `architecture.md` still read like construction notes: a status line calling the whole thing an end-goal target and an inventory measured against `main`, a paragraph saying #301 slice 2 owes the composition, table rows calling the adversarial loop and mutation-proposal admission unbuilt, a Workspace specification saying the Git operations of §7 are not built, a runtime document opening with the claim that the repository, worktree, process and working-directory capabilities are not there yet, an Agent ceiling described as a read/search permission bridge inside a native read-only sandbox, replay re-registering Agent directories that are never registered, and four documents insisting that nothing schedules a resume. Every one of those was true of an earlier revision and is false of this one, which So the documents describe the revision containing them. The composition, the Repository and Worktree topology, the generated observation and mutation admission, the Git and Git-host effects and the durable checkpoints are stated as built — with the one real exclusion beside them, which is that a generated fragment admits no workflow-bundled Markdown component. The Agent ceiling is the profile that ships: an empty provider-owned directory, no additional directory, no MCP server, an empty requested tool set, deny-all, and a native permission request denied and failing its turn, with #496 kept as the explicit nonclaim about portable adapter-level tool absence. Replay reattaches that profile's own session arrangement rather than a directory nobody registered. Delivery executes nothing, and a continuation is asked for — by a person, or by a trusted host deciding *when* through the scheduler #300 built. Both take the same executor lock and run the same path, and no watcher, delivery-to-resume wiring, unattended arbitration or second executor exists. The specification's last construction-era section goes with them. What stood under "Open" was four boundaries this composition already runs inside and one question about somebody else's filesystem; they are recorded as settled boundaries, generated Git, Git-host, issue, process, execution, credential and external-write effects are stated as outside admission rather than as a class still to be decided, and the exercise framing that asked a reader to resolve enough of them for one vertical slice is gone. What this workflow does not do is now written down as such. Worker Shell stays out-of-band inspector and a lab or `xmd play` surface are nonclaims with their reasons, not roadmap promises; #227 owns the host filesystem's validate-then-use guarantee, which a provider-owned Workspace namespace never races, and #327 owns the outer `<PrintErrors>`/`<Output>` correction, which this workflow writes no region for. The issue map records what each issue delivered: #290 and #301 implemented on PR #181 and closing with its merge, #300's explicit scheduling shipped beside the exclusion it is not, undefined-prop omission shipped by #537 and #541, and Two corrections are about ownership rather than status. `<Worktree>` is self-closing: it creates or restores the named checkout and binds its path, renders no children and establishes no working directory, and the lexical `<Dir>` consumes that binding and owns cwd. The shared Git-host reconciliation stands behind Push and PullRequest, while `<Issue>` reconciles through its own provider-neutral `IssueApi`. `SYNC1` keeps them honest, beside AC0–AC7 rather than inside them. It is a source-truth case: a small table of what each owned document must say and the claims none of them may make again, matched against the flattened text so it is about sentences rather than line breaks. Restoring any one of those claims fails it. It supplements semantic review and does not replace it. SCH9's reviewed blobs move with the documents this synchronization edited, under independent Planner review, and its `525efaa7` over `170a021d` provenance is untouched. Claude-Session: https://claude.ai/code/session_01MNztk1fikXUnD2FW4yS6Kr
1 parent 9e1f0c2 commit 46ebbf9

12 files changed

Lines changed: 470 additions & 189 deletions

‎architecture.md‎

Lines changed: 12 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -1263,7 +1263,9 @@ workflow capability is absent.
12631263
Replay rehydrates the Effection tree. A completed durable effect restores its
12641264
recorded result without executing again. Ephemeral operations run again only to
12651265
rebuild live structure: attach the Workspace, enter lexical working-directory
1266-
scopes, attach providers and re-register Agent directories. A completed root
1266+
scopes, and attach providers — including the Agent profile's own session
1267+
arrangement, which is a provider-owned empty directory and a retained session
1268+
mapping rather than a directory registered with an Agent. A completed root
12671269
result returns without attaching any provider.
12681270

12691271
The Workspace stores the current frontier state. The journal stores the
@@ -2491,9 +2493,12 @@ identities and the constraint travels with the pinned one, decided in the
24912493
whole-fragment preflight rather than inside the component after earlier elements
24922494
have run.
24932495

2494-
Mutation-proposal admission and workflow-bundled Markdown component admission
2495-
remain unbuilt. Directory registration is not among them: a workflow Agent is
2496-
given no directory to register.
2496+
Mutation-proposal admission is built (#369, delivered by #572): a generated
2497+
fragment's paired `<File>`, lexical `<Dir>` and self-closing `<File.Delete>` are
2498+
admitted by class and authored form, and each admitted element runs as the
2499+
ordinary component it is. What remains unbuilt beside it is workflow-bundled
2500+
Markdown component admission — a generated fragment names none. Directory
2501+
registration is neither: a workflow Agent is given no directory to register.
24972502

24982503
### Typed candidate recovery around Evaluate
24992504

@@ -5341,7 +5346,7 @@ validation effectful.
53415346

53425347
## Construct inventory
53435348

5344-
Status is measured against main.
5349+
Status is measured against the revision containing this document.
53455350

53465351
| Construct | Does | Status |
53475352
| --- | --- | --- |
@@ -5370,7 +5375,7 @@ Status is measured against main.
53705375
| source-bundle workflow definition | version 2 of the workflow definition is the exact bytes themselves: an entrypoint, a canonically ordered manifest of logical paths with each source's domain-separated SHA-256 and byte length, a bundle hash over that manifest and mapping, and the optional exact target and component mapping. The bytes are retained with the run in live schema version 2, so starting, resuming, replaying, forking and exporting need no repository and survive the original being edited, moved or deleted | built on the #443 stack; version 1 is unchanged, nothing migrates between them, and the artifact-backed fork remains unbuilt |
53715376
| installed structural syntax | a trusted host declares a structural construct and the regions written directly inside it, as the second arm of the same `declarations` list: name, origin, accepted forms, props schema, syntax examples, description, what the content means, and `parent` — `null` for the construct, the construct's name for one of its regions. The accepted regions are derived from the regions that named the construct rather than restated by it. The installation that declares them supplies the one `expand` handler, read once and bound at capture, and held on the admitted catalog entry rather than in any registry, context or second dispatch protocol. Admission refuses an invalid name, an empty origin, absent or non-canonical forms, an uncompilable schema, missing syntax examples or description, a context that is neither prose nor `null`, a name the engine's structural table or the canonical protected tier owns, a name a reserved registration claims, a duplicate across either arm or across installations, a collision with a private closure name, an orphan region, a region of a region, a pair split across two installations, a construct with no region, declarations with no handler, and a handler with no declarations — all of it before the root document is read. Resolution places a declared construct in the host tier beside declared Markdown; `inspectComponent()`, `inspectSyntax()` and document validation describe and check it from the same catalog, with the structural entries sorted by code point beside the engine's own and the symbols unchanged at version 2. Expansion asks the catalog after every engine branch and before component import, settles placement, forms, `as`/`slot` and every construct and region prop, and then calls the captured handler once inside its own scope with a frozen request. Each region is an operation whose subscription owns one demand-driven producer: a chunk is delivered only to a waiting read, authored work waits for the read that permits it, output never reaches `DocumentOutput` or the journal, and leaving the handler's scope halts and joins every producer it entered | built on the #806 stack |
53725377
| declared Markdown component | a trusted host declares exact first-party Markdown to one execution as immutable data on an `ExecutionInstallation`, built with `Markdown({…})`: the host states the name, origin, source, its SHA-256, the accepted forms, an optional statement of the props and return that must agree with the parsed source, and an optional private component closure, and the constructor returns a fresh declaration carrying the required `kind: "component"` written after that description. It validates, hashes, copies and freezes nothing. Admission reads the kind before any other member and refuses a missing, unknown or superseded one — including the `"markdown"` earlier versions stated — rather than reading the value as Markdown, then parses the bytes and refuses a mismatched digest or schema, a non-canonical form, a name that is not a component name or is structural, a duplicate, a reserved-registration collision and a private name a registration also claims. Resolution places it in the protected tier with reserved registrations, above the workflow component bundle, repository files and every registered default. Live import and retained history are held to the declared origin, digest and bytes, private names resolve only while canonical core expands the declaring bytes' own body — by the authored occurrence rather than by the name, so an answer kept from a legitimate private import authorizes no later site, no alias, no copy of the definition, no invocation that is over and no later execution — including one that declares no Markdown at all — while a private name written anywhere else resolves to nothing before the bundle, the repository or a registration can answer for it — and `xmd syntax` and document validation describe the declared contract from the same declaration without describing the closure. Closure is per name: only the declared component and its private closure become canonical imports, and every other name in the execution stays the ordinary open import middleware may still answer | built on the #660 stack; no public component uses it yet (#660 PR 2) |
5373-
| workflow component bundle | a workflow root declares a closed set of authored Markdown components; the workflow definition optionally carries them as one canonically ordered array, and an absent member identifies a run closed over no components — so a definition closed over none identifies exactly that. An entry maps the name onto a logical path the same source bundle retains. `start` reads every component from beside the root and retains it, and `resume` executes the closure the lifecycle authenticated; the array takes part in definition identity and is compared as part of the same descriptor in compatible reuse; and canonical core resolves those names and holds both live import and retained history to that exact bundle | built on the #301 stack; the full adversarial implementation loop and its scheduling remain unbuilt (#300), and generated XMD admits no bundled Markdown component (#369) |
5378+
| workflow component bundle | a workflow root declares a closed set of authored Markdown components; the workflow definition optionally carries them as one canonically ordered array, and an absent member identifies a run closed over no components — so a definition closed over none identifies exactly that. An entry maps the name onto a logical path the same source bundle retains. `start` reads every component from beside the root and retains it, and `resume` executes the closure the lifecycle authenticated; the array takes part in definition identity and is compared as part of the same descriptor in compatible reuse; and canonical core resolves those names and holds both live import and retained history to that exact bundle | built on the #301 stack; the complete adversarial implementation loop is built in this revision; explicit host scheduling of its ordinary resume is built by #300, and generated XMD admits no bundled Markdown component (#369) |
53745379
| `getWorkflowRun()` | reads the run the current execution is associated with | built on the #366 stack |
53755380
| `retainedWorkflowInstallation()` | associates one document execution with a run storage already created, requiring exact journal agreement. It resolves no revision and names no Git feature, and a run retains the bytes it executes, so nothing afterwards reaches a repository for its source | built on the #366 stack |
53765381
| `GitQuery.resolve()` | verifies and resolves one Git revision expression contextually | built on main |
@@ -5397,7 +5402,7 @@ Status is measured against main.
53975402
| `ephemeral eval` | reconstructs live middleware and bindings without a journal entry | built on main |
53985403
| `useWorkflowServiceDenial()` | provides a non-delegating workflow service denial provider, installed inside every start and resume execution scope | built on the #366 stack |
53995404
| `xmd workflow start` / `xmd workflow resume` | starts or resumes a workflow run from the CLI, under the Deno entrypoints only | built on the #366 stack; both acquire #367's executor lock before any lifecycle transition |
5400-
| implicit workflow Workspace | retains provider-neutral filesystem, repository and attachment state by run ID | document filesystem built on the #366 stack and Repository/Worktree composition on the #293 stack; process capabilities unbuilt (#218) |
5405+
| implicit workflow Workspace | retains provider-neutral filesystem, repository and attachment state by run ID | document filesystem built on the #366 stack and Repository/Worktree composition on the #293 stack; a command the document runs executes under the run and its result is retained with it, so a continuation reads the result back rather than running the command again |
54015406
| `<Repository>` / `<Worktree>` composition under a workflow run | names a Git repository and its linked checkouts inside the run-owned Workspace, installs each as contextual working directory, and retains creation identity beside the retained Git bytes | built on the #293 stack, Deno provider only |
54025407
| `<Dir path>` | asks the mandatory provider-neutral `API.Files.ensureDirectory` operation to recursively create or adopt its target before content begins, then expands content with that target as cwd. Relative paths resolve from the enclosing cwd and absolute paths keep their existing meaning; an existing directory and its contents are preserved, a file or special target refuses before content, and the enclosing cwd is restored on success, failure and cancellation without deleting what was created. Dir changes cwd only and leaves the Repository selection untouched | directory-creation contract added by #643; host and workflow Files providers |
54035408
| transactional Git effects (`Git.Switch` / `Git.Add` / `Git.Commit`) under a workflow run | publish local Git mutations with their journal result; the enclosing Repository and the contextual working directory select which retained checkout one runs in, and neither observation admits anything — the observed record is compared with the retained row and the directory with the checkouts that row holds, so a failure of admission, of retained state or of an unrecognized native condition fails the run instead of publishing a result | built on the #294 stack, Deno provider only |

‎packages/cli/tests/workflow-scheduling.test.ts‎

Lines changed: 16 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -1014,40 +1014,41 @@ const REVIEWED_CONSUMER_ROOTS = [
10141014
* name the base at all.
10151015
*
10161016
* The provenance below is unchanged: this slice was reviewed on PR #181 head
1017-
* `525efaa7` over `170a021d`, and it still is. Two of these blobs have moved
1018-
* since, and only through a repair reviewed in its own right — #299's R3
1019-
* corrected the observation instruction the Implementation stage renders, and
1020-
* extended AC2 to send it, so the workflow document and the composition suite
1021-
* each hold one approved change. Pinning what they hold now is what keeps this
1022-
* case a statement about *this* slice changing them rather than a statement
1023-
* about nobody changing them.
1017+
* `525efaa7` over `170a021d`, and it still is. What has moved since are blobs,
1018+
* and only through work reviewed in its own right — #299's R3 corrected the
1019+
* observation instruction the Implementation stage renders and extended AC2 to
1020+
* send it, and #292's final synchronization then made the workflow documents
1021+
* describe the delivered revision and added `SYNC1` beside AC0–AC7, each under
1022+
* independent Planner review. Pinning what those files hold now is what keeps
1023+
* this case a statement about *this* slice changing them rather than a
1024+
* statement about nobody changing them.
10241025
*/
10251026
const REVIEWED_CONSUMER: readonly (readonly [string, string])[] = [
10261027
[
10271028
"scripts/tests/adversarial-composition-workflow.test.ts",
1028-
"bb942b506d67431b1621c99ea3e08242a62f77cf",
1029+
"adf7e58e609c116e2f93fb97e3592bc70756f24b",
10291030
],
10301031
["workflows/adversarial-implementation/Discovery.md", "eea1c650fe5a9d417595b9b457b73dc51485f05a"],
10311032
[
10321033
"workflows/adversarial-implementation/Implementation.md",
1033-
"c38076574eae1b55304eade578480f8efbdf3f4b",
1034+
"65333321a163f125d6021f807ac14108e049deac",
10341035
],
10351036
[
10361037
"workflows/adversarial-implementation/InstructionFiles.md",
10371038
"7ce93d7c1b7f79c560c9a861f27e7597697724d9",
10381039
],
1039-
["workflows/adversarial-implementation/Planning.md", "cc3b3f473da35c94a8fba541afc20536a8fe3d19"],
1040+
["workflows/adversarial-implementation/Planning.md", "943cb9701e3f4a464f13606547ca319e770aecf3"],
10401041
[
10411042
"workflows/adversarial-implementation/UserCheckpoint.md",
1042-
"54f1e97bbee1890fe77ec7b3e19277031cc101d3",
1043+
"576e352ac232426c157a33be964402d600a545bc",
10431044
],
1044-
["workflows/adversarial-implementation/artifacts.md", "dd8462a76d604f14cd9eeeb618faa8f6bfa24664"],
1045+
["workflows/adversarial-implementation/artifacts.md", "98899d95b70286851c08b5ccb10e26fd7b20e17e"],
10451046
[
10461047
"workflows/adversarial-implementation/primitives.md",
1047-
"17a89b9c5474a8ebb41964a016213ecfcc032b96",
1048+
"9e66ca0df27608a3c2a6f2887db5b7cb4ed1e34a",
10481049
],
1049-
["workflows/adversarial-implementation/runtime.md", "f13cb034b1321860916a48e5c80d205b3f7bcb6a"],
1050-
["workflows/adversarial-implementation/start.md", "0e248182f89a3b4fe3a1d1e316e239c4195ce3f0"],
1050+
["workflows/adversarial-implementation/runtime.md", "128fb2c1337b5d78890ebc05dcfe79f7416d7f3c"],
1051+
["workflows/adversarial-implementation/start.md", "b898f95188e5e1940e0e483a9ce74e69c49a53f2"],
10511052
[
10521053
"workflows/adversarial-implementation/tests/agents/checkpoint-material-choice.md",
10531054
"c126bdfe64c227c381317bf12338e235c52e78b5",

0 commit comments

Comments
 (0)