pub const UNKNOWN_OPERATION: &str = "turnframe.operation.unknown";Expand description
The rejection code a workflow uses when compile_act does not recognise an
operation at all.
§Why this one string is reserved
A workflow declares its operations in interpretation_catalog and turns
them into commands in compile_act. The two are different functions and
nothing relates them, so an operation added to one and forgotten in the
other fails as far downstream as a mistake can: the catalogue offers it, the
interpreter proposes it correctly, and the user is told his request could
not be carried out — on a sentence that was understood perfectly.
A workflow that returns this code says which of the two it is, and two
things follow. The state explorer walks every reachable state, asks each
state’s catalogue whether compile_act knows its operations, and reports
the ones that come back with it — the drift becomes a test failure in the
workflow’s own suite instead of a sentence a user reads three times. And the
runtime treats it as its own refusal rather than the domain’s, because a
catalogue and a compiler that disagree is a defect in the deployment and not
an outcome for the user.
A workflow that uses its own code keeps today’s behaviour exactly: its words reach the user and nothing checks the drift. The check sees what the workflow declares, and this constant is the declaration.