| Independent contribution and shared meaning | Contributors can avoid editing one another’s modules, but someone must understand both sides of each required new intersection. |
| Openness and coverage | A receiving application needs known behavior for its admitted inputs; future contributions can introduce cases outside that promise. |
| Reuse and recursive reach | An old handler should remain reusable when a new form occurs below it, while recursive calls must reach the assembled implementation. |
| Early checking and late composition | Static interfaces can expose missing capabilities before execution; late selection permits further combinations and introduces visibility and loading conditions. |
| Extension and preservation | Adding a body is easy; showing that old calls still select equivalent behavior depends on the dispatch and effect model. |
| Flexibility and total cost | Generic interfaces, joining bodies, diagnostics and deployment can cost more than maintaining a closed set of cases. |