@cratis/pi 7.21.0 → 7.23.0

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

@@ -0,0 +1,80 @@
+<!-- Copyright (c) Cratis. All rights reserved. -->
+<!-- Licensed under the MIT license. See LICENSE file in the project root for full license information. -->
+
+# Systems and operation intent
+
+## Contents
+
+- Declare and produce
+- Phases and ordered work
+- Specification intent
+
+## Declare and produce
+
+A top-level `system` names an external business system. A slice-owned `operation`
+declares exactly one `uses <System>`, typed inputs, optional description and
+execute/compensate phases. Operations and their specification steps are
+**authoring-only** at Screenplay 4.125.0: compile acceptance is not execution;
+binding refuses the whole model with PLAY0268. Source: released `operations.md`.
+
+`produces operation <Name>` declares an inline slice-owned operation with typed
+input mappings. Plain `produces <Name>` references an existing event or operation;
+it never creates one from a typo. Event and operation names share resolution:
+collisions/ambiguity refuse, not event-first guessing. Standalone operation
+references can be qualified across slices; that does not broaden event-production
+grammar. Operations are produced by commands, not reactions, and take no `for`,
+tags or event routing metadata. Inputs cannot be identifier/generated properties.
+
+## Phases and ordered work
+
+Keep mixed event/operation productions in their authored sequence. The intended
+future transaction contract enrolls events first, executes operations in authored
+order before commit, and compensates according to commit disposition. It does
+not promise reverse compensation order, rollback or post-commit delivery.
+
+Each phase accepts a description and one direct file/tagged body or an
+`implementation` wrapper with ordered nonblank hints and optional source.
+Direct/wrapped sources cannot mix; duplicate phases/payloads refuse.
+Description-only/hints-only phases are pending intent, not executable code.
+Typed `execute Type` remains an input; bare `execute` opens a phase. Escape an
+input named uses as `@uses`, and event-metadata input names where needed.
+No automatic operation extraction ships: moving an inline declaration manually
+must preserve its production sequence, mappings, comments and attachment paths.
+
+## Specification intent
+
+This complete authoring-only model compiles with `--warnaserror` at 4.125.0.
+`screenplay test` intentionally returns exit 3/unbound with PLAY0268; it proves
+no failure/compensation behavior today:
+
+```screenplay
+system Accounting
+concept ProjectId : Uuid
+module Projects
+  feature Registration
+    slice StateChange Register
+      operation OpenCostCenter
+        uses Accounting
+        projectId ProjectId
+        execute
+          description "Open a provisional cost center"
+        compensate
+          description "Close it if registration does not commit"
+      command RegisterProject
+        projectId ProjectId identifier
+        produces OpenCostCenter
+          projectId = projectId
+      specification Compensating
+        given operation OpenCostCenter fails
+        when RegisterProject
+          projectId = "3fa85f64-5717-4562-b3fc-2c963f66afa6"
+        then operation OpenCostCenter
+          projectId = "3fa85f64-5717-4562-b3fc-2c963f66afa6"
+        then compensated OpenCostCenter
+```
+
+`given operation ... fails` and `then compensated ...` are leaves. A requested
+`then operation` can state a partial input subset, with unique fields and
+compatible concrete values. References resolve against declared operations;
+compensation intent needs a declared compensate phase. Provider execution is a
+separate future admission, never implied by a source fixture.

package/package/corpus/skills/cratis-screenplay-command-surface/references/policy-persona-seed.md

@@ -20,7 +20,7 @@ persona Accountant
   policy IsAccountant
 ```
 
-Three condition forms: `authenticated`, `role "<name>"`, and
+Condition atoms: `authenticated`, `role "<name>"`, and
 `claim "<name>" matches subject | "<value>" | <path>`. A policy has **exactly one**
 `require` line — continue the condition on deeper-indented lines instead of adding
 a second (`PLAY0441`) — **or** one implementation (a tagged ` ```csharp ` block or
@@ -29,6 +29,28 @@ runner; a code policy binds as opaque ESM v3 and needs a target to evaluate it.
 A `persona` is authoring metadata: the binder reports it as information `PLAY0270`
 (report-only) and it does not block binding; an unknown policy it lists is an error.
 
+## Policy negation
+
+At Screenplay 4.125.0, `not <condition>` is a portable ESM v7 policy-condition
+form (decision 0027), not a named-policy operator in `authorize`. It can negate
+atoms/groups, not an opaque inline/file implementation. Precedence is `not`,
+then `and`, then `or`; parentheses override grouping. Double negation restores
+a known value, not an unknown target.
+
+Missing caller claims compared to a known text target have no match (false),
+so their negation is true. A missing/null/non-text comparison target or absent
+subject is instead **unknown**. `not unknown` stays unknown; final unknown denies.
+Kleene combinations preserve known decisive values: true OR unknown is true,
+false AND unknown is false; false OR unknown and true AND unknown stay unknown.
+`not role "Service"` alone does not require authentication: retain an explicit
+`authenticated` condition when a signed-in caller is required.
+
+Opaque predicates reached in authored short-circuit order return unsupported,
+never false or permission under negation. Binding warns with PLAY0546 when a
+negated claim's target is optional, non-string, or a subject without a command
+identifier. This C# semantic check does not come from ordinary editor validation.
+Source: `v4.125.0:Documentation/screenplay/policies.md`.
+
 ## `seed`
 
 Excerpt: `CustomerRegistered` is declared in a slice.

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

@@ -3,6 +3,12 @@
   "input": "Declare a Screenplay command with validation, authorization, a uniqueness constraint and a state-dependent rule.",
   "fixtures": [],
   "assertions": [
+    { "kind": "skill-contains", "value": "PLAY0653" },
+    { "kind": "skill-contains", "value": "personal` is an alias of `pii", "file": "references/compliance.md" },
+    { "kind": "skill-contains", "value": "report-only (PLAY0270)", "file": "references/compliance.md" },
+    { "kind": "skill-contains", "value": "--check purposes", "file": "references/compliance.md" },
+    { "kind": "skill-contains", "value": "PLAY0633–0646", "file": "references/context.md" },
+    { "kind": "skill-contains", "value": "The block is **authoring metadata**", "file": "references/context.md" },
     { "kind": "skill-contains", "value": "main `fd18129`" },
     { "kind": "skill-contains", "value": "produces event ProjectRenamed", "file": "references/inline-events.md" },
     { "kind": "skill-contains", "value": "name ProjectName = name", "file": "references/inline-events.md" },
@@ -75,13 +81,13 @@
     },
     {
       "kind": "skill-contains",
-      "value": "No supported ESM version admits them", "file": "references/generated-values-and-responses.md"
+      "value": "streams and command/specification routes instead bind and reference-execute as", "file": "references/generated-values-and-responses.md"
     },
     { "kind": "skill-contains", "value": "Generated values and responses (ESM v7)" },
     { "kind": "skill-contains", "value": "A generated value is not a request input", "file": "references/generated-values-and-responses.md" },
     { "kind": "skill-contains", "value": "(`PLAY0273`), and a concept with any validation rule cannot back a\n  generated property (`PLAY0268`)", "file": "references/generated-values-and-responses.md" },
     { "kind": "skill-contains", "value": "A response exists only on acceptance", "file": "references/generated-values-and-responses.md" },
-    { "kind": "skill-contains", "value": "**not rendered yet**", "file": "references/generated-values-and-responses.md" },
+    { "kind": "skill-contains", "value": "STAGE-ESM-028/029", "file": "references/generated-values-and-responses.md" },
     { "kind": "skill-contains", "value": "4.68.0" }
   ]
 }

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

@@ -48,12 +48,13 @@ Statements here were checked at those tags:
 
 | Fact used here | Source |
 | --- | --- |
-| Persona syntax, report-only, policies must be declared, `description` first and once | Screenplay `v4.66.0:Documentation/screenplay/personas.md` |
+| Persona syntax, report-only, policies must be declared | Screenplay `v4.66.0:Documentation/screenplay/personas.md` |
+| Description order; authored/import board order and order-preserving MCP layouts | Screenplay `v4.125.0:Documentation/screenplay/grammar.md`, `folders.md`, `imports.md` |
 | Single-line and fenced `description` (`FencedText`) | `v4.66.0:Documentation/screenplay/slices.md#descriptions`, `grammar.md:1084-1088` |
 | `<Type>[]`, shapes must be declared; `@pii` and `reason` on concepts | `v4.66.0:Documentation/screenplay/events.md`, `concepts.md` |
 | `then denied`, `given caller`, `then error` | `v4.66.0:Documentation/screenplay/specifications.md` |
 | PII on an event-source id is rejected by Chronicle (CHR0034); nullable event properties warn (CHR0012) | Chronicle `v19.32.0:Source/Clients/DotNET.CodeAnalysis/DiagnosticIds.cs` |
-| Any `@pii` or `@sensitive` on a concept fails binding (PLAY0268) | `v4.66.0:Source/DotNET/Screenplay/Semantics/SemanticModelBinder.Concepts.cs:21-24` |
+| Any `@pii` or `@sensitive` on a concept fails binding (PLAY0268) at 4.66.0; current markers are in `cratis-screenplay-command-surface` | `v4.66.0:Source/DotNET/Screenplay/Semantics/SemanticModelBinder.Concepts.cs:21-24` |
 
 Every complete `screenplay` fence in this skill compiles with the standalone compiler
 4.68.0 (`--warnaserror`) and with `cratis screenplay validate --warnings-as-errors` 3.28.2.
@@ -122,8 +123,15 @@ decided apart from what you assumed. Never guess silently.
    two business facts that make it meaningful. A simple state transition may carry no payload
    beyond its identity: do not pad events with fields just to reach a count. Domain names; `<Type>[]` for collections (declare the `type`); a
    `concept` for a value with its own meaning; classify personal data on the concept with
-   `@pii` and a reason now. `@pii` compiles but does not bind (PLAY0268 at 4.66.0): record it
-   as a known target gap; never drop it to get a clean result.
+   bare `pii` and a reason now; operational secrets use `secret` (4.127.0).
+   Either blocks binding (PLAY0268); record the gap, never drop protection.
+   Ask what use, lawful basis, retention, recipient/transfer and erasure needs the
+   data serves; declare those in a `purpose`, not a concept reason. Special/criminal
+   qualifiers describe the value, not legal permission. See command-surface
+   `references/compliance.md` for purpose coverage checks and the processing record.
+   For who-is-calling details, distinguish token claims from a keyed single-result
+   identity-source query or opaque implementation. The `identity` block is metadata;
+   executable detail reads remain unsupported. See `references/context.md` in command-surface.
 7. **Validate, gate, hand off.** After a coherent batch of edits (not every sentence) run V1
    with the tool and version named (`cratis-screenplay-toolchain`). Stop storming a workflow
    when the user says it is complete or both closing questions return nothing new; unattended,
@@ -136,12 +144,14 @@ decided apart from what you assumed. Never guess silently.
 - Slice types are a closed set: `StateChange`, `StateView`, `Automation`, `Translate`. In
   discovery an event lives in the `StateChange` slice that will produce it, named after the
   probable command; a slice with only an `event` compiles.
-- A `persona` names declared policies only (unknown policy = error); `description` is the
-  first body line and appears once.
+- A `persona` names declared policies only (unknown policy = error); `description` appears
+  at most once, anywhere in its body.
 - Declare each event once in the whole application; other slices refer to it by name.
-- Folder-layout round-trips re-sort modules, features and slices by name (a single document
-  keeps authored order at v4.66.0): story order is documentation (feature `description`,
-  STATE.md), never structure.
+- Boards keep authored declaration and import order: imports expand depth-first, glob
+  matches alphabetically. Unimported folder files remain visible after ranked siblings.
+  MCP `expand-layout` preserves this order with import barrels; an import-less
+  `PlayFileWriter.Expand` layout falls back to path order. Order is presentation, not
+  execution or identity. Keep causes and branches in the feature `description` and STATE.md.
 - A misspelt keyword inside a slice is only warning PLAY0029 and the block disappears: always
   validate with warnings as errors.
 

package/package/corpus/skills/cratis-screenplay-discovery/references/interview-questions.md

@@ -21,7 +21,7 @@ assumption you take instead of asking.
 | Outside | Which outside parties or systems send or receive information here? | Later translations and contracts | they send facts we rely on: ask how we recognise which of our records it concerns |
 | Corrections | Can a recorded fact turn out wrong? How is it put right today? | Correction and reversal events instead of edits | "we just edit it": ask who needs to know it was changed |
 | History | What would an auditor, a regulator or an angry customer ask to see later? | Finds facts that look like detail but must be kept | a calculation must be shown later: treat it as a fact |
-| People's data | Which values identify or describe a person? How long may we keep them? | `@pii` on concepts before event shapes settle | data about two people in one fact: consider separate facts |
+| People's data | Which values identify or describe a person? For what use, basis, retention, recipients/transfers and erasure exceptions? | bare `pii` on concepts; purpose declarations separate from reasons | special/criminal data needs declared safeguards; two people in one fact may need separate facts |
 | Volume | How often does this happen, and how long does one instance live? | Informs stream design later; never a reason to drop a fact | an instance lives for years: note it for stream review |
 | Input | What do we have to go on: written rules, a rough list, word of mouth, a running system? | Sets how hard to sweep | only word of mouth: run every sweep lens |
 | Who decides | Who has the final word on what this means for the business? | Separates decisions from assumptions | no one present: mark meaning as assumption to confirm |

package/package/corpus/skills/cratis-screenplay-discovery/references/storming-loop.md

@@ -29,7 +29,7 @@ then reports what changed and asks one question. The user should always be able
    | rename | better business name for an existing fact | identity-affecting once persisted: see SKILL.md |
    | split | one name was covering two facts | keep the original if it is persisted; add the second |
    | merge | two names for one fact | only when they truly mean the same thing |
-   | reorder | the story order changed | update the feature `description`/STATE.md; files sort by name |
+   | reorder | the story order changed | change declaration/import order for the board; update the feature `description`/STATE.md for causes and branches |
    | drop | not a fact after all | record why in STATE.md |
    | none | already modeled | say so briefly |
 
@@ -65,10 +65,11 @@ open, start the sweep (`divergent-sweep.md`).
 ## A discovery skeleton
 
 What a model looks like after the first workflow has been stormed: no commands, read models
-or screens yet. Slices are named after the command expected to produce each event and are
-sorted by name when a folder layout is written back (a single document keeps authored order
-at v4.66.0), so the order of the story lives in the feature `description`, not in position. Persona
-`description` text holds Does / Reads / Cannot on one quoted line here; the multi-line fenced
+or screens yet. Slices are named after the command expected to produce each event. At
+Screenplay 4.125.0, boards use authored declaration/import order, and MCP `expand-layout`
+preserves it with imports. An import-less `PlayFileWriter.Expand` layout still falls back to
+path order. Order is presentation only; the feature `description` records causes and branches.
+Persona `description` text holds Does / Reads / Cannot on one quoted line here; the multi-line fenced
 form is in `personas-and-causes.md`.
 
 ```screenplay

package/package/corpus/skills/cratis-screenplay-event-modeling/SKILL.md

@@ -53,7 +53,7 @@ Framework repositories and brownfield work that has not opted in stay code-first
   handlers, adapters, and scope Stage cannot render yet (the model stays the contract).
 - **Never:** use code as a shortcut around the model; change the model to match
   existing code; edit Stage-managed output; leave a modeled rule living only in
-  code; weaken protection (authorization, `@pii`, rules) so a model compiles or renders.
+  code; weaken protection (authorization, `pii`, rules) so a model compiles or renders.
 
 **2. Run the lifecycle.** Load `cratis-screenplay-modeling-lifecycle` for modes, the
 independent verdicts V1-V5, the P0-P9 phases with their gates, stop-or-assume,
@@ -131,14 +131,16 @@ What binds depends on **which tool** you ask, so name the tool and its version:
 - `reads` and `concurrency` on a command do not bind (`PLAY0271`), so no decision is
   protected against stale state. A reaction trigger's `reads` that only `invokes` is
   report-only intent (`PLAY0270`); one that `produces` directly fails binding (`PLAY0268`).
-- `persona` declarations are report-only and never block; `@pii` and `@sensitive`
+- `persona` declarations are report-only and never block; bare `pii` and `secret`
   concepts do block binding (`PLAY0268`). Keep them anyway: the classification is
   part of the model. Report the block.
-- Generated values and `returns` responses bind and execute from standalone 4.68.0 (ESM v7) but fail binding
-  with `PLAY0268` on the 4.66.0 bundled in `cratis` 3.28.x, and Stage 4.24.2 does not render them
-  (`STAGE-ESM-016`, tracked in Stage#201): gap-fill. Operations and systems, and event sources and
-  streams, are authorable but non-executable (`PLAY0268`; not admitted by any supported ESM version);
-  a command `handler` never binds.
+- Generated values/responses bind and reference-execute as v7; sources, streams
+  and command/specification routes as v8; reaction `runs as` identity as v10 on
+  standalone 4.125.0. Use `screenplay test` or MCP `run-specifications` for V4.
+  Operations/systems, exact numbers and refusal/redelivery remain unadmitted.
+  CLI 3.41.0 bundles older syntax and renders through v7 only: its parser rejects
+  `runs as`, and Stage refuses generated values/responses with STAGE-ESM-028/029.
+  Source/binding admission and target realization are separate gates.
 
 The ESM versions, the full disposition table and the Step 7 clock example's binding
 result are in [references/parsed-not-runnable.md](references/parsed-not-runnable.md)
@@ -241,7 +243,7 @@ compile or will not be safe. Both are deliberate.
 ## Naming the primitives is the highest-value work
 
 Name concepts before events, classify personal data at the concept, keep events past tense and single-purpose, and never put the event-source identity in an event payload.
-Read [references/naming-primitives.md](references/naming-primitives.md) when declaring concepts, `@pii` classification, event shapes, `identifier`, inline events or `id "<old name>"` pins.
+Read [references/naming-primitives.md](references/naming-primitives.md) when declaring concepts, `pii` classification, event shapes, `identifier`, inline events or `id "<old name>"` pins.
 
 ## Quick gate - before specifications are called done
 

package/package/corpus/skills/cratis-screenplay-event-modeling/references/naming-primitives.md

@@ -5,10 +5,12 @@
   `Decimal`, `Bool`, `Date` and `DateTime`; `Enum` is a separate concept kind,
   with its values indented beneath.
 - **Classify personal data at the concept**, with a reason:
-  `concept PersonName : String @pii` plus an indented `pii reason "..."`. Every
+  `concept PersonName : String pii` plus an indented `pii reason "..."`. Every
   usage inherits it; a reason for an attribute the concept does not declare is an
-  error. Decide this before fixing event shapes - erasure follows the subject and
-  the subject follows the stream.
+  error. Decide this before fixing event shapes; purpose/basis/retention belong in
+  processing-purpose declarations, not a reason. An event subject defaults to the
+  source unless supplied; the trailing event-property `subject` mark is report-only
+  at 4.127.0, not runtime lineage. See command-surface `references/compliance.md`.
 - **Events are past tense and self-describing** - `InvoiceRegistered`, never
   `Created`. One purpose per event; an event needing an optional property to cover
   two situations is two events.

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

@@ -32,8 +32,8 @@ module Invoicing
     description "Registering and managing the lifecycle of invoices"
 ```
 
-`description` is the optional **first body line** of a module, feature, slice,
-persona or command; at most one. Use a fenced block tagged ` ```text ` when one line
+`description` is optional on a module, feature, slice, persona or command;
+at most one, anywhere in its body. Use a fenced block tagged ` ```text ` when one line
 is not enough (a bare fence warns with `PLAY0397`).
 
 ## Step 2 — Brainstorm events
@@ -59,9 +59,10 @@ Phase skill: `cratis-screenplay-discovery`.
 Arrange into the timeline — the plot. *"What happens first? And then what
 happens?"* Identify the happy path **and** the alternative and error paths.
 
-**Output:** the order the slices will be written in. A folder round-trip sorts
-modules, features and slices by name, so the timeline is documentation, not
-structure.
+**Output:** the authored declaration/import order for the board, with causes
+and branches documented. Screenplay 4.125.0 MCP layouts preserve this presentation
+order with imports; an import-less `PlayFileWriter.Expand` layout uses path order.
+Timeline position does not impose execution order or change identities.
 
 ## Step 4 — Create wireframes
 

package/package/corpus/skills/cratis-screenplay-event-modeling/references/parsed-not-runnable.md

@@ -1,63 +1,55 @@
 # Parsed is not runnable: ESM versions and dispositions
 
-Facts read at Screenplay `v4.68.0` (`79801bf`; the persona, operation and stream rows were first read at `v4.66.0`): `Source/DotNET/Screenplay/Semantics/Versions.cs`,
-`SemanticModelBinder.cs` (`ReportTopLevelDispositions`), `SemanticModelBinder.CommandProductions.cs`,
-`Documentation/screenplay/{commands,operations,event-sources}.md` and decisions 0025 and 0026. Tool versions and which tool
-reports what: `cratis-screenplay-toolchain` `references/versions.md`.
+Current evidence: Screenplay v4.125.0 `SemanticModelBinder.cs`, `Versions.cs`,
+`Documentation/screenplay/{commands,operations,event-sources,reactions,tool}.md`.
+The binder selects v8 for event routes and v10 for declared reaction identity.
+Pins and consumer boundaries: toolchain `references/versions.md`.
 
 ## Which ESM version a model needs
 
-- **v1** by default.
-- **v2** for typed event-source facts: `produces ... for <identifier>` when the event does not
-  repeat the identifier, `for` values in specifications, and `$context.occurred` or caller
-  identity in `produces`.
-- **v3** for code the model hands off: bodied reducers, code validation, code policies. Code
-  binds as an opaque requirement; the reference runner reports any specification that needs it
-  as unsupported. A command `handler` (including `implementation` and `hint`) never binds
-  (`PLAY0268`).
-- **v4** for event-contract lineage (multiple event generations) and **v5** for keyed read-model
-  absence assertions (`then no readmodel`).
-- **v6** for reactions, captures, application triggers and the clock (and so `Automation` and
-  `Translate` slices).
-- **v7** for generated command properties, `returns` responses, generated fixtures and `then returns`
-  expectations, and only when one is used (standalone 4.68.0 or later; decision 0026).
-- Operations, event sources and streams, decision reads and exact numbers are **not admitted by any
-  supported ESM version**; they have no number until a release-ready admission (decision 0025).
+- v1 by default; v2 for typed event-source facts and admitted occurrence/audit mappings.
+- v3 for opaque code requirements. Reference execution cannot execute their bodies.
+- v4 for event-contract lineage; v5 for keyed read-model absence assertions.
+- v6 for admitted reactions, captures, application triggers and clock.
+- v7 for generated command values, responses, fixtures/return assertions and policy negation.
+- v8 for sources/streams and command/specification routes.
+- v9 for public-event contracts; v10 for reaction `runs as system` identity.
+- Operations/systems, exact numeric mode and refusal/redelivery remain unadmitted
+  (PLAY0268). Version allocation is not inferred from an older planning decision.
 
 ## Dispositions to keep apart
 
-| Construct | Authoring | Binding at 4.68.0 |
-| --- | --- | --- |
-| `persona` | accepted | information `PLAY0270` ("authoring metadata and is not part of ESM v1 behavior"). Never blocks; an unknown policy on a persona is an error |
-| `domain`, `authentication` | accepted | report-only information (`PLAY0270`) |
-| `@pii`, `@sensitive` on a concept | accepted | `PLAY0268`, blocks binding and rendering |
-| `reads`, `concurrency` on a command | accepted | `PLAY0271` |
-| `reads` under a reaction trigger that only `invokes` | accepted | information `PLAY0270`: report-only intent, the model does not consult the view |
-| `reads` under a reaction trigger that `produces` directly | accepted | `PLAY0268` |
-| Generated properties, `returns` responses | authorable | binds and runs as ESM v7 on standalone 4.68.0; `PLAY0268` on the 4.66.0 in `cratis` 3.28.x; not rendered (Stage 4.24.2: `STAGE-ESM-016`, tracked in Stage#201) |
-| A policy, rule or requirement that references a generated value | accepted | `PLAY0273`; a generated property on a concept with validation rules: `PLAY0268` |
-| `system`, `operation` | authorable, syntax-only | `PLAY0268`; not admitted by any supported ESM version |
-| `eventsource`, `stream` | authorable, authoring-only | `PLAY0268`; not admitted by any supported ESM version (`cratis-screenplay-toolchain` `references/sources-and-streams.md`) |
-| UI constructs | accepted | information `PLAY0269` |
-
-A model that carries one of the blocked constructs is still a valid design model. Never remove
-the construct to make a tool pass; record the gap against its address
-(`cratis-screenplay-modeling-lifecycle`).
+| Construct | Current standalone disposition |
+| --- | --- |
+| `persona`, domain/authentication metadata | Report-only; unknown named policies remain source defects |
+| Compliance concepts | Bare `pii`/`secret` (4.127.0); binding still refuses PLAY0268, never remove protection |
+| Identity details / processing purposes / event subject | Report-only metadata (4.127.0); executable detail reads refuse PLAY0268, not source declaration errors |
+| Composite stream ids | v8 routing; complete named parts/canonical comparisons, PLAY0515 refuses protected keys/sources; not a legacy text split |
+| Command reads/concurrency | Legacy unprotected decisions, PLAY0271 |
+| Invokes-only trigger reads | Report-only, not protected state; direct production with reads refuses |
+| Generated values/responses | v7 binding/reference execution; Stage 4.51.3 member refusals STAGE-ESM-028/029 |
+| Sources/streams and command/specification routes | v8 binding/reference execution; CLI 3.41.0 render boundary is v7 |
+| Declared reaction invocation actor | v10 binding/reference execution; older CLI parser PLAY0137; Stage planner refuses v10 |
+| Operations/systems, exact numbers, refusal/redelivery | Source accepted; whole binding refuses PLAY0268 |
+| UI | Authoring/deferred metadata; runtime support is a separate consumer contract |
+
+Run standalone `screenplay test` or MCP `run-specifications` for V4. Compile
+success alone is not execution; unbound/unsupported is not passed. Preserve
+source that a narrower renderer cannot realize and report the addressed gap.
+Routing and actor checked examples: toolchain `references/sources-and-streams.md`
+and captures-and-reactions `references/invocation-identity.md`.
 
 ## The Step 7 clock example
 
-The complete example in [nine-steps.md](nine-steps.md) (Step 7) compiled with
-`screenplay <folder> --warnaserror` 4.66.0 (0 errors, 0 warnings) and opened through
-`screenplay mcp <folder>` with `executableReady: true` and five `PLAY0270` information
-diagnostics. It binds as a scheduled invocation; its `reads` is intent only, so the overdue
-decision is not executed by the model. The `cratis` 3.28.2 bundle (Screenplay 4.66.0) binds it the same way (probed); the 3.27.1 bundle
-(Screenplay 4.60.1, ESM v1 to v5) compiled it but rejected the Automation slice at binding. Report reaction
-specifications as authored, not as run, unless a V4 run says otherwise.
+The complete example in [nine-steps.md](nine-steps.md) (Step 7) had historical
+4.66.0 compile/binding evidence (zero errors/warnings, executableReady true).
+Its invokes-only reads still record intent rather than execute the overdue
+selection. Run its admitted specifications with the current reference route
+before claiming a V4 pass; no overdue-selection proof follows from binding.
 
 ## Decision 0006 and shipped generations
 
-Decision 0006 shipped in Screenplay 4.31.0: a reaction trigger can declare the
-views it decides from with `reads` (see `cratis-screenplay-captures-and-reactions`),
-but nothing enforces them yet. Event generations and typed repairs now ship;
-generations do not supply deployed migrations. Do not treat every accepted
-decision as implemented: check the construct's own page and the versions table.
+Trigger reads do not enforce decision consistency. Event generations and typed repairs now ship,
+but historical schemas do not supply deployed migrations.
+Check actual binder, runner and consumer admission instead of equating an
+accepted decision or parsed node with a running application.

package/package/corpus/skills/cratis-screenplay-legacy-extraction/SKILL.md

@@ -44,7 +44,7 @@ v19.32.0): `cratis-screenplay-toolchain` `references/versions.md`. Checked at th
 | `prologue start` is an interactive wizard that writes `cratis-prologue.json`; `interpret` resolves its language model from the Prologue file, then the global CLI configuration (cli#241 open) | cli `v3.28.2:Source/Cli/Commands/Prologue/{StartPrologueCommand,LlmOptionsResolver}.cs`, `Documentation/reference/prologue.md` |
 | Extractor effects (CDC enable, publication and replication slot), POST/PUT/DELETE only, 2 s correlation window, interpret payload (uncapped model outline and names, observed lists capped at 50, schema tables capped per schema observation), existing slot/publication reused; cleanup missing (Prologue#37) | Prologue `ad4bbe7:Source/Extractor/Sources/**`, `Source/Configuration/*`, `Source/Interpretation/EvidenceFormatter.cs` |
 | `then error`, `then denied`, `unique ... released by` | Screenplay `v4.66.0:Documentation/screenplay/{specifications,constraints}.md` |
-| No semantic diff or equivalence check exists (Screenplay#387 open) | `gh issue view 387 --repo Cratis/Screenplay` |
+| MCP semantic-diff compares canonical workspace exports; structural comparison is not execution equivalence | Screenplay `v4.125.0:Documentation/screenplay/mcp/reference.md` |
 
 Every complete `screenplay` fence here compiles with the standalone compiler 4.68.0 (`--warnaserror`) and
 `cratis screenplay validate --warnings-as-errors` 3.28.2.
@@ -153,7 +153,15 @@ chain per slice before handoff (evidence template); never manufacture references
      in the model today**, target named; a unique index with business meaning becomes
      `unique ... on <every event that sets it>` with `released by`
      (`references/rule-modeling.md`);
-   - keep `@pii` / `@sensitive` and authorization found in code; every role gate has `authorize`
+   - preserve personal-data/secret protection and authorization found in code,
+     using bare `pii` / `secret` (4.127.0); deprecated marker repairs keep legal
+     notes intact, never guess a purpose or basis. Derive purpose/use/retention
+     declarations only from evidence or expert decisions; run `--check purposes`
+     and inspect the processing record as prompts, not a legal verdict. Keep
+     hand-joined legacy ids scalar; never infer composite parts by splitting text.
+     Event `subject` is report-only; distinguish observed lineage from runtime
+     realization. See command-surface `references/compliance.md`.
+     Every role gate has `authorize`
      plus a `then denied` spec, else a recorded gap; rules you cannot express truthfully are
      recorded one by one, never fabricated.
 3. Cite evidence ids in each slice `description` ("Evidence: E3, E7"). Read `references/intent-example.md` when authoring the intentional candidate to check the complete example of evidence citations, re-slicing, constraints, authorization and recorded state-dependent rules.
@@ -191,9 +199,11 @@ handoff packet appended, first line `Outcome:`; no prose reports in the model ro
   ask again only when target or consequence expands): capture setup and Extractor runs, traffic
   re-routing, load or scenario runs that write data, cleanup DDL, hosted language-model use.
   Production needs DBA sign-off (`rules/capability-is-not-authority.md`).
-- No claims of equivalence: Screenplay has no semantic diff or equivalence check yet
-  (Screenplay#387).
-- Never weaken protection (authorization, `@pii`, rules) to make the candidate compile.
+- No claims of execution equivalence from structure. MCP `semantic-diff` compares
+  same-application canonical exports with authoritative catalogs; it does not guess
+  rename continuity, run specifications or prove recovered behavior. Inspect
+  incomplete sections and exclusions before using the result in the loss report.
+- Never weaken protection (authorization, `pii`, rules) to make the candidate compile.
 
 ## Gate
 

package/package/corpus/skills/cratis-screenplay-legacy-extraction/references/generate-notes.md

@@ -1,5 +1,14 @@
 # `cratis screenplay generate` notes
 
+## Contents
+
+- Command
+- Preconditions
+- Coverage (what a provider reads)
+- Diagnostics are the loss list
+- Arc recovery and authoring-only options
+- Reading the output cheaply
+
 Flags verified with `cratis screenplay generate --help` on the version recorded in
 cratis-screenplay-toolchain `references/versions.md`; behaviour from the cratis CLI
 (`v3.28.2:Source/Cli/Commands/Screenplay/`; the generate files are unchanged since `v3.27.1`), Arc `v22.50.5`
@@ -8,6 +17,12 @@ cratis-screenplay-toolchain `references/versions.md`; behaviour from the cratis
 Screenplay.CritterStack `v0.24.0`. Version-specific capability facts belong in cratis-screenplay-toolchain
 `references/versions.md`.
 
+Current CLI is 3.41.0, with Arc.Screenplay 22.54.0 (`references/versions.md` in
+the toolchain). Current option/admission evidence: CLI released
+`GenerateScreenplaySettings.cs`, `ArcScreenplayGeneration.cs`, v7 planning specs
+and `Documentation/reference/screenplay.md`; older diagnostic probes below keep
+their original labels. Arc#3054 and CLI#270 describe the recovered-source expansion.
+
 ## Command
 ```
 cratis screenplay generate <solution|project|folder> \
@@ -56,14 +71,39 @@ cratis screenplay generate <solution|project|folder> \
   persistence, stream ownership or authorization.
 - "Success" only means no error diagnostic was produced. Read warnings and information too.
 
-## Known lag
-The generators are built against older Screenplay packages than the CLI's compiler. Expect
-no event generations, no `when append` specifications, and no absence assertions in
-generated output, even when the code has them. Reactors are emitted as file-backed
-reactions with one named event trigger per observed event (a reactor observing no events
-is dropped with a warning), but their bodies and declarative effects are not recovered.
-Application triggers (clock, application-defined) are not generated. Record these as
-losses, then read the code for them.
+## Arc recovery and authoring-only options
+
+`--authoring-only-constructs` maps to `ScreenplayOptions.AuthoringOnlyConstructs`
+in the Arc adapter (false by default). It includes operations/systems, source and
+stream declarations/routes, and reads/requirements recovered from Provide/Handle.
+Other providers warn CLI0014 and do not apply it. Added syntax does not realize
+code or waive admission: operations refuse PLAY0268 and legacy reads PLAY0271.
+Source/stream routes themselves bind as v8 on the current standalone compiler;
+older blanket authoring-only route caveats are not its current disposition.
+
+The expanded Arc recovery surface includes:
+- Proven command identifiers and event `for` destinations.
+- Inline events where one unconditional complete production uniquely owns them.
+- Event description/documentation and generation-1 stored-name rename pins.
+- Unconditional named Must(Method) rules with implementation-file provenance,
+  where no specification exercises the command.
+- Event scenarios as `when append`, and event-source-faithful `for` fixtures.
+  Scenarios whose sources cannot be stated faithfully are omitted with SP0039;
+  record the omission as a loss, never fabricate identities to retain a scenario.
+- Supported generated UUID command values and scalar/record responses by default,
+  without the authoring-only flag, for commands without successful scenarios.
+  Commands with successful scenarios retain the legacy representation until
+  deterministic generation fixtures and response expectations can be recovered.
+  Unsupported shapes/pre-generation protection remain code with SP0052.
+
+Generated values/responses select ESM v7. CLI 3.41.0 admits v7 to planning, but
+Stage refuses those members with STAGE-ESM-028/029. CLI#261 is closed; do not say
+the compiler or CLI version gate universally refuses v7. Above v7 remains
+CLI-RENDER-004. A generated source model is evidence, not guaranteed render output.
+
+Handler/reaction bodies, unresolved conditions and unproven origins still need
+source review. Do not infer generation/evolution/absence-assertion coverage from
+a package upgrade; read diagnostics and reconcile each recovered scenario.
 
 ## Reading the output cheaply
 1. V1 on `.ai-work/screenplay/<model-slug>/legacy/static` (folder mode) with the tool and