cratis-application-slice-conformance

Slice conformance: the code matches its contract, element by element

Purpose

Hand-written code drifts from what was agreed in two directions: something agreed is missing, or something nobody agreed is there. This skill is the check that closes both, plus the rules for specifications, re-delivery and the final status. It does not decide what a slice should do; the contract does.

Model-first rule: when a .play model covers the slice, the model is the contract and the code is derived. Code is written only for scope the renderer rejects, adapters and other infrastructure. Change behaviour in the model first, never in managed output.

When to use / when not

• Use: implementing or finishing a slice by hand; gap-fill after a render; re-delivery after a model or outline change; reviewing slice code; a hand-over where "done" must mean something.
• Not for: the choice of behaviour (cratis-screenplay-slice-design, cratis-chronicle-event-modeling); how to write specifications (cratis-application-slice-specifications); the render workflow itself (cratis-screenplay-render-and-gap-fill).

Startup verification for Automation and Translation

• Real startup participation. A ReactorScenario bypasses observer registration, so it cannot show that the application subscribes the reactor. Verify, through the repository's integration route or a startup check, that the real application discovers the intended reactor (its assembly is scanned, per the repository's discovery convention), that it observes the intended event store and event sequence, and that a trigger event delivered there reaches it. Report this apart from the in-process specifications.

Product facts

This skill is a method: it names no API of its own. When the Screenplay skills are installed their SKILL.md (in cratis-screenplay-toolchain) explains how to read the installed tool versions.

Fact used here	Source
Where each rule lives (validator, Provide(), handler result, constraint, exception)	rules/vertical-slices.md "The decision matrix"
A customization never makes a rejected model renderable; managed output is never hand-edited	Stage (Customizations/ is the unmanaged seam; managed output is regenerated)
Attached file or inline command handlers are refused with PLAY0800, a permanent requirement for a code implementation attachment (Requires Screenplay 4.210.0; older binders report PLAY0268); pending handlers with unconditional productions bind v23 as described commands, but reached bodies are Unsupported ImplementationBody and Stage refuses STAGE-IMPL-002 even in Stub mode	Screenplay and Stage; use the model as the gap-fill contract