Skip to content

Commit e921d6f

Browse files
committed
📄 Say what the contextual content answer does and does not guarantee
Two sentences claimed more than the code does. The language specification said a component whose two forms select different effects reads the authored form from its invocation. That describes `<File>` and `<Dir>` and nothing else: every other component reads the contextual operation, and saying otherwise reads as a rule the reader can rely on. It now states the boundary as it is — only the invocation's own `hasContent()` is authoritative, those two read it, and a component reading the contextual operation has no authored-form guarantee at all. The architecture said moving the remaining eleven consumers to the invocation is a follow-up, and that until it happens they are held to the weaker rule. A contract describes what is built, not what is planned. It now records only the present terms: those eleven read the contextual answer, so middleware may alter the effect, the guard or the retained data each of their branches decides, and this invocation boundary makes no stronger guarantee for them. Which consumer decides what is already enumerated beside it; the sequencing belongs in the handback. Documentation only: no source, test, assertion or test identifier changes. Refs #369
1 parent 9a69ea3 commit e921d6f

2 files changed

Lines changed: 10 additions & 7 deletions

File tree

‎architecture.md‎

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -2583,15 +2583,15 @@ the file the document wrote a read for.
25832583

25842584
The contextual operation stays exported and composable, and every other
25852585
component still reads it. That is not a statement that the remaining readers are
2586-
safe. Eleven of them branch on it today, and the branch decides more than how to
2586+
safe. Eleven of them branch on it, and the branch decides more than how to
25872587
render: `<Issue>` selects a read against an external upsert, `<Repository>`,
25882588
`<Worktree>`, `<TempDir>` and `<IssueTracker>` decide whether a context or a
25892589
working directory is installed for their descendants at all, `<Git.Add>`,
25902590
`<Git.Push>`, `<Git.Switch>` and `<Json>` turn a content-bearing invocation into
25912591
a refusal, and `<Git.Commit>` and `<PullRequest>` decide what body is committed
2592-
or published. Each is reachable by the same middleware on the same terms.
2593-
Moving them to the invocation is a follow-up rather than part of this boundary,
2594-
and until it happens the rule they are held to is the weaker one.
2592+
or published. Each reads the contextual answer, so middleware may alter the
2593+
effect, the guard or the retained data each of those branches decides, and this
2594+
invocation boundary makes no stronger guarantee for them.
25952595

25962596
**Which domain an invocation is in is decided by what resolution selected, not
25972597
by the name that was asked for.** An authored name is what a document wrote, and

‎specs/executable-mdx-spec.md‎

Lines changed: 6 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -3740,9 +3740,12 @@ It is a **contextual** operation, so it composes like the rest of this Api: a
37403740
handler installed anywhere outside the invocation answers ahead of the engine's
37413741
own account, and may answer differently on each call. A caller that reads it and
37423742
then invokes something which reads it again has therefore verified nothing —
3743-
the two are separate dispatches. A component whose two forms select different
3744-
*effects* reads the authored form from its invocation instead (§5.6), which no
3745-
handler reaches. `<File>` (§6.13) and the workflow package's `<Dir>` do.
3743+
the two are separate dispatches.
3744+
3745+
Only the invocation's own `hasContent()` (§5.6) is authoritative about the
3746+
authored form. `<File>` (§6.13) and the workflow package's `<Dir>` read it. A
3747+
component that reads this contextual operation has no authored-form guarantee:
3748+
what it receives is whatever the chain answered for that call.
37463749

37473750
`hasBinding()` reports the other half of the invocation's shape, and reports a
37483751
boolean only. `as` stays engine-owned: it is validated and stripped before the

0 commit comments

Comments
 (0)