A.2.2:11 - Consequences

Benefits.

• Planning separates “can do” from “is assigned now”.
• Method steps can name capability thresholds without putting extra meaning into system-role-kind names.
• Work records can be judged against the capability claim and fit predicate current at the time of work.
• The internal ability and measured envelope supporting a promise are explicit.
• Composite-system ability can be stated at the right holder instead of scattered across parts.

Costs.

• Capability tables need envelope, measures, and currentness fields.
• Teams need to stop using system-role labels or assignments as shortcuts for ability.
• Some old “function”, “service”, “process”, and “algorithm” sentences need kind recovery before they can be used in FPF.

These distinctions let practitioners check authorization, ability, method, and performance separately.