@cratis/pi 7.127.0 → 7.129.0

package/package/corpus/skills/cratis-screenplay-command-surface/SKILL.md

@@ -105,11 +105,12 @@ fix to migrate. `--warnaserror` does not reject information diagnostics.
 properties, `reads`, `authorize`, `validate`, `produces`/`handler`, `concurrency`.
 Keep to it.
 
-A file/code `handler` cannot coexist with `produces` and fails binding
-with PLAY0800 (`CommandHandlerRequiresAttachment`): gap-fill the slice in code
-with a constrained implementation attachment, not by waiting for a new ESM version.
+A file/code `handler` beside unconditional `produces`, with a resolved nonempty body,
+binds as the v23 result contract: `produces` fixes the
+events and the body owns their property values. Without `produces`, with `produces ... when`,
+or with an unresolved body it fails binding with PLAY0800 (`CommandHandlerRequiresAttachment`).
 Read the required typed `subject` argument for the command, never parse the message.
-Requires Screenplay 4.210.0 (`screenplay --version`) for PLAY0800; older binders use PLAY0268 for this refusal. A pending `handler implementation` beside unconditional `produces`
+Requires Screenplay 4.250.0 (`screenplay --version`); 4.210.0 to 4.249.x refuse every attached handler with PLAY0800 and older binders use PLAY0268. A pending `handler implementation` beside unconditional `produces`
 is a described command (ESM v23): the body owns payload values only. Prefer plain
 `produces` for declarative logic. Read [described handlers](references/described-handlers.md)
 when logic needs prose, for the result contract, PLAY0695–0698, Unsupported

package/package/corpus/skills/cratis-screenplay-command-surface/references/described-handlers.md

@@ -32,13 +32,17 @@ module Invoices
 
 A pending `implementation` has no `file` or fence. Bare `implementation` is valid;
 optional `hint` lines are ordered, nonblank quoted strings, decoded without trimming.
-One wrapper and at most one payload are permitted. Attaching a file or fence stops
-being a described command: attached handlers fail binding with PLAY0800
-(`CommandHandlerRequiresAttachment`) and cannot coexist with `produces`.
-This permanent limitation requires a constrained implementation attachment:
-gap-fill the slice in code, not by waiting for a supported ESM version.
-
-Requires Screenplay 4.210.0 (`screenplay --version`) for PLAY0800 and its required typed `subject` declaration argument naming the command; older binders use PLAY0268. Hosts switch on the code and read `arguments.subject`, never parse the message.
+One wrapper and at most one payload are permitted. Attaching a file or fence makes it
+an attached handler. Beside unconditional `produces`, with a resolved, nonempty,
+language-tagged body, it binds with the same v23 result contract (Screenplay 4.250.0,
+decision 0117): the productions fix event types, count, order and destinations, and
+the body owns property values. Reaching the body in reference execution is Unsupported
+(`ImplementationBody`) and appends nothing. An attached handler with no `produces`,
+with `produces ... when`, or with an empty or unresolved body fails binding with PLAY0800
+(`CommandHandlerRequiresAttachment`): declare unconditional `produces`, split variable
+outcomes into separate commands, or attach a resolved body.
+
+Requires Screenplay 4.250.0 (`screenplay --version`) for attached handlers beside `produces` to bind; 4.210.0 to 4.249.x refuse every attached handler with PLAY0800, and older binders use PLAY0268. Hosts switch on the code and read `arguments.subject`, never parse the message.
 
 ## Result contract v1
 
@@ -61,7 +65,7 @@ explicitly admit this version, never silently drop the body.
 
 | Diagnostic | Meaning and action |
 | --- | --- |
-| PLAY0800 (error) | File/inline handler requires a constrained implementation attachment; `subject` identifies the command to gap-fill |
+| PLAY0800 (error) | File/inline handler without unconditional `produces` or a resolved, nonempty body; `subject` identifies the command |
 | PLAY0695 (information) | Described command admitted; command and RequirementId name the missing body |
 | PLAY0696 (error) | No productions, including response-only; add unconditional productions |
 | PLAY0697 (error) | Conditional productions; result v1 needs unconditional events |

package/package/corpus/skills/cratis-screenplay-command-surface/references/validate-rules.md

@@ -98,11 +98,11 @@ validate
 
 A bodied rule or fenced block on a validation, rule or policy binds as opaque code
 (ESM v3): the reference runner reports it unsupported, and a target must supply the
-implementation. Attached command handlers refuse PLAY0800 and require constrained
-implementation attachments; `file` constraints retain PLAY0268 (only `unique`
-constraints bind). Requires Screenplay 4.210.0 (`screenplay --version`) for the
-handler's PLAY0800; older binders use PLAY0268. Pending command handlers beside unconditional
-`produces` instead bind as described commands; see [described handlers](described-handlers.md).
+implementation. Attached command handlers bind beside unconditional `produces` with a
+resolved body (Screenplay 4.250.0) and otherwise refuse PLAY0800; `file` constraints
+retain PLAY0268 (only `unique` constraints bind). Pending and attached command handlers
+beside unconditional `produces` share the v23 result contract; see
+[described handlers](described-handlers.md).
 Literal text rules, portable patterns and Studio desugaring: [text and match rules](text-and-match-rules.md).
 Stage renders pure reducer transitions and opaque policy bodies, but refuses command and
 concept code validations and rule predicates (STAGE-ESM-005): those are gap-fill code. Prefer a

package/package/corpus/skills/cratis-screenplay-command-surface/verification.json

@@ -52,7 +52,7 @@
     },
     {
       "kind": "skill-contains",
-      "value": "A file/code `handler` cannot coexist with `produces`"
+      "value": "A file/code `handler` beside unconditional `produces`, with a resolved nonempty body,"
     },
     {
       "kind": "skill-contains",

package/package/corpus/skills/cratis-screenplay-event-modeling/references/nine-steps.md

@@ -274,11 +274,14 @@ module Invoicing
       specification IssuingOnMonday
         given clock "2026-10-05T07:00:00Z"
         when clock "2026-10-05T07:30:00Z"
-        then CollectionsDigestIssued
-          for "weekly"
-          issuedAt = "2026-10-05T07:30:00Z"
+        then invokes IssueCollectionsDigest
+          period = "weekly"
 ```
 
+Each slice proves its own link (Screenplay decision 0115): the automation states the
+command it invokes with `then invokes` (ESM v34), and `IssuingTheDigest` in the command's
+slice states `CollectionsDigestIssued`.
+
 At the example's verified Screenplay version, iterating the overdue items needs code (a clock trigger reads the whole view and takes
 no `by`); see `cratis-screenplay-automations-and-translations`. A reaction that `produces`
 directly while it `reads` fails binding (`PLAY0268`): decide in a command instead.

package/package/corpus/skills/cratis-screenplay-legacy-extraction/references/generated-recovery.md

@@ -178,9 +178,9 @@ resolved adapter version, diagnostic, retained/withheld form and open question:
 `MaximumExecutableModelVersion` below v15 withholds non-default concept generation
 with SP0073 and dependent values/responses/mappings with SP0052; pins against them
 withhold scenarios with SP0039. Below v7 responses/return expectations are withheld.
-A cap describes less behavior, not an equivalent implementation. Handler references
-compile but refuse executable binding (PLAY0800 for file/inline command handlers);
-record that verdict separately and gap-fill the slice with a constrained implementation
-attachment, not by waiting for ESM admission.
+A cap describes less behavior, not an equivalent implementation. A file/inline command
+handler binds only beside unconditional `produces` with a resolved body (Screenplay
+4.250.0); otherwise it refuses executable binding with PLAY0800. Record that verdict
+separately and gap-fill the slice in code.
 Requires Screenplay 4.210.0 (`screenplay --version`); older binders use PLAY0268 for these handlers.
 Never remove protection, required payloads or loss rows to obtain a green result.

package/package/corpus/skills/cratis-screenplay-model-authoring/references/language-reference.md

@@ -257,7 +257,7 @@ See read-surface `references/named-keys.md` for the collection-key exclusion alg
 | Disposition | Constructs |
 | --- | --- |
 | Binds and runs in the reference runner | `StateChange`/`StateView` slices; `produces` including `when` conditions over command properties and literal tags; the portable validation rules, `matches email`, quoted `matches` patterns and `require` over command properties; declarative policies and `authorize` on modules, features, commands and keyed queries; `unique` constraints; projections as Chronicle lowers them, including variants, except the projection constructs in the next row; specifications, including `given caller`, `then denied` and `when append` |
-| Binds, but the reference execution plan refuses it | A projection-level `remove via join`; `all` beside removals, `children` or `nested`; a `join`, `children` or `remove via join` inside `nested`; any event-context value other than the event source identity in a projection mapping or key, such as `$eventContext.occurred`, `$eventContext.sequenceNumber` or `$eventContext.causedBy.subject` (`$eventSourceId` and `$eventContext.eventSourceId` run) |
+| Binds, but the reference execution plan refuses it | A projection-level `remove via join`; `all` beside removals, `children` or `nested`; a `join`, `children` or `remove via join` inside `nested`; any event-context value other than the event source identity and occurrence time in a projection mapping or key, such as `$eventContext.sequenceNumber` or `$eventContext.causedBy.subject` (`$eventSourceId` and `$eventContext.eventSourceId` run; `$eventContext.occurred` runs in `from`, `every` and `children` blocks for facts appended during the run under `given clock`, while a `given` fact carries no occurrence time and reports Unsupported) |
 | Binds as ESM v6 (`PLAY0268` on a compiler that stops before v6) | `Automation` and `Translate` slices, reactions that produce or invoke, captures, top-level `trigger`, clock, trigger and capture specifications. The standalone `screenplay test`/MCP reference route evaluates admitted v6 actions; Stage renders supported event-triggered Automation, with remaining refusals in the Stage skill's `references/admission.md` |
 | Reaction with trigger `reads` | Direct-producing (or code-bodied) reaction with `reads`: `PLAY0268` ("ESM v6 cannot protect that decision dependency"), non-executable. Invokes-only reaction with `reads`: information only; the invoked command must declare and protect its own decision reads. Keep the `reads`; never remove them to obtain binding |
 | Binds as opaque code (v3); reference runner reports unsupported | Bodied reducers, bodied named rules, fenced `validate` blocks, code or file policies. A pure reducer body is the only attachment Stage admits |
@@ -279,7 +279,7 @@ See read-surface `references/named-keys.md` for the collection-key exclusion alg
 | Chronological command dates (ESM v26) | Same-primitive Date/DateTime `==`, `!=`, `>`, `>=`, `<`, `<=` in require/produces-when (property or literal RHS) and command/property rules (literal RHS only). DateTime uses UTC ticks, participating offset-less inputs reject Validation before rules; then matching stays ordinal. Requires Screenplay 4.199.0 (`screenplay --version`); older binders refuse PLAY0268. The Stage Host and executor run v26 (older Stage refuses STAGE-ESM-016); the renderer and legacy engines refuse STAGE-ESM-046 (toolchain `language-admission.md`). Read command-surface `references/date-comparisons.md`. |
 | Current routing and actor admission | Sources/streams and command/specification routes bind and reference-execute as v8; reaction `runs as system role` supplies the invocation actor as v10. Whole-workspace binding determines executable availability; CLI/Stage realization remains separate |
 | Blocks binding (`PLAY0268`) | enum/identity compliance and events combining personal or explicitly subject-scoped secret values with explicit subject marks; a compiler that stops before v13 refuses all `pii`/`secret` concepts ("compliance attributes require portable data-subject semantics"), while v13 binds them and Stage renders protection; bare `rule <Name>`, read paths without protected opt-in or in unsupported positions such as `produces when`, date comparisons with mixed primitives, optional condition operands, `$context`, protected read paths or `today`, date rules on concepts or reaction `where`, `$context.tenant`/claims/roles/causation in `produces`, `$env` conditions, `file` constraints, unquoted `import` of an external contract, a read model with neither explicit `key` nor unambiguous query-based identity as described above (several key marks bind as v27; older binders refuse PLAY0268; toolchain `language-admission.md`), queries with context `from` sources (typed query context is unadmitted), single-result filters (collections only), `scoped to` (opaque scope) or a `by` block on a list query or non-optional single result (a `performer` query is not refused: it is an opaque read, PLAY0270, left out of the executable model; [version gate](../../cratis-screenplay-toolchain/references/executable-subset.md#code-attachments-what-binds-what-never-does)); optional keyed and collection queries, including caller-supplied equality filters and observable delivery, bind, `$causedBy` and templates in projections |
-| Blocks binding (`PLAY0800`, permanent attachment requirement) | Attached file/inline command `handler`: gap-fill the slice with a constrained implementation attachment, not by waiting for ESM admission. PLAY0035 beside productions; pending described intent instead binds v23. Read required typed `arguments.subject` for the command, never parse the message. Compiler prerequisite and older PLAY0268 attribution: [diagnostic arguments](../../cratis-screenplay-toolchain/references/diagnostic-arguments.md) |
+| Blocks binding (`PLAY0800`) | Attached file/inline command `handler` with no unconditional `produces`, with `produces ... when`, or with an unresolved body. Beside unconditional `produces` with a resolved body it binds as the v23 result contract, and pending described intent also binds v23 (command-surface `references/described-handlers.md` has the compiler gate). Read required typed `arguments.subject` for the command, never parse the message. Compiler prerequisite and older PLAY0268 attribution: [diagnostic arguments](../../cratis-screenplay-toolchain/references/diagnostic-arguments.md) |
 | Blocks binding (`PLAY0271`, legacy meaning) | Command reads without protected opt-in and `concurrency`; combined protected reads/concurrency is PLAY0783 |
 | Deferred (`PLAY0269`, information) | Screens, layouts, templates, forms, contributions, UI profiles, themes, behaviors and `on`/`uses` |
 | Metadata only (`PLAY0270`, information) | `domain`, `seed`, `persona`, trigger and other descriptions, and `file` provenance on declarations |

package/package/corpus/skills/cratis-screenplay-read-surface/references/named-keys.md

@@ -183,7 +183,9 @@ module Billing
         when append PaymentRemoved
           invoice = "INV-1"
           method = "card"
-        then no readmodel PaymentTotals for {"invoiceId":"INV-1","method":"card"}
+        then no readmodel PaymentTotals for
+          invoiceId = "INV-1"
+          method    = "card"
         then readmodel PaymentTotals
           invoiceId = "INV-1"
           method = "cash"

package/package/corpus/skills/cratis-screenplay-read-surface/references/screen-patterns.md

@@ -83,7 +83,7 @@ module Berths
           berth BerthName = berth
       screen BookBerthScreen
         title "Book a berth"
-        action BookBerth
+        action BookBerth for screen
           navigate to OpenBookingsScreen
       specification BookingABerth
         given caller
@@ -115,7 +115,7 @@ module Berths
       screen OpenBookingsScreen
         title "Open bookings"
         data OpenBooking[] via query ListOpenBookings
-        action BookBerth
+        action BookBerth for screen
 ```
 
 ## What a screen pattern is not

package/package/corpus/skills/cratis-screenplay-render-and-gap-fill/SKILL.md

@@ -42,10 +42,10 @@ mode; query-performer gaps are a separate contract, not completed behavior. Prot
 support is not generated-app protection.
 Preserve contracts; reference success is not target realization.
 
-File/inline command handlers permanently require constrained attachments: gap-fill
-in code, not by waiting for ESM admission. Requires Screenplay 4.210.0
-(`screenplay --version`) for PLAY0800 and required typed `arguments.subject`;
-older binders use PLAY0268. Read [renderability gate](references/renderability-gate.md)
+A file/inline command handler binds beside unconditional `produces` with a resolved
+body (v23 result contract, Screenplay 4.250.0); without them it refuses PLAY0800 with a
+required typed `arguments.subject`. 4.210.0 to 4.249.x refuse every attached handler
+with PLAY0800; older binders use PLAY0268. Read [renderability gate](references/renderability-gate.md)
 when classifying a handler or other binding refusal; never parse message text.
 
 Inline bodies (`csharp`, `typescript`, `react`, `html`, `sql`, `java`) are opaque and reach the target

package/package/corpus/skills/cratis-screenplay-render-and-gap-fill/references/renderability-gate.md

@@ -10,10 +10,11 @@ probe reports and choosing what to do. Do not copy the code table here.
 1. The CLI compiles and binds the **whole** model with its **bundled** Screenplay (the ESM level it renders is bounded by the bundle; older bundles bound less). Binding is never scoped:
    any binding error blocks even a `--scope` render. Binding errors are `PLAY0268` (outside the admitted vertical), `PLAY0269`
    (deferred), `PLAY0270` (report-only information), `PLAY0271` (legacy semantics) and `PLAY0273`
-   (a specification shape). File/inline command handlers instead report PLAY0800
-   (`CommandHandlerRequiresAttachment`), a permanent constrained-attachment requirement.
-   Requires Screenplay 4.210.0 (`screenplay --version`); older bundled binders use
-   PLAY0268 for these handlers. Hosts read the required typed `arguments.subject`
+   (a specification shape). A file/inline command handler without unconditional `produces`
+   or a resolved body instead reports PLAY0800 (`CommandHandlerRequiresAttachment`); beside
+   unconditional `produces` with a resolved body it binds as the v23 result contract.
+   Requires Screenplay 4.250.0 (`screenplay --version`); 4.210.0 to 4.249.x refuse every
+   attached handler with PLAY0800 and older bundled binders use PLAY0268 for these handlers. Hosts read the required typed `arguments.subject`
    to identify the command, never the message.
 2. Execution planning builds the plan and can emit `PLAN-*` diagnostics before Stage runs.
 3. Stage plans the target and admits or rejects each member: `STAGE-ESM-0xx`; profile and path
@@ -36,7 +37,7 @@ ESM). Only the probe answers renderability. `PLAY0270` entries are information,
 | --- | --- | --- | --- |
 | **Model fix (in mode)** | the model is in, or the user chose, renderable mode and breaks its own subset in a way that has a renderable equivalent with the same meaning | a `produces` whose `for` is not the command identifier; two projections for one read model (`-007`); a policy Stage cannot express portably (`-015`; role-only and opaque pure policies render) | edit request to the modeler session with address, change and rationale |
 | **Capability gap** | the intended meaning needs a construct Stage does not render yet | DateTime equality filters and required parameters after optional filters (`-010`); context/single-result filters, opaque `scoped to` and a list-query `by` block remain PLAY0268; an unsupported query performer (observable, a non-C# body, or a missing, changed or non-compiling body) becomes an explicit implementation gap, while a verified C# body renders ([performer bodies](../../cratis-screenplay-read-surface/SKILL.md#performer-bodies-are-rendered)); a read model with several key parts or a projection keyed by parts (v27) refuses `STAGE-ESM-048` (always for a DateTime or decimal key part; the decimal refusal lifts with Stage#847 once Chronicle#5427 lands) and a single-instance query by parts `STAGE-ESM-047` (Chronicle#4265); Translate, clocks, captures, non-event triggers and opaque reaction bodies (`-024`); claim-reading/opaque `runs as` gates (`-034`), legacy `from` (`-035`), mixed effects in one handler (`-037`, retries can duplicate events; keep it whole), unsupported reaction mappings (`-039`); unsupported generated types/result combinations (`-028`/`-038`); `then no readmodel` (`-027`); evolved events (`STAGE-ESM-026`); unsupported expression/enum production conditions (`-006`; supported conditional productions render); legacy reads (`PLAY0271`), protected reads the renderer cannot preserve, or any protected read in an older CLI bundle (STAGE-ESM-044 despite v25 admission; semantic Host/executor support is separate); code validation (`-005`); protected identities/enums (`-040`) or unadmitted explicit subject lineage (`PLAY0268`); described handlers (v23, STAGE-IMPL-002 even Stub mode), atomic mode (STAGE-ESM-043; v22 admission Requires Stage 4.139.0, older Stage reports -016) | keep the model; fallback record entry; options a to c in `SKILL.md`; link the Stage issue |
-| **Implementation attachment** | a permanent limitation, not future ESM admission | file/inline command handlers (PLAY0800; typed `subject` names the command) | keep the model contract and gap-fill the slice in code with a constrained implementation attachment; do not wait for a new ESM version |
+| **Implementation attachment** | the handler shape, not future ESM admission | file/inline command handlers without unconditional `produces` or a resolved body (PLAY0800; typed `subject` names the command) | declare unconditional `produces` beside a resolved body, split variable outcomes into separate commands, or keep the model contract and gap-fill the slice in code |
 | **Tool skew** | the bundled compiler disagrees with documented semantics | the false `PLAY0285` on reaction cascades from an older bundle; codes the standalone compiler does not raise | record in the session state and the fallback record; never "fix" a correct model |
 | **Environment** | not the model | restore failures, missing SDK, a destination that is not writable | fix the environment or report blocked |
 

package/package/corpus/skills/cratis-screenplay-scenario-coverage/SKILL.md

@@ -175,8 +175,8 @@ Use a separate `when added` append when initial observations should produce a fa
 Read captures-and-reactions `references/record-capture-specifications.md` for the
 prerequisite and runnable cases. Include first, changed and unchanged rows in the matrix.
 
-## Version skew: reaction cascades and false PLAY0285
-Under ESM v6 a command spec's `then` lists the events reactions cascade from it; an older `cratis` bundle reports a **false PLAY0285** for it. Never delete the reaction. Read [references/version-skew.md](references/version-skew.md) when a spec with cascade events reports PLAY0285 or the bundled compiler is older than the standalone tool.
+## Reaction chains: one slice per specification
+A specification runs only its own slice. Prove a chain across slices link by link: the command's spec states its own events, the Automation's `when append` spec states what it appends, and `then invokes <Command>` (ESM v34) states a command it invokes in another slice. Another slice's event in a spec is PLAY0285. Never delete the reaction. Read [references/version-skew.md](references/version-skew.md) when a spec reports PLAY0285 or the bundled compiler is older than the standalone tool.
 
 ## Gate
 A scope is spec-complete only when: the matrix has no `open`, `question` or `gap` cell (or the

package/package/corpus/skills/cratis-screenplay-scenario-coverage/references/invoicing-dues-design.md

@@ -203,9 +203,6 @@ module Invoicing
         then PaymentReversed
           for "9c1f0a52-6a4e-4b1c-9f55-0d2c7b8e1a01"
           amount = 130
-        then RefundRequested
-          for "9c1f0a52-6a4e-4b1c-9f55-0d2c7b8e1a01"
-          amount = 130
 
       specification RejectingAReversalWithoutAReceivedPayment
         given caller

package/package/corpus/skills/cratis-screenplay-scenario-coverage/references/invoicing-dues-example.md

@@ -227,9 +227,6 @@ module Invoicing
           for "9c1f0a52-6a4e-4b1c-9f55-0d2c7b8e1a01"
           outcome = "declined"
           reason  = "Card declined"
-        then PaymentDeclined
-          for "9c1f0a52-6a4e-4b1c-9f55-0d2c7b8e1a01"
-          reason = "Card declined"
 
     slice Automation RecordPaymentOutcome
       reaction ReceivedTranslator
@@ -247,6 +244,14 @@ module Invoicing
       event PaymentReceived
       event PaymentDeclined
         reason String
+      specification RecordingADeclinedPayment
+        when append PaymentGatewayResultReceived
+          for "9c1f0a52-6a4e-4b1c-9f55-0d2c7b8e1a01"
+          outcome = "declined"
+          reason  = "Card declined"
+        then PaymentDeclined
+          for "9c1f0a52-6a4e-4b1c-9f55-0d2c7b8e1a01"
+          reason = "Card declined"
 
     slice StateView OpenInvoices
       description "Todo list: membership means 'still to collect'; there is no status flag."

package/package/corpus/skills/cratis-screenplay-scenario-coverage/references/scenario-examples.md

@@ -104,9 +104,9 @@ design-mode rejection spec and `recorded` in the matrix. See `RejectingSettlemen
 in `invoicing-dues-design.md`; it is never prose and never a spec that pretends to enforce it.
 
 ## 3. External failure: the capture, then the retry
-Two separate obligations. First, the **capture specification**: concrete external input in, our
-facts out. The provider's refusal is a fact (never a `then error`), kept in the provider's
-vocabulary; a separate Automation records the local outcome. The capture uses
+Two separate obligations. First, the **capture specification**: concrete external input in, the
+provider's fact out. The provider's refusal is a fact (never a `then error`), kept in the provider's
+vocabulary; a separate Automation records the local outcome and states it in its own specification. The capture uses
 `when added` for first sight and a separate `when outcome` for updates. An update
 spec needs `given capture` with the same key's earlier record; the first record's
 fields are not modifications (root, child or nested). See captures-and-reactions
@@ -121,6 +121,15 @@ specification TranslatingADeclinedCardResult
     for "9c1f0a52-6a4e-4b1c-9f55-0d2c7b8e1a01"
     outcome = "declined"
     reason  = "Card declined"
+```
+The Automation that records the local outcome proves its own link in its own slice
+(a specification runs only its slice, Screenplay decision 0115):
+```screenplay excerpt parent=references/invoicing-dues-example.md#1
+specification RecordingADeclinedPayment
+  when append PaymentGatewayResultReceived
+    for "9c1f0a52-6a4e-4b1c-9f55-0d2c7b8e1a01"
+    outcome = "declined"
+    reason  = "Card declined"
   then PaymentDeclined
     for "9c1f0a52-6a4e-4b1c-9f55-0d2c7b8e1a01"
     reason = "Card declined"
@@ -153,9 +162,11 @@ model; it tests the projection only, never the translation.
 
 ## 4. Compensation
 A reversal needs a paid history, the reversal action and the exact consequence. The command spec
-lists the declared consequence (`RefundRequested`); the reaction is also specified on its own.
-`RefundRequested` is a recorded request, not proof that money moved, and there is no
-`then <Command>` form. What the target must do to deliver the refund is a requirement, not a spec.
+states the command's own fact (`PaymentReversed`); the `RequestRefunds` Automation states
+`RefundRequested` in its own specification, because a specification runs only its own slice
+(Screenplay decision 0115). `RefundRequested` is a recorded request, not proof that money moved.
+An automation that invokes another slice's command states it with `then invokes <Command>`
+(ESM v34). What the target must do to deliver the refund is a requirement, not a spec.
 From `invoicing-dues-design.md` (design mode; the specs do not run):
 ```screenplay excerpt parent=references/invoicing-dues-design.md#1 expect PLAY0516 test=unbound
 specification ReversingAReceivedPayment
@@ -174,9 +185,6 @@ specification ReversingAReceivedPayment
   then PaymentReversed
     for "9c1f0a52-6a4e-4b1c-9f55-0d2c7b8e1a01"
     amount = 130
-  then RefundRequested
-    for "9c1f0a52-6a4e-4b1c-9f55-0d2c7b8e1a01"
-    amount = 130
 
 specification RequestingARefundAfterAReversal
   when append PaymentReversed

package/package/corpus/skills/cratis-screenplay-scenario-coverage/references/spec-forms-by-mode.md

@@ -29,7 +29,8 @@ Typed example/override forms: `cratis-screenplay-specifications`
 | `when query` -> `then result` / `then no result` | yes | yes | same as `then query`: only the query-only cases below |
 | `given clock` / `when clock`, `when trigger`, record-source `given`/`when capture` | yes | yes (standalone and any cratis whose compiler admits v6; an older bundle does not, see toolchain `references/executable-subset.md`) | no |
 | Event-source capture fixtures | `given <FromEvent>` / `when append <FromEvent>`, not capture records (PLAY0701) | admitted root capture behavior executes; see `public-event-coverage.md` for prerequisites and limits | separate target admission |
-| Command spec listing reaction cascade events | yes (v6 semantics) | false PLAY0285 on an older cratis bundle only; see SKILL.md "Version skew" | no: STAGE-ESM-011; generated CommandScenario does not settle reactions |
+| Command spec listing its own slice's reaction cascade events | yes (v6 semantics) | yes; another slice's event is PLAY0285 (decision 0115); see SKILL.md "Reaction chains" | no: STAGE-ESM-011; generated CommandScenario does not settle reactions |
+| `then invokes <Command>` in an Automation spec | yes | yes, ESM v34 | Stage spec runner compares it; the Cratis renderer refuses models after v33 (STAGE-ESM-016) |
 | `generated <name> = <value>` under `when`, `then returns` (ESM v7) | yes | yes on a compiler that admits v7 (PLAY0268 on an older bundle) | yes on Stage for supported UUID/String strategies and v15 freshness and scalar/named responses; unsupported types/combinations remain -028/-038 |
 | v15 generation strategy fixtures and used-source rejection | yes | strict encoding/size/case/version/variant; Contract for invalid pins, Concurrency for reused source | supported strategies/freshness render; invalid pins refuse -011, unpinned unordered/projected assertions -038; source: command-surface `references/generated-values-and-responses.md` |
 | `then events in any order` | yes | yes | yes |
@@ -44,13 +45,13 @@ Typed example/override forms: `cratis-screenplay-specifications`
 | Date rules using `today`, `$context`, mixed `Date`/`DateTime`, concept or reaction-`where` positions; nested paths | spec them in design | rule does not bind: `recorded` | `recorded` |
 | Bodied rules, code policies | spec them | spec reported **unsupported**, never passed | no |
 | Pending described command handlers (v23) | specify intent | binds; denial/validation execute, body-reaching specs Unsupported ImplementationBody; all-Unsupported is not green | STAGE-IMPL-002 even Stub mode |
-| Attached command handlers | spec them in design | blocked: PLAY0800, no spec runs (V3 blocked); permanent constrained-attachment requirement, gap-fill in code | no |
+| Attached command handlers | spec them in design | beside unconditional `produces` with a resolved body: binds v23, a spec reaching the body is Unsupported (`ImplementationBody`); otherwise PLAY0800, no spec runs | Stage renders a C# body; generated specifications execute verified synchronous C# handlers |
 | `file` constraints | spec them in design | blocked: PLAY0268 at binding, no spec runs (V3 blocked) | no |
 | Query `performer`s | spec them in design | opaque read: PLAY0270 information, left out of the executable model; a spec that reads it is left out, every other spec still runs ([version gate](../../cratis-screenplay-toolchain/references/executable-subset.md#code-attachments-what-binds-what-never-does); older compilers report PLAY0268) | no |
 | Atomic reaction mode (v22) | declare for new models | failed batch adds no facts or view changes; earlier batches/commands remain; `then error` alone is insufficient | v22 STAGE-ESM-016; mode in admitted v23–v27 STAGE-ESM-043 |
 | Protected command reads (v25) | declare opt-in for eligible reads | absence Validation; matching intervening facts Conflict; race vectors are not a new spec construct | Cratis C# rendering in a new enough bundle (STAGE-ESM-044 before, or for unpreservable shapes); semantic Host/executor execute admitted reads, non-Error protected requirements STAGE-ESM-045; v25 pair admitted |
 
-Requires Screenplay 4.210.0 (`screenplay --version`) for attached handlers to report PLAY0800; older binders use PLAY0268. Other PLAY0268 families are unchanged.
+Requires Screenplay 4.250.0 (`screenplay --version`) for attached handlers beside `produces` to bind; 4.210.0 to 4.249.x report PLAY0800 for every attached handler and older binders use PLAY0268. Other PLAY0268 families are unchanged.
 
 Requires Screenplay 4.105.0 or later (`screenplay --version`) for list-query specifications, and 4.143.0 or later for collection equality filters (ESM v14).
 

package/package/corpus/skills/cratis-screenplay-scenario-coverage/references/version-skew.md

@@ -1,14 +1,25 @@
-# Version skew: reaction cascades and false PLAY0285
-
-How to specify reaction cascades across compiler versions.
-
-Under ESM v6 a command spec's `then` lists the events reactions cascade from it. A compiler
-bundled in an older `cratis` reports a **false PLAY0285** for such
-a spec; the standalone `screenplay` and a `cratis` whose compiler admits v6 accept it.
-Neither checks that a cascade event is *missing*.
-- A compiler that admits v6 (standalone, or a current `cratis`): write the v6-correct spec
-  (own productions plus cascade); validate with `screenplay <folder> --warnaserror --no-color`
-  or `cratis screenplay validate <folder> --warnings-as-errors`.
-- Only an older `cratis` bundle and no standalone tool: keep the command spec to its own productions, specify the reaction in its
-  Automation slice (`when append <Trigger>` -> `then <Produced>`), record the pending cascade
-  expectation in `STATE.md` as known-incomplete. Never delete the reaction.
+# Specifying reaction chains across slices and compiler versions
+
+How to specify a chain of reactions, and what `PLAY0285` means on each compiler.
+
+Requires Screenplay 4.246.0 or later (`screenplay --version`) for single-slice runs and `then invokes`.
+
+A specification runs only the slice that declares it (Screenplay decision 0115, for every model
+and version). A chain across slices is proved link by link:
+- The command's slice: `when <Command>` states the command's own events.
+- The Automation slice: `when append <Trigger>` states what its reaction appends, and
+  `then invokes <Command>` (ESM v34) states a command it invokes in another slice.
+- The invoked command's slice: `when <Command>` states that command's events.
+
+A command spec that states another slice's event is refused with `PLAY0285` (unreachable)
+and fails at run time with "Expected N fact(s), got M". That is a modeling error: move
+the expectation to the slice that produces it. Never delete the reaction.
+
+Older compilers:
+- A compiler older than ESM v6 does not trace reactions and can report `PLAY0285` on a
+  reaction in the specification's own slice. That is tool skew: validate with the
+  standalone `screenplay <folder> --warnaserror --no-color` or a current
+  `cratis screenplay validate <folder> --warnings-as-errors`, and record which tool gave which verdict.
+- A compiler that predates `then invokes` refuses it. With only such a tool, keep the
+  automation's own appended facts in its spec and record the pending hand-over expectation
+  in `STATE.md` as known-incomplete.

package/package/corpus/skills/cratis-screenplay-scenario-coverage/references/view-and-story-specs.md

@@ -142,12 +142,13 @@ not prove an entire list is empty: assert the unkeyed list query itself (an unke
 - **Projection lag**: a spec asserts the settled state. If a screen decision depends on the view
   being current (a booking screen that must not offer a taken berth), that is not protection:
   the command needs its own constraint, or the rule is `recorded` as target-enforced.
-- **Rebuild**: a view rebuilt from all facts must give the same rows. Mappings from
-  `$eventContext.occurred` or other occurrence data cannot be executed:
-  the reference runner refuses every event-context path except the event source id
-  (`UnsupportedEventContext`), so specifications that reach that projection report unsupported. `given clock` does not change that; it supplies `$context.occurred`
-  to command productions only. Record such projection cases as capability gaps (keep the
-  mapping and the intended spec in design mode).
+- **Rebuild**: a view rebuilt from all facts must give the same rows. The reference runner
+  refuses every event-context path except the event source id and, from Screenplay 4.254.0,
+  `$eventContext.occurred` in `from`, `every` and `children` blocks
+  (`UnsupportedEventContext` otherwise). `occurred` executes only for a fact appended during
+  the run under `given clock` (`when append` or a command's production); a `given` fact
+  carries no occurrence time and the specification reports unsupported. Record the
+  remaining cases as capability gaps (keep the mapping and the intended spec in design mode).
 - **Corrections and backdated facts**: a correction is a new fact; specify the view after it.
   If a fact carries a business date earlier than its occurrence, specify which date the view
   shows.

package/package/corpus/skills/cratis-screenplay-scenario-coverage/verification.json

@@ -10,7 +10,7 @@
     { "kind": "skill-contains", "value": "Once, idempotent, exactly once are different claims" },
     { "kind": "skill-contains", "value": "Unauthorized is never `then error`" },
     { "kind": "skill-contains", "value": "find-specification-obligations" },
-    { "kind": "skill-contains", "value": "false PLAY0285" },
+    { "kind": "skill-contains", "value": "A specification runs only its own slice." },
     { "kind": "skill-contains", "value": "One behaviour per spec" },
     { "kind": "skill-contains", "value": "No command has only two specs" },
     { "kind": "skill-contains", "value": "not scenario-complete" },

package/package/corpus/skills/cratis-screenplay-slice-design/references/read-model-design.md

@@ -280,7 +280,7 @@ module Berths
       screen OpenBooking
         title "Open booking"
         data OpenBooking via query OpenBookingById
-        action CancelBooking
+        action CancelBooking for item
       specification CancelledBookingLeavesTheList
         given caller
           authenticated

package/package/corpus/skills/cratis-screenplay-slice-design/references/slicing.md

@@ -83,7 +83,7 @@ module Moorings
       query WaitingRequests => WaitingRequest[]
       screen WaitingListPage
         data WaitingRequest via query WaitingRequests
-        action AssignBerth
+        action AssignBerth for item
     slice StateChange AssignBerth
       command AssignBerth
         berthRequestId BerthRequestId identifier

package/package/corpus/skills/cratis-screenplay-slice-design/references/worked-example.md

@@ -121,8 +121,8 @@ module Lockers
           column number   label "Locker"
           column volume     label "Volume (l)"
           column assigned label "Taken"
-        action InstallLocker
-        action AssignLocker
+        action InstallLocker for screen
+        action AssignLocker for item
       specification RefusingAnAnonymousLockerLookup
         given caller
         then query LockerById
@@ -273,7 +273,7 @@ module Lockers
       screen MyRequest
         title "My locker request"
         data RequestStatus via query RequestById
-        action RequestLocker
+        action RequestLocker for screen
       specification FollowingARequestToAssignment
         given caller
           authenticated

package/package/corpus/skills/cratis-screenplay-specifications/SKILL.md

@@ -186,8 +186,10 @@ Read [references/actions-beyond-commands.md](references/actions-beyond-commands.
 
 ## Reactions and cascades (ESM v6)
 
-From ESM v6 every action sets reactions off and `then` events compare every new fact, the action's and the reactions'. A specification whose action is a command goes in the slice that declares the command. A false `PLAY0285` on a cascade under a compiler that stops before ESM v6 is tool skew, not a modeling error: never delete the `then` line to silence it.
-Read [references/reactions-and-cascades.md](references/reactions-and-cascades.md) when a specification's expected events include what a reaction appends, when a cascade, clock tick or invoked command is involved, or when `cratis` reports `PLAY0285` on a model that `screenplay` accepts (it holds the "Version skew: cascades and the false `PLAY0285`" section).
+From ESM v6 every action sets reactions off. A specification runs only the slice that declares it: only that slice's reactions, captures and publications run, and `then` events compare the new facts of that slice. A specification whose action is a command goes in the slice that declares the command and states the command's own events. Another slice's event is `PLAY0285` (unreachable): state it in the slice that produces it. An automation states a command it invokes in another slice with `then invokes <Command>` (ESM v34).
+Read [references/reactions-and-cascades.md](references/reactions-and-cascades.md) when a specification's expected events include what a reaction appends, when a cascade, clock tick or invoked command is involved, or when a compiler reports `PLAY0285` (it holds the "Version skew and `PLAY0285`" section).
+
+A `statemachine` or `workflow` (ESM v36) carries its own specifications with `then is`, `then sends`, `then starts`, `outcome`, `then completes`, `then fails at` and `then waits at`. Read automations-and-translations [state machines and workflows](../cratis-screenplay-automations-and-translations/references/statemachines-and-workflows.md) when specifying either.
 
 ## Published-event specifications (released ESM v9)
 

package/package/corpus/skills/cratis-screenplay-specifications/references/actions-beyond-commands.md

@@ -21,8 +21,10 @@ Event captures use the typed event fixtures and overlay rules in
 
 Use `given clock`, never `given time`, to state the scenario occurrence time and
 assert a value mapped from `$context.occurred`. In a command's `produces`, that
-mapping executes when the scenario has `given clock`. It is not the same as
-`$eventContext.occurred` in a projection, which the execution plan refuses (SKILL.md, "Reference execution — what actually runs").
+mapping executes when the scenario has `given clock`. `$eventContext.occurred` in a
+projection is the fact's occurrence time: the reference runner executes it in `from`,
+`every` and `children` blocks for facts appended during the run under `given clock`, and a
+`given` fact carries none (Unsupported).
 
 **Which tools bind these actions.** A compiler that admits ESM v6 binds the clock, trigger
 and capture actions, and the `Automation` and `Translate` slices, reactions and captures they

package/package/corpus/skills/cratis-screenplay-specifications/references/child-ordering.md

@@ -69,7 +69,10 @@ module Orders
           orderId = "00000000-0000-0000-0000-000000000001"
         then readmodel OrderView
           orderId = "00000000-0000-0000-0000-000000000001"
-          lines = [{"lineNumber":1,"amount":10}]
+          lines
+            item
+              lineNumber = 1
+              amount     = 10
       specification ChildBeforeGivenParent
         given LineAdded
           orderId = "00000000-0000-0000-0000-000000000001"
@@ -79,7 +82,10 @@ module Orders
           orderId = "00000000-0000-0000-0000-000000000001"
         then readmodel OrderView
           orderId = "00000000-0000-0000-0000-000000000001"
-          lines = [{"lineNumber":1,"amount":10}]
+          lines
+            item
+              lineNumber = 1
+              amount     = 10
       specification ParentBeforeChild
         given OrderAdded
           orderId = "00000000-0000-0000-0000-000000000001"
@@ -89,7 +95,10 @@ module Orders
           amount = 10
         then readmodel OrderView
           orderId = "00000000-0000-0000-0000-000000000001"
-          lines = [{"lineNumber":1,"amount":10}]
+          lines
+            item
+              lineNumber = 1
+              amount     = 10
       specification ParentNeverArrives
         given LineAdded
           orderId = "00000000-0000-0000-0000-000000000001"