| Method-content coherence | Rows must return to one current MethodDescription or candidate account, while every receiver/action pair keeps its own selection and limits. |
| User-action fit | A representation should expose the claim that changes one action, while adding every available claim raises burden and hides stops. |
| Status preservation | Plans, candidate claims, and observed Work can help explain a Method, while representation cannot promote their status. |
| View discipline | Project, process, and case viewpoints can illuminate one Work occurrence, while viewpoint names alone establish neither a view nor co-use for another action. |
| Formal precision | A mathematical lens can expose a Method relation or unfolding, while a node-link appearance can overstate correspondence or graph structure. |
| Reliance proportionality | Reversible orientation may need only a direct result and visible limit, while consequential use may require an exact A.10 path and disposition. |
| Maintenance cost | A persisted profile can aid reuse and refresh, while every temporary presentation need not create a second C.37 account, collection, structure, or edition. |