A.15.1:1 - Problem Frame

After we have separated which system-role assignment obtains (via U.SystemRoleAssignment), what capability is being relied on (through an A.2.2 qualified holder-ability claim), how in principle the Work is done (the exact U.Method), and which claim-bearing episteme, if selected, describes that Method (U.MethodDescription), we still need a precise concept for what happened as performed Work in real time and space.

Every Work individual has an A.13 core basis for every claimed actual performer System, an independently grounded performance history, at least one enacted Method, temporal extent, and at least one locally declared containing-system relation. Several such relations may obtain under different exact system boundaries. The A.13 core already contains one obtaining assignment for its scope, situation, and window; an F.6 relation may later use that same occurrence but is not a Work-membership premise. A Work stands in a direct work-to-referent, binding, or resource-use relation only when that relation obtains world-side; none is a field stored in the occurrence. A separate assertion or description may designate that individual and state the relations, but the episteme neither creates the relations nor becomes the Work occurrence.