Source changed 2026-10-03 02:22:15 UTC · snapshot created 2026-10-03 03:38:22 UTC · last check 2026-10-03 04:00:05 UTC
A.2.2:4 - Separation From Neighboring Values
Source wording
Recovered FPF values
“Engineer role can approve the design.”
Treat bare role as an E.10.ROLE trigger. If it means classification, recover local kind EngineerSystemRole and a C.3.2 judgment for an admitted System. If assignment identity matters, name the assignment occurrence and its declared U.SystemRoleAssignment species. Do not infer permission, capability, action, responsibility, or approval Work from either claim; add a capability claim only for the measured and qualified ability of the holder System, and use the permission and performed-Work relations when those claims are made.
“The robot is assigned as welder.”
Name an assignment occurrence with the robot as holder and its declared U.SystemRoleAssignment species, whose assigned-kind position has local domain WelderSystemRoleKindDomain; the occurrence supplies WelderSystemRole as the value admitted by that domain. Add a capability claim only if the claim also says that the robot can meet a welding envelope and measures.
“The solver has the scheduling algorithm.”
First identify what the possession phrase claims: a deployed-software relation, a capability statement about the solver system, a reference to exact U.Method, or a candidate claim-bearing episteme. Apply A.3.2 only to the last candidate; it is U.MethodDescription only when its exact EntityOfConcern is one admitted Method and at least one substantive claim says how that Method is done. The phrase alone establishes none of these.
“The report has evidence capability.”
Recover the report’s evidence-use relation. A separate capability claim needs a system that can perform evidential work.
“The team did one successful run.”
U.Work occurrence; a broader capability claim needs justified conditions, attained measures and current support.
“We promise five-day close.”
Promise content and commitment; the provider’s qualified ability and its fit to the promised result need separate support.
“The architecture provides resilience capability.”
Architecture-characteristic or Q-Bundle material under C.30, C.32.HCS, C.32.ACS, and C.25; add a capability claim only when it states a named holder System’s ability to produce or maintain a result class within declared conditions and bounds. Resilience characteristics may constrain a capability-fit condition; they are not capability by name.