Open	Who acts
Core → State Model Designer; Reason Policy Designer; Model publications	Model author and independent reviewer

Publish an exact state/reason contract for a named consumer so later edits to authoring data do not silently change running behavior.

Input shown on screen	Enter or select	Explain its significance
State dimension / state value	The lifecycle aspect and allowed states	States in different dimensions are not interchangeable.
Transition	Allowed prior state, action and resulting state	The transition defines a permitted move, not its execution.
Reason domain / reason applicability	Allowed reason and narrative requirements	A reason can be restricted to a particular action or transition.
Consumer / publication reference	The designated consuming module and returned snapshot	The consumer binds an exact approved version/hash.

Step	Demonstrator action	Point out on the screen
1	Define the required states and transitions in the selected dimension.	The initial, terminal and allowed intermediate moves can be explained.
2	Define reason values and applicability, including required narrative.	A reason is valid only in its intended context.
3	Propose model publication for the chosen consumer.	The proposal captures the exact source definitions.
4	Have the eligible independent reviewer compare and decide that proposal.	Approval yields a controlled publication reference and hash.
5	Use Check a published transition with a valid action/reason combination.	The evaluation allows the configured move.
6	Repeat the non-mutating check with a disallowed transition or missing required narrative.	The evaluation rejects it without changing a business record.

Evidence to show before continuing

Show one allowed and one rejected evaluation plus the immutable published reference.

Condition to explain	Supported recovery
Sources changed after proposal	Prepare a successor proposal; do not approve a stale snapshot.
The consumer still uses old behavior	Inspect its bound publication ID/hash and adopt the new publication through its supported change process.

Hand the publication reference to the consuming module, which still owns business execution and authorization.