@cratis/pi 7.62.0 → 7.63.0

package/package/corpus/skills/cratis-screenplay-toolchain/references/renderable-subset.md

@@ -21,24 +21,34 @@ and concept compliance (v13) render.
 
 ## Current admission
 
-Stage admits exact ESM v1–v17 and v19 pairs, not v18 or v20; v19 does not imply v18
-admission. The CLI's bundled Stage can be older: read installed versions and the
-pins in `product-sync.json`, not the standalone compiler's version. Each construct
-it does not render refuses with its own code before any artifact is planned.
+Stage admits exact ESM v1–v21 and v23–v25 pairs; v22/v26 and mixed pairs
+refuse STAGE-ESM-016. Version admission is separate from construct support.
+Requires Stage 4.106.0 for v18 admission; older Stage refuses it with `STAGE-ESM-016`.
+For generated-concept v20/v21 admission and construct prerequisites, read
+[Stage admission](../../cratis-stage-rendering-and-sandbox/references/admission.md).
+The CLI's bundled Stage can be older: read installed versions and the pins in
+`product-sync.json`, not the standalone compiler's version. Each construct it
+does not render refuses with its own code before any artifact is planned.
 
 Requires Stage 4.96.0 for stored event names (v16), 4.101.0 for no-event assertions (v17), 4.102.0 for refusal branches (v19), and 4.103.0 for rendered redelivery; older renderers refuse the respective shapes.
 Requires Cratis CLI 3.60.0 (`cratis --version`) for v16 rendering; a bundle that stops at v16 refuses newer models with CLI-RENDER-004.
 
+With an admitting renderer, all-Proven generated-concept rules allow unpinned
+rendered specs; warning/info rules and semantic checksum validation are enforced,
+and pattern/random strategies render. `generate rule` remains STAGE-ESM-028.
+The independent executor still needs deterministic pins. Dated patterns use
+receipt-time UTC; random ranges use `long` with inclusive endpoints.
+
 This table is a reading of the renderer's admission, not a render result: run the bundled renderer before asserting renderability.
 
 | Area | Renders | Refused (code) |
 | --- | --- | --- |
 | Slice kinds | `StateChange`, `StateView`, supported event-triggered `Automation` with Chronicle reactors | Translate, captures, non-event triggers, opaque bodies, clock/trigger/capture specs (`-024`); claim-reading/opaque `runs as` gates (`-034`), mixed effects from one handler (`-037`, redelivery can duplicate events), unsupported conditions/destinations/mappings (`-039`). Keep refused reactions whole |
-| Queries | optional keyed snapshot lookups; snapshot or observable collections, keyed or unkeyed, with v14 equality filters | context/single-result filters, opaque `scoped to`/`performer` and composite `by`: PLAY0268. DateTime filters and required parameters after optional filters refuse `-010`; filter-name collisions refuse `-012`; validated scalar keys render as primitives and convert inside the query (an out-of-rule key finds no instance), nested validated keys still refuse `-010` |
+| Queries | optional keyed snapshot lookups; snapshot or observable collections, keyed or unkeyed, with v14 equality filters | context/single-result filters, opaque `scoped to`/`performer` and composite `by`: PLAY0268. DateTime filters and required parameters after optional filters refuse `-010`; filter-name collisions refuse `-012`; concept arguments retain Arc validation, including nested members/elements; nullable keys or optional concept filters with `not empty` refuse `-010` rather than changing null behavior |
 | Authorization | role-only, authenticated, opaque pure policies, claim conditions with Uuid, Date, DateTime or text targets (numeric and Boolean claim matches render as always false), `not`/and/or; roles read through the identity's `RoleClaimType` | role-claim URIs, nested opaque policies, unresolved or non-portable policies, no single identifier, opaque-policy subjects that are not text, Uuid, Date or DateTime (`STAGE-ESM-015`, a restriction separate from declarative claim targets) |
 | Event sources, streams, routes (ESM v8) | rendered, including routed read-model/query companion replay | reserved stored names, unformattable routed fixtures (`STAGE-ESM-030`) |
 | Numbers, case tables | whole numbers as `long` from ESM v8; case tables | out-of-`int` literals below v8 (`STAGE-ESM-031`) |
-| Generated values and responses (v7/v15) | required scalar UUID/String strategies, Guarded v15 freshness, scalar/named responses, generation fixtures and `then returns` | unsupported generated types (`-028`); routed/generated-rule/legacy-allocation/name-collision or unsupported response combinations, unpinned unordered/projected expectations (`-038`); no blanket `-029` refusal |
+| Generated values and responses (v7/v15/v20/v21) | required scalar UUID/String strategies and Int random, pattern/checksum, concept validators at all severities, all-Proven unpinned relational specs, Guarded v15 freshness, scalar/named responses and fixtures | `generate rule`, unknown strategies and unsupported generated types (`-028`); unsupported response combinations, generated-property validation, name collisions, unpinned Unproven/Refuted rules or unordered/projected/collision-sensitive expectations (`-038`); invalid pins (`-011`); opaque concept rules (`-005`); unknown rule kinds and legacy checksum (`-042`) |
 | Enum numbers / compliance | explicit enum numbers (v12); concept `[PII]` or scoped `[Encrypted]` + `[NotAudited]` (v13), property-level `[NotAudited]` for protected command inputs | protected identities/enums (`-040`); explicit subject lineage remains unadmitted |
 | Specifications | command scenarios and supported single-hop reaction appends; Stage's `admission.md` | appends outside the single-hop subset and commands cascading into reactions (`-011`); `then no readmodel` (`-027`); an unauthenticated caller carrying roles or claims (`-011`); command `given clock` renders only whole milliseconds at or after 1970 |
 | v9 and v10 | reaction/reducer `from` filters; role/authenticated `runs as` | public events and event-target projections (`-032`); foreign origins and event-source captures (`-033`); directed Translate (`-024`); claim-reading/opaque `runs as` gates (`-034`); legacy `from` (`-035`); per-production route overrides (`-036`) |
@@ -48,8 +58,12 @@ This table is a reading of the renderer's admission, not a render result: run th
 | Evolved events | initial revisions only (migrations are not rendered) | `STAGE-ESM-026` |
 | Descriptions, documentation | XML `<summary>`/`<remarks>` doc comments only | characters invalid in XML: `CLI-RENDER-005`; never behavior |
 
-The CLI's bundled compiler still refuses `reads` and `concurrency` (PLAY0271) and command
-`handler`s (PLAY0268) at binding, before Stage admission. Supported filters and strategies render.
+Stage refuses protected command reads with STAGE-ESM-044, described handlers
+with STAGE-IMPL-002 (even Stub mode), and atomic mode in admitted pairs with
+STAGE-ESM-043. Literal
+text rules execute/render ordinal UTF-16 comparisons. Read [language admission](language-admission.md).
+A CLI's older bundled compiler may fail first: legacy reads/concurrency PLAY0271,
+attached handlers PLAY0268. Protected reads bind standalone v25, not a Stage render.
 Response-name authoring scopes are not rendered and Scene runtime does not supply them.
 
 Compliance mapping in the generated C#: personal data to `[PII]`, operational secrets to
@@ -76,8 +90,9 @@ ids into routing to fit a renderer (PLAY0515).
   older renderers refuse snapshot lists with STAGE-ESM-010.
   context/single-result filters, opaque `scoped to` and `performer` block binding. Keep a list the domain needs and report
   the capability gap; marking it `observable` or keying it is a modeling decision for the user.
-- A `handler` (with or without `implementation` or `hint`) never binds; the slice is
-  gap-fill, never "customized into" rendering.
+- Attached handlers remain PLAY0268. Pending handlers beside unconditional
+  productions bind v23 but Stage refuses their bodies (STAGE-IMPL-002), even Stub mode;
+  deliver as authorized gap-fill, never as implemented generated stubs.
 - Descriptions and documentation render only as XML doc comments, never as
   behavior: a rule that exists only in prose is unenforced in rendered code.