SYSE.42:10 - Architectural Rationale

Execution binding sits between action selection and the receiving work. Keeping it explicit makes three repairs distinguishable: choose another action, repair the aid/interface, or correct input binding and result use. A good calculation on the wrong numbers and a correct return that the next step ignores need different repairs.

A deterministic direct call is preferable when its input mapping already suffices. Model participation is useful where interpretation is needed, while the contract remains the basis for actual effects.