| System-role-kind-as-capability | “The inspector role can detect this defect.” | Treat bare role through E.10.ROLE; retain the exact local system-role kind and any independently obtaining assignment, then state capability for the holder System only when the bounded capability claim and current support justify it. |
| Assignment-as-capability | “Assigned, therefore able.” | Use A.2.1 for assignment and A.2.2 for the qualified holder ability. |
| Capability attributed to a procedure | “The procedure has capability” | Keep capability with the holder system. |
Unjustified U.MethodDescription admission | Treating “the solver has the algorithm” as sufficient for U.MethodDescription admission. | Treat procedure or algorithm wording as a cue to one candidate episteme only when that is the actual object; admit it as U.MethodDescription through A.3.2 only after its exact EntityOfConcern is an admitted Method and a substantive claim says how that Method is done. |
| Work-as-capability | “We did it once, so we can.” | Keep the work occurrence; add a separate capability claim only when envelope, measures, and currentness are justified. |
| Promise-as-capability | “The SLA is our capability.” | Use promise content or commitment for what is offered; capability is the internal measured ability that makes the promise credible. |
| Episteme-as-holder | “The report has assessment capability.” | Use evidence, source, status, or assessment relation for the episteme; capability holder remains a system. |
| Unbounded capability | “The tool can machine titanium.” | Add material grade, tolerances, feed range, environment, version, qualification window, and measurement evidence. |
| Capability threshold in system-role-kind name | HighPrecisionWelderSystemRole hides a measured threshold. | Keep the system-role-kind name free of the threshold; put precision in the Method-side admission or fit condition and the holder capability claim. |
| Characteristic-as-capability | “Low latency is a capability.” | Use U.Characteristic with declared scale for latency; add a capability claim only when a named holder can produce a result class within an envelope that includes the latency measure. |
| Q-Bundle-as-capability | “Resilience is our capability.” | Use C.25 for the composite quality family; cite a capability only when a currentness assessment supports reliance on a qualified holder ability and a fit predicate tests the relevant bundle slot. |
| Architecture-row-as-capability | “Maintainability row gives capability.” | Use C.32.ACS for the architecture-characteristic criteria row; it may constrain a capability-fit condition but does not establish the holder’s ability. |