E.10.MOVE:4.2 - Trigger groups
After E.10 selects this pattern, use these cue groups to find the appropriate recovery branch while an action-changing ambiguity remains:
move,step,action,application,solution, andnext action;readiness,ready,full kit,work entry,committed, andlaunch-ready;movement,direction, orshiftused for an expected evaluation-result change;route,workflow,process,path,trajectory,loop, orflowused for an unresolved claim about a path, ordering, or what it represents; use the direct exits below;- imported source wording such as TameFlow
MOVE.
The cue group locates a recovery branch. The recovered claim and its direct owner determine the governed-value kind.
E.10.MOVE:4.2.1 - Readiness exits
Stay in E.10.MOVE only while readiness, ready, full kit, work entry, or a similar cue still hides which governed value is meant. Once that value is recovered, use the direct pattern:
| Recovered claim | Direct pattern |
|---|---|
| A patient, system, or other subject has a value in a still-hidden state frame | A.19.SPR, then the subject pattern that defines or tests the recovered value. |
| An exact system-role assignment satisfies a by-value assignment-state condition | A.2.5; keep its predicate, world-side relation occurrence, and assertion episteme distinct. |
| One intended performance satisfies a work-entry criterion | A.15.5; its local readiness result is not a gate decision or performed target Work. |
| A named gate decides whether one bounded action or transition may proceed under an applicable profile | A.21 combines independently established check results into a GateDecisionResult; publication is a separate optional use. A ready label or readiness result alone is not gate passage. |
| A publication use, permission claim, preparation Work, or target Work is meant | E.17, the direct permission pattern, or A.15.1 as applicable. Keep each claim separate. |
If the direct pattern and value were already clear, bypass this table and use that pattern immediately.