A.1:1 - Problem Frame
FPF cannot use system as its universal root. A pump, theory, software product, legal code, dashboard, research program, work occurrence, discipline, and team can all be objects under concern, but they do not all act, exchange matter, execute methods, or carry physical ports.
A.1 separates four questions that are often collapsed:
- reference: what can be individuated as
U.Entity; - part-whole treatment: which exact candidates satisfy the constructive recognition criterion for
U.Holonor another already admitted public holon kind; - acting eligibility: which recognized holons also satisfy the kind-specific criterion for the already admitted
U.Systemkind; - claim-bearing knowledge: which recognized holons also satisfy the kind-specific criterion for the already admitted
U.Epistemekind.
Entity identity and world-side holon recognition have a context-independent base. Claim scope, effective reference scheme, and selected model-use structure can qualify a particular assertion or use, but none identifies the candidate, makes the constructive criterion true, or admits a public U-kind.
Other admitted holon kinds are not created by title, by filling one locally named slot, or by ordinary-language label. They remain governed by their direct patterns. Current accepted examples include U.Method under A.3.1, U.Work under A.15.1, and U.Discipline under C.20. BoundedModelUseStructure under A.1.1 is U.Structure, not a holon kind.