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 1e44987
Browse filesBrowse the repository at this point in the historyBrowse files
✨ Capture the problems with <Json as>, and claim the directory before making it (#260)
Rebased onto `<Json as>` (#667), which supplies what the single-child `<Let>`
wrapper was standing in for. Both wrappers in the packaged prompt command
document are gone; `<Json value={check.diagnostics} as="problems" />` binds the
serialized text directly, and the bytes reaching `<CodeBlock>` are the same
bytes — the repair turn and the review presentation still carry the complete
structured problems, now proven by parsing the fence back rather than by
matching a substring of it.
The default session's directory is now a scope-owned resource rather than a
directory with an ensure attached afterwards. The release is registered before
the `mkdir` that could create it, so there is no window in which a leaf exists
that nothing is responsible for: a failure between making it and using it hands
it back like every other ending. What the release knows is whether the
directory was ever handed over, and that decides which question it is answering.
Once established, the exit has exactly two outcomes and no third. Still the
empty directory it was given, and the leaf is removed, non-recursively. Anything
else — content that appeared, or a directory that vanished — is preserved as
found and fails the command terminally. A leaf that disappears under a live
conversation was silently accepted before, which was wrong twice over: nothing
here is allowed to remove it, so its absence is interference, and treating
interference as a clean exit would let admission, the save and the execution
proceed on a conversation something else had already reached into.
A directory establishment never handed over is a different question, already
answered by what establishment reported. The release leaves that report and the
directory's contents alone, while still handing back an empty leaf it did
create.
Explicitly named directories are untouched by any of this: they stay, because
the next `--session` derives the same ACPX session identity from where they are.
Claude-Session: https://claude.ai/code/session_015HcqB9kJM9KFnMNToAuZF6
Copy file name to clipboardExpand all lines: architecture.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -36,7 +36,7 @@ Existing documents and code get aligned to this section retroactively.
36
36
| Prompt | a person's original request, in ordinary natural language. `xmd prompt` takes exactly one |
37
37
| Plan | the executable program produced from a Prompt: an Executable Markdown document combining readable prose that expresses the Prompt's intent with the components that carry it out, each placed beside the prose describing what it does. A Plan is what `xmd prompt` approves, optionally saves and runs; it is not a synonym for a workflow, a policy document or any executable Markdown file |
38
38
| prompt command document | the one exact checked-in first-party Markdown value root `xmd prompt` executes to convert a Prompt into a Plan. It implements that conversion and its review workflow — the request wording, the draft and repair loops, the check branches, human review, revision, approval, abort and exhaustion — and returns the exact approved Plan source. It is not itself a Plan. Internal: no command-line option selects another one, and no repository component search can answer for it |
39
-
| prompt profile | the trusted-host assembly used only for the prompt command document: its fixed inputs, a constrained Agent provider, Elicitation, the fixed first-party components and the host-declared draft validator. It uses no repository component search and exposes no custom root, and the ceiling it establishes is not readable from the command line. Its working directory is one host-owned directory dedicated to the logical prompt session, keyed by the digest of that name, created empty and required to be empty on the way in. An explicitly named session's directory is durable, because continuation derives the same session identity from it; an invocation-unique default session's is scope-owned, and exactly one cleanup is attempted after profile teardown and before admission on every ending — the leaf removed non-recursively when still empty, and preserved whole with the command failing terminally when it is not. Where those directories live is a host dependency no caller or document selects |
39
+
| prompt profile | the trusted-host assembly used only for the prompt command document: its fixed inputs, a constrained Agent provider, Elicitation, the fixed first-party components and the host-declared draft validator. It uses no repository component search and exposes no custom root, and the ceiling it establishes is not readable from the command line. Its working directory is one host-owned directory dedicated to the logical prompt session, keyed by the digest of that name, created empty and required to be empty on the way in. An explicitly named session's directory is durable, because continuation derives the same session identity from it; an invocation-unique default session's is scope-owned, claimed before it is created, and exactly one cleanup is attempted after profile teardown and before admission on every ending — the leaf removed non-recursively when it is still the empty directory that was handed over, and left as found with the command failing terminally when it has gained content or vanished. Where those directories live is a host dependency no caller or document selects |
40
40
| expansion | one logical evaluation of an authored executable element within a document execution |
41
41
| expansion ID | a deterministic identifier for one logical expansion; restoring or retrying that expansion preserves the ID, while a distinct evaluation requested by the document receives another |
42
42
| Git capability | the contextual interface through which workflow infrastructure queries the Git repository associated with the current working directory |
0 commit comments