E.10:0.2c.12 - route, branch, handoff, path, trajectory, move, flow

Recover the movement, control, and temporal relation set before using these words:

• E.10.MOVE for project-move, first-move, working-move, next-move, pattern-use, work-entry-readiness, architecture-candidate-use, call-planning next-action, or other move-like wording whose direct FPF target is hidden;
• A.16 local move;
• A.16.0 trajectory account;
• A.19, C.2.2a position in characteristic space or state space;
• B.2.5 for a two-sided supervisor-subholon feedback relation; use the direct subject pattern for any other control or control-layer relation and C.30.LCA for a control-structure view;
• process handoff;
• selector relation or selection mechanism;
• work transfer;
• E.18 graph path or PathSlice expression;
• A.6.3, A.6.4 episteme morphism or retargeting.

When handoff instead names an entity, package, result, delivery, transfer, acceptance, or receiving-use boundary, apply A.6.P.WMR to that exact relation-bearing claim. Use E.10.MOVE for a process-baton or project-move case only when that movement itself is current; a handoff record or package remains an episteme or another entity, not the transfer.

If no movement, control, and temporal relation is being made, keep the word ordinary and non-authorizing.