Screenplay scenario coverage
Purpose
Decide which situations need specifications in a coverage matrix, then use
consistent example data and mode-admitted forms. Record inexpressible cases; never
fake them. This skill owns coverage; cratis-screenplay-specifications owns grammar
and outcome comparison.
When / when not
- Use: the scenario phase of
cratis-screenplay-modeling-lifecycle; adding or changing a
slice's specs; checking coverage of an existing model; deciding how to specify retries, races,
cascades or event evolution; running a scenario workshop.
- Not for: grammar and comparison (
cratis-screenplay-specifications); designing the commands
or views (cratis-screenplay-slice-design); where invariants live
(cratis-screenplay-streams-and-consistency); reaction and capture recipes
(cratis-screenplay-automations-and-translations); C# specs (cratis-specifications-csharp,
cratis-specification-by-example); a full audit (cratis-screenplay-model-review).
Product sources
Screenplay Documentation/screenplay/specifications.md and queries.md and the standalone compiler
describe the released behavior (including ESM v7 fixtures and then returns). Reading the installed tool and bundle versions is covered in
cratis-screenplay-toolchain SKILL.md.
MCP find-specification-obligations derives SPEC001–SPEC008 from declarations;
met means matching authored presence, not full coverage or passing execution.
Use it to seed, never replace, the matrix. Multi-step storylines remain unavailable;
lifecycle families emulate them.
Interview phase
Ask only what is missing: coverage depth, allowed/refused rule examples, intended
execution mode and who validates. Read interview prompts
when these inputs are unsettled; skip answered questions.
Unattended: assume visibly, never invent a rule, and record who actually answered; an agent asking itself four kinds of question is not four approvals.
Procedure
- Mode first (
cratis-screenplay-modeling-lifecycle): it decides the admitted spec forms.
Fix the model root and source revision.
- Ask only what is missing (Interview phase). Take discovery and slice-design outcome lists
(Cannot lines, "only if", refusals, competition candidates, endings) as coverage seeds.
- Inventory before drafting: read commands, effective gates (own, feature, module), rules,
constraints, productions, reactions, captures, read models and queries in scope; derive the
obligations from those declarations, not from specs already present. Use scoped
find-specification-obligations and inspect unmet/message-specific obligations;
ambiguous references and opaque code are not inferred coverage.
- Coverage matrix before any spec (
references/coverage-matrix.md). Rows: every command,
reaction, capture, read model and gated query. Columns: the scenario types below. Each cell
is spec <Name>, n/a: <domain reason>, recorded: <why not expressible>,
n/a: technical (closed list), open: <case>, question: <id> or gap: <code>. "Fewer specs" is never a reason; a
declaration (constraint, policy) or another command's denial is not a spec.
- Per read model, decide the shape: single-transition specs only, or also a lifecycle
family (cumulative givens). Write the decision and reason in the matrix, before drafting any
payload: one line per read model. One schema reused for every command and view may indicate
the per-view judgment was skipped: check for a recorded reason per view before concluding.
- Example data: a small cast per feature; reuse only where meaning agrees; preserve
existing intentional fixtures (
references/scenario-catalogue.md "Example data"). Shared
fixtures may live as typed examples in another document beside the declarations they type
(cratis-screenplay-specifications references/examples-and-routes.md).
- Draft commands for each applicable scenario type below. Vary only the value
under test in a rejection. Read specifications'
persona callers and cases
when sharing a validation matrix or choosing synthesized versus explicit callers;
cases are not fixture examples and do not group unrelated behaviors.
- Separate view pass: population, each update, accumulation, removal (with a surviving
row), absence, ordering. Mark lifecycle branches. Views combining sources must
tolerate any arrival order. Pin a child before its parent (Requires Screenplay 4.149.1 or later):
given child, then parent, then read model; "parent never arrives" leaves the
child absent. Evidence/example:
references/view-and-story-specs.md.
- State-dependent rules: use
reads plus require over authoritative state;
eligible views opt into command reads protected (v25). Cover present/absent reads,
refusal and denial; matching decide/commit changes are conflicts, not refusals.
Read protected reads
for admission and Stage refusal; legacy/refused shapes remain marked unenforced
with a named target mechanism. Forbidden:
caller-supplied copies of state in require, boolean attestation inputs (confirmsX == true) and rules hidden in handler/hint prose. Never drop an unresolved given or assertion
to make a spec compile: record the blocked case and continue.
- Validate the batch (V1, warnings as errors); V2/V3 when executable or renderable. Fix diagnostics without dropping intended rules, prerequisites or assertions, then rerun the applicable verdicts; if the chosen mode cannot admit the construct, preserve it and report the blocked scope explicitly. The
phase report carries the matrix path, spec names added or changed,
recorded, open and
gap cells and open questions.
Scenario types (decide each per command; detail in references/scenario-catalogue.md)
Decide each of these per command: happy path; rule rejection (one spec per rule, exact pinned then error); denial (given caller without the policy, then denied, one per gated command and query); state violation; duplicate or retry; competing claim; alternative path; ordering; external failure; compensation; evolution; and the view pass. Read references/scenario-catalogue.md ("Scenario types at a glance") for each type's question and usual shape.
For command Date/DateTime ordering, cover increasing and inverted intervals,
equality across offsets, a one-tick boundary and each participating DateTime
input without an offset or Z. That last case rejects with Validation before rules,
even if a condition short-circuits or a production is skipped. then stays ordinal;
never replace payload text with an equivalent instant. Read the complete
retention-window specifications
for the compiler prerequisite, admitted positions, refused today and Stage's v26
refusal. Missing-offset runtime coverage needs an evaluator-request or target input
test: a typed .play fixture rejects that value at binding with PLAY0273, before runtime.
For recovery, when redelivered <Event> to <Reaction> must select one definitely
matching effective given and no undecided candidate. It delivers only to the named
reaction without re-appending the input; then no events explicitly checks no
new facts from the settled cascade (ESM v17). Read references/scenario-catalogue.md
("Redelivery selectors") when choosing retry/no-effect cases or stream/no stream.
Read query rejection examples
when specifying malformed keys/filters versus valid absence (ESM v18).
Requires Screenplay 4.157.0 (screenplay --version) for v17, 4.161.0 for query
validation/error assertions; older tools do not execute these contracts.
Once, idempotent, exactly once are different claims. unique event proves a once-only fact,
not successful retry handling or an exactly-once external effect. Name the claim
proved and keep other guarantees as target requirements; recovery cases are in
references/scenario-catalogue.md.
Rules
Compiler contracts
- At most one
when action; with none, assert only read-model or query outcomes.
then events are exact in count and order (then events in any order relaxes order only).
- Command denial:
then denied with no success or error outcome. Read-only query denial:
then query <Query> with arguments and no result, then then denied. Every gated command
or query spec needs given caller or given caller as <Persona> (module and feature gates count); an authorized scenario
gets no inferred fixture (PLAY0389). Unauthorized is never then error.
- Duplicate and competing specs use
when <Command>; when append is for projection and
automation triggers, consumed public events driving captures, and for a
constraint the command's own validation would reject first.
null only for optional read-model properties; constraint messages are copied verbatim.
- Executable-only binding checks (PLAY0350/0352/0388/0389/0273) do not show in V1: run V3.
Modeling defaults
- Every slice has at least one specification at the application boundary.
- One behaviour per spec; names read as sentences:
Reserving..., Rejecting..., Refusing...
(denial), <View>LifecycleN<State> for families.
for on every given, appended and expected event (plain produces <Name> too; inline produces event omits it), and on the when command where the
destination matters. A competing-claim given needs a different for. A given without for
belongs to the event source the specification acts on; state for when the command appends to
several event sources or an assertion depends on the given's source, and never assert
$eventSourceId of a sourceless given. Read
examples and routes.
Foreign event fixtures feeding a capture may omit for; supplied for is
opaque source text, not the capture's content key.
- Format rules belong on a
concept: give each concept rule representative acceptance,
rejection and boundary specs once (through one command that carries it), not on every use;
never n/a automatically. Date/DateTime comparisons are command-only, not concept rules.
Include a whitespace-only rejection for text not empty:
this changes outcomes in every ESM version (Requires Screenplay 4.151.0 or later). Unicode/identity boundaries
and evidence: command-surface references/validate-rules.md.
A business rule gets one rejection spec if an expert could recognize it from its message;
binder-enforced shape is no scenario (catalogue §2).
- Persona Cannot lines are intent: each needs an executable gate plus a
then denied spec whose
caller is a synthesized persona witness or an explicit gate fixture, else record a gap.
- Descriptions are not rendered: a rule only in prose is unenforced; make it a rule layer, a
spec or a recorded target requirement.
- Prove projections with events (
given/when append), not given readmodel; seed read models
only for performer-backed views or commands that decide on view state. A query performer is an opaque read
(information PLAY0270, not PLAY0268): it is left out of the executable model, a spec that reads it is
left out too and the other specs still run, so mark it gap for the executable modes (version gate).
- No contradiction between a family and single-transition specs of the same view.
Quality checklist (adapted from the TrogonStack scenario checklist; references/provenance.md)
Read references/quality-checklist.md before reporting a scope spec-complete. No command has only two specs (success and one rejection) unless every other type was reviewed and found inapplicable; a model with dozens of command specs and no read-model spec is not scenario-complete.
Review questions
Read references/review-questions.md for the race, retry, arrival-order, correction and cross-context questions.
Public-event coverage (ESM v9)
Outbound publication needs when append <private> and then <PublicEvent>.
Captures over public events use given <FromEvent> / when append <FromEvent>,
not capture records (PLAY0701). Read references/public-event-coverage.md
when specifying public events or routed producers and observers.
Record captures distinguish first sight from updates: first root/child/nested
records are added only, so field guards need given capture for the same key.
Use a separate when added append when initial observations should produce a fact.
Read captures-and-reactions references/record-capture-specifications.md for the
prerequisite and runnable cases. Include first, changed and unchanged rows in the matrix.
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 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
scope is reported as explicitly incomplete); V1 passes with the tool named in
cratis-screenplay-toolchain; for executable or renderable scope V3 is binding-ready.
Verify
- Re-inventory declarations at the reported revision: every applicable obligation maps to an
existing spec whose givens, action and assertions exercise it.
- Commands and read models are checked in separate passes; each removing projection has a
populated-then-removed spec.
- V1 passes (standalone
screenplay required when cascades are specified); report tool and
version.
- Run V4 through standalone
screenplay test or MCP run-specifications;
propose → review → run with proposalId →
apply (Requires Screenplay 4.145.0 or later). PLAY0285 (impossible then) unbinds
the whole model; no spec runs.
if not executed, report the actual host/input reason, not a blanket no-route
claim. Stage's runner is target-engine evidence, never V4; V1/V3 do not prove pass. V5 is "not run" unless rendering was attempted; report admission, publication, build and
tests separately.
- Match guarantees to evidence:
.play outcomes, in-process Chronicle scenarios and real-kernel
tests are not interchangeable (references/chronicle-verification.md).
- Reference example
references/berth-reservations.md: compiles with warnings as errors.
Route near misses
Read references/neighbouring-skills.md when the work is grammar, rules, projections, reactions, invariant placement, review or C# specs.
References (load on demand)
references/scenario-catalogue.md - each type: ask, applies when, n/a when, shape, traps; example data. Read when deciding applicability, eliciting cases or choosing example data.
references/view-and-story-specs.md - view specs, lifecycle families, ordering, lag. Read before deciding each view's lifecycle family and drafting view specifications.
references/coverage-matrix.md - obligations from declarations, template, worked matrix. Read before constructing or reconciling the coverage matrix.
references/scenario-examples.md - compact worked examples per category, good and bad forms,
list and todo-list views; copied from the complete references/invoicing-dues-example.md
(runnable) and, for compensation, references/invoicing-dues-design.md (design mode: holds the
stored-state rules, does not bind). Read references/scenario-examples.md when drafting a category and you need good/bad or worked specification forms; read references/invoicing-dues-example.md when you need the complete executable declarations behind the invoicing excerpts; read references/invoicing-dues-design.md when specifying stored-state invoicing rules or their compensation scenarios in design mode.
references/scenario-workshop.md - facilitation guide for group scenario sessions. Read when facilitating a group scenario session.
references/chronicle-verification.md - guarantees that need more than a .play outcome. Read when a claimed guarantee needs in-process or real-kernel evidence beyond .play outcomes.
references/spec-forms-by-mode.md - admitted forms in design, executable, renderable. Read after choosing the mode and before drafting its admitted specification forms.
references/berth-reservations.md - complete compiled example (marina guest berths). Read when you need a complete design-mode example of a coverage matrix realized as specifications.
Lineage
Attribution and adapted sources: references/provenance.md. Read references/provenance.md when checking attribution or how an adapted practice differs from its source.
1---2name: cratis-screenplay-scenario-coverage3description: Use when deciding which Screenplay scenarios a slice needs or auditing its refusal, retry, race and view-lifecycle coverage. Not for specification grammar, comparison semantics or C# tests.4license: MIT5metadata:6 source: https://skillmd.com/skills/cratis/cratis-screenplay-scenario-coverage7---89# Screenplay scenario coverage1011## Purpose12Decide **which** situations need specifications in a coverage matrix, then use13consistent example data and mode-admitted forms. Record inexpressible cases; never14fake them. This skill owns coverage; `cratis-screenplay-specifications` owns grammar15and outcome comparison.1617## When / when not18- Use: the scenario phase of `cratis-screenplay-modeling-lifecycle`; adding or changing a19 slice's specs; checking coverage of an existing model; deciding how to specify retries, races,20 cascades or event evolution; running a scenario workshop.21- Not for: grammar and comparison (`cratis-screenplay-specifications`); designing the commands22 or views (`cratis-screenplay-slice-design`); where invariants live23 (`cratis-screenplay-streams-and-consistency`); reaction and capture recipes24 (`cratis-screenplay-automations-and-translations`); C# specs (`cratis-specifications-csharp`,25 `cratis-specification-by-example`); a full audit (`cratis-screenplay-model-review`).2627## Product sources28Screenplay `Documentation/screenplay/specifications.md` and `queries.md` and the standalone compiler29describe the released behavior (including ESM v7 fixtures and `then returns`). Reading the installed tool and bundle versions is covered in30`cratis-screenplay-toolchain` `SKILL.md`.31MCP `find-specification-obligations` derives SPEC001–SPEC008 from declarations;32met means matching authored presence, not full coverage or passing execution.33Use it to seed, never replace, the matrix. Multi-step storylines remain unavailable;34lifecycle families emulate them.3536## Interview phase37Ask only what is missing: coverage depth, allowed/refused rule examples, intended38execution mode and who validates. Read [interview prompts](references/interview-batch.md)39when these inputs are unsettled; skip answered questions.4041**Unattended:** assume visibly, never invent a rule, and record who actually answered; an agent asking itself four kinds of question is not four approvals.4243## Procedure441. **Mode first** (`cratis-screenplay-modeling-lifecycle`): it decides the admitted spec forms.45 Fix the model root and source revision.462. **Ask only what is missing** (Interview phase). Take discovery and slice-design outcome lists47 (Cannot lines, "only if", refusals, competition candidates, endings) as coverage seeds.483. **Inventory before drafting**: read commands, effective gates (own, feature, module), rules,49 constraints, productions, reactions, captures, read models and queries in scope; derive the50 obligations from those declarations, not from specs already present. Use scoped51 `find-specification-obligations` and inspect unmet/message-specific obligations;52 ambiguous references and opaque code are not inferred coverage.534. **Coverage matrix before any spec** (`references/coverage-matrix.md`). Rows: every command,54 reaction, capture, read model and gated query. Columns: the scenario types below. Each cell55 is `spec <Name>`, `n/a: <domain reason>`, `recorded: <why not expressible>`,56 `n/a: technical` (closed list), `open: <case>`, `question: <id>` or `gap: <code>`. "Fewer specs" is never a reason; a57 declaration (constraint, policy) or another command's denial is not a spec.585. **Per read model, decide the shape**: single-transition specs only, or also a lifecycle59 family (cumulative givens). Write the decision and reason in the matrix, before drafting any60 payload: one line per read model. One schema reused for every command and view may indicate61 the per-view judgment was skipped: check for a recorded reason per view before concluding.626. **Example data**: a small cast per feature; reuse only where meaning agrees; preserve63 existing intentional fixtures (`references/scenario-catalogue.md` "Example data"). Shared64 fixtures may live as typed `example`s in another document beside the declarations they type65 (`cratis-screenplay-specifications` `references/examples-and-routes.md`).667. **Draft commands** for each applicable scenario type below. Vary only the value67 under test in a rejection. Read specifications'68 [persona callers and cases](../cratis-screenplay-specifications/references/persona-callers-and-cases.md)69 when sharing a validation matrix or choosing synthesized versus explicit callers;70 cases are not fixture examples and do not group unrelated behaviors.718. **Separate view pass**: population, each update, accumulation, removal (with a surviving72 row), absence, ordering. Mark lifecycle branches. Views combining sources must73 tolerate any arrival order. Pin a child before its parent (Requires Screenplay 4.149.1 or later):74 given child, then parent, then read model; "parent never arrives" leaves the75 child absent. Evidence/example: `references/view-and-story-specs.md`.769. **State-dependent rules**: use `reads` plus `require` over authoritative state;77 eligible views opt into `command reads protected` (v25). Cover present/absent reads,78 refusal and denial; matching decide/commit changes are conflicts, not refusals.79 Read [protected reads](../cratis-screenplay-command-surface/references/protected-reads.md)80 for admission and Stage refusal; legacy/refused shapes remain marked unenforced81 with a named target mechanism. Forbidden:82 caller-supplied copies of state in `require`, boolean attestation inputs (`confirmsX ==83 true`) and rules hidden in `handler`/hint prose. Never drop an unresolved given or assertion84 to make a spec compile: record the blocked case and continue.8510. **Validate** the batch (V1, warnings as errors); V2/V3 when executable or renderable. Fix diagnostics without dropping intended rules, prerequisites or assertions, then rerun the applicable verdicts; if the chosen mode cannot admit the construct, preserve it and report the blocked scope explicitly. The86 phase report carries the matrix path, spec names added or changed, `recorded`, `open` and87 `gap` cells and open questions.8889## Scenario types (decide each per command; detail in `references/scenario-catalogue.md`)90Decide each of these per command: happy path; rule rejection (one spec per rule, exact pinned `then error`); denial (`given caller` without the policy, `then denied`, one per gated command and query); state violation; duplicate or retry; competing claim; alternative path; ordering; external failure; compensation; evolution; and the view pass. Read [references/scenario-catalogue.md](references/scenario-catalogue.md) ("Scenario types at a glance") for each type's question and usual shape.9192For command Date/DateTime ordering, cover increasing and inverted intervals,93equality across offsets, a one-tick boundary and **each participating DateTime94input without an offset or Z**. That last case rejects with Validation before rules,95even if a condition short-circuits or a production is skipped. `then` stays ordinal;96never replace payload text with an equivalent instant. Read the complete97[retention-window specifications](../cratis-screenplay-command-surface/references/date-comparisons.md)98for the compiler prerequisite, admitted positions, refused `today` and Stage's v2699refusal. Missing-offset runtime coverage needs an evaluator-request or target input100test: a typed `.play` fixture rejects that value at binding with PLAY0273, before runtime.101102For recovery, `when redelivered <Event> to <Reaction>` must select one definitely103matching effective given and no undecided candidate. It delivers only to the named104reaction without re-appending the input; `then no events` explicitly checks no105new facts from the settled cascade (ESM v17). Read `references/scenario-catalogue.md`106("Redelivery selectors") when choosing retry/no-effect cases or `stream`/`no stream`.107Read [query rejection examples](../cratis-screenplay-specifications/references/query-rejections.md)108when specifying malformed keys/filters versus valid absence (ESM v18).109Requires Screenplay 4.157.0 (`screenplay --version`) for v17, 4.161.0 for query110validation/error assertions; older tools do not execute these contracts.111112**Once, idempotent, exactly once are different claims.** `unique event` proves a once-only fact,113not successful retry handling or an exactly-once external effect. Name the claim114proved and keep other guarantees as target requirements; recovery cases are in115`references/scenario-catalogue.md`.116117## Rules118### Compiler contracts119- At most one `when` action; with none, assert only read-model or query outcomes.120- `then` events are exact in count and order (`then events in any order` relaxes order only).121- Command denial: `then denied` with no success or error outcome. Read-only query denial:122 `then query <Query>` with `arguments` and no `result`, then `then denied`. Every gated command123 or query spec needs `given caller` or `given caller as <Persona>` (module and feature gates count); an authorized scenario124 gets no inferred fixture (PLAY0389). Unauthorized is never `then error`.125- Duplicate and competing specs use `when <Command>`; `when append` is for projection and126 automation triggers, consumed public events driving captures, and for a127 constraint the command's own validation would reject first.128- `null` only for optional read-model properties; constraint messages are copied verbatim.129- Executable-only binding checks (PLAY0350/0352/0388/0389/0273) do not show in V1: run V3.130131### Modeling defaults132- Every slice has at least one specification at the application boundary.133- One behaviour per spec; names read as sentences: `Reserving...`, `Rejecting...`, `Refusing...`134 (denial), `<View>LifecycleN<State>` for families.135- `for` on every given, appended and expected event (plain `produces <Name>` too; inline `produces event` omits it), and on the `when` command where the136 destination matters. A competing-claim given needs a *different* `for`. A given without `for`137 belongs to the event source the specification acts on; state `for` when the command appends to138 several event sources or an assertion depends on the given's source, and never assert139 `$eventSourceId` of a sourceless given. Read140 [examples and routes](../cratis-screenplay-specifications/references/examples-and-routes.md#givens-without-an-event-source).141 Foreign event fixtures feeding a capture may omit `for`; supplied `for` is142 opaque source text, not the capture's content key.143- Format rules belong on a `concept`: give each concept rule representative acceptance,144 rejection and boundary specs once (through one command that carries it), not on every use;145 never `n/a` automatically. Date/DateTime comparisons are command-only, not concept rules.146 Include a whitespace-only rejection for text `not empty`:147 this changes outcomes in every ESM version (Requires Screenplay 4.151.0 or later). Unicode/identity boundaries148 and evidence: command-surface `references/validate-rules.md`.149 A business rule gets one rejection spec if an expert could recognize it from its message;150 binder-enforced shape is no scenario (catalogue §2).151- Persona Cannot lines are intent: each needs an executable gate plus a `then denied` spec whose152 caller is a synthesized persona witness or an explicit gate fixture, else record a gap.153- Descriptions are not rendered: a rule only in prose is unenforced; make it a rule layer, a154 spec or a recorded target requirement.155- Prove projections with events (`given`/`when append`), not `given readmodel`; seed read models156 only for performer-backed views or commands that decide on view state. A query `performer` is an opaque read157 (information `PLAY0270`, not `PLAY0268`): it is left out of the executable model, a spec that reads it is158 left out too and the other specs still run, so mark it `gap` for the executable modes ([version gate](../cratis-screenplay-toolchain/references/executable-subset.md#code-attachments-what-binds-what-never-does)).159- No contradiction between a family and single-transition specs of the same view.160161### Quality checklist (adapted from the TrogonStack scenario checklist; `references/provenance.md`)162Read [references/quality-checklist.md](references/quality-checklist.md) before reporting a scope spec-complete. No command has only two specs (success and one rejection) unless every other type was reviewed and found inapplicable; a model with dozens of command specs and no read-model spec is not scenario-complete.163164### Review questions165Read [references/review-questions.md](references/review-questions.md) for the race, retry, arrival-order, correction and cross-context questions.166167## Public-event coverage (ESM v9)168169Outbound publication needs `when append <private>` and `then <PublicEvent>`.170Captures over public events use `given <FromEvent>` / `when append <FromEvent>`,171not capture records (PLAY0701). Read [references/public-event-coverage.md](references/public-event-coverage.md)172when specifying public events or routed producers and observers.173174Record captures distinguish first sight from updates: first root/child/nested175records are added only, so field guards need `given capture` for the same key.176Use a separate `when added` append when initial observations should produce a fact.177Read captures-and-reactions `references/record-capture-specifications.md` for the178prerequisite and runnable cases. Include first, changed and unchanged rows in the matrix.179180## Reaction chains: one slice per specification181A 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.182183## Gate184A scope is spec-complete only when: the matrix has no `open`, `question` or `gap` cell (or the185scope is reported as explicitly incomplete); V1 passes with the tool named in186`cratis-screenplay-toolchain`; for executable or renderable scope V3 is binding-ready.187188## Verify189- Re-inventory declarations at the reported revision: every applicable obligation maps to an190 existing spec whose givens, action and assertions exercise it.191- Commands and read models are checked in separate passes; each removing projection has a192 populated-then-removed spec.193- V1 passes (standalone `screenplay` required when cascades are specified); report tool and194 version.195- Run V4 through standalone `screenplay test` or MCP `run-specifications`;196 propose → review → run with `proposalId` →197 apply (Requires Screenplay 4.145.0 or later). PLAY0285 (impossible `then`) unbinds198 the whole model; no spec runs.199 if not executed, report the actual host/input reason, not a blanket no-route200 claim. Stage's runner is target-engine evidence, never V4; V1/V3 do not prove pass. V5 is "not run" unless rendering was attempted; report admission, publication, build and201 tests separately.202- Match guarantees to evidence: `.play` outcomes, in-process Chronicle scenarios and real-kernel203 tests are not interchangeable (`references/chronicle-verification.md`).204- Reference example `references/berth-reservations.md`: compiles with warnings as errors.205206## Route near misses207Read [references/neighbouring-skills.md](references/neighbouring-skills.md) when the work is grammar, rules, projections, reactions, invariant placement, review or C# specs.208209## References (load on demand)210- `references/scenario-catalogue.md` - each type: ask, applies when, n/a when, shape, traps; example data. Read when deciding applicability, eliciting cases or choosing example data.211- `references/view-and-story-specs.md` - view specs, lifecycle families, ordering, lag. Read before deciding each view's lifecycle family and drafting view specifications.212- `references/coverage-matrix.md` - obligations from declarations, template, worked matrix. Read before constructing or reconciling the coverage matrix.213- `references/scenario-examples.md` - compact worked examples per category, good and bad forms,214 list and todo-list views; copied from the complete `references/invoicing-dues-example.md`215 (runnable) and, for compensation, `references/invoicing-dues-design.md` (design mode: holds the216 stored-state rules, does not bind). Read `references/scenario-examples.md` when drafting a category and you need good/bad or worked specification forms; read `references/invoicing-dues-example.md` when you need the complete executable declarations behind the invoicing excerpts; read `references/invoicing-dues-design.md` when specifying stored-state invoicing rules or their compensation scenarios in design mode.217- `references/scenario-workshop.md` - facilitation guide for group scenario sessions. Read when facilitating a group scenario session.218- `references/chronicle-verification.md` - guarantees that need more than a `.play` outcome. Read when a claimed guarantee needs in-process or real-kernel evidence beyond `.play` outcomes.219- `references/spec-forms-by-mode.md` - admitted forms in design, executable, renderable. Read after choosing the mode and before drafting its admitted specification forms.220- `references/berth-reservations.md` - complete compiled example (marina guest berths). Read when you need a complete design-mode example of a coverage matrix realized as specifications.221222## Lineage223Attribution and adapted sources: `references/provenance.md`. Read `references/provenance.md` when checking attribution or how an adapted practice differs from its source.