PM-CND-0020
A failed Condition leaves the State unchanged and emits an outbound event naming the violated constraints
When a Condition does not hold, the transition MUST NOT take effect, the object's data MUST NOT be stored, and the implementation MUST send data representing the untrue condition.
Non-normative: an unusually good design choice, and worth not losing. A rejection is not an error — it is a modelled outcome that carries, in machine-readable form, which constraint was violated. That makes rejections queryable, explainable to a user, and directly consumable by an automated caller deciding what to do next. Most systems return a failure; this one returns a reason.
The blog says the same thing in its own words: "an outbound event is going to happen spelling the constraints generated by the Condition and the object State is kept as in the start of the transition."
SRC-PATENT MUST · draft · area CND · since 0.1.0
Verbatim quote
if the condition is untrue the valid state transition is not valid and the processor is controlled by the computer program code to perform sending condition constraint data representing the untrue condition
Source
frozen 2026-09-08T095618Z · sha256 2d6b61ee55a4688d… · live