A.15.8:4.1 - Keep the governed object and non-kinds explicit

This pattern introduces no root U.ExtendedPerformer, U.WorkSystem, U.WorkState, U.Attention, U.Memory, or joint-cognition kind. It does not admit an arrangement as a System, performer, Agent, Structure, ArchitectureRelation, or capability holder merely because its constituents are coupled or jointly useful.

In the actual branch, the governed world-side focus is one exact admitted U.Work occurrence. In the prospective branch, it is one exact present U.WorkPlan; proposed performance stays declaration-local content of that episteme. Supporting Systems and values may be inside or outside a selected containing-System boundary. Their contribution, dependency, access, update, control, or other relations must be directly declared and supported when the result relies on them.

An arrangement remains ordinary prose unless another use needs an exact U.Structure admitted under A.22. An architecture claim enters only through C.30. A configuration account can designate several independently governed Systems and values without making them one whole or using a plural EntityOfConcern.