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 46ebbf9
Browse filesBrowse the repository at this point in the historyBrowse files
📝 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
Copy file name to clipboardExpand all lines: architecture.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
@@ -1263,7 +1263,9 @@ workflow capability is absent.
1263
1263
Replay rehydrates the Effection tree. A completed durable effect restores its
1264
1264
recorded result without executing again. Ephemeral operations run again only to
1265
1265
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
1267
1269
result returns without attaching any provider.
1268
1270
1269
1271
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
2491
2493
whole-fragment preflight rather than inside the component after earlier elements
2492
2494
have run.
2493
2495
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.
2497
2502
2498
2503
### Typed candidate recovery around Evaluate
2499
2504
@@ -5341,7 +5346,7 @@ validation effectful.
5341
5346
5342
5347
## Construct inventory
5343
5348
5344
-
Status is measured against main.
5349
+
Status is measured against the revision containing this document.
5345
5350
5346
5351
| Construct | Does | Status |
5347
5352
| --- | --- | --- |
@@ -5370,7 +5375,7 @@ Status is measured against main.
5370
5375
| 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 |
5371
5376
| 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 |
5372
5377
| 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) |
5374
5379
|`getWorkflowRun()`| reads the run the current execution is associated with | built on the #366 stack |
5375
5380
|`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 |
5376
5381
|`GitQuery.resolve()`| verifies and resolves one Git revision expression contextually | built on main |
@@ -5397,7 +5402,7 @@ Status is measured against main.
5397
5402
|`ephemeral eval`| reconstructs live middleware and bindings without a journal entry | built on main |
5398
5403
|`useWorkflowServiceDenial()`| provides a non-delegating workflow service denial provider, installed inside every start and resume execution scope | built on the #366 stack |
5399
5404
|`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|
5401
5406
|`<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 |
5402
5407
|`<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 |
5403
5408
| 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 |
0 commit comments