| User-task value | A small configuration may solve the problem, while platform ambitions encourage premature breadth. |
| Current material | Users need trustworthy status and editions, while publication and collection membership do not establish currentness by themselves. |
| Tool assistance | Search, PLM, CI, prompts, and automation can reduce burden, while outputs and interfaces must not acquire authority. |
| Organizational precision | Relations and constraints may need an A.22 structure, while a proposal must remain useful before selection facts exist. |
| User and provider boundaries | Human and non-human user Systems and provider Systems can contribute differently, while vague “support” wording can merge performance, service, capability, permission, authority, and result. |
| Testing | Actual user Work is needed to test the arrangement, while a successful bounded task proves neither general capability nor Method effectiveness. |