E.24.UK:11 - SoTA Decision for Durable Kind Admission

The bounded question is practical: when should a reusable distinction become a durable public kind, when is a local classifier or direct relation enough, and what identity commitment does each choice add? Compare alternatives at the effort of repairing or authoring one FPF pattern—not at the effort of adopting a whole enterprise ontology.

Current line	Strong contribution	Failure mode or extra effort for this question	FPF decision and receiving locus
gUFO, March 2026, with its type typology, intrinsic and relational aspects, situations, and higher-order types; ISO/IEC DIS 21838-5 is a draft under development, not a published standard (ISO status observed 2026-09-25)	Rich distinctions expose whether one bearer gains a classification or a distinct dependent individual needs grounding.	Using the whole typology first adds a foundational-ontology mapping and can choose an imported category before the FPF receiving use and local alternative are known.	Adapt the same-individual/distinct-individual question in the admission tree and the WorkPlan, capability, role, phase, and quality cases. Reject automatic import of the taxonomy or its labels as FPF admission.
Current BFO 2020 artifacts, maintained for the ISO 21838 top-level-ontology line	Strong formal separation of dependence, continuant mereology, process, role, and disposition.	Adopting the whole upper ontology is expensive for a bounded FPF authoring decision, and its categories do not decide whether one FPF name deserves durable public reliance.	Adopt the warning that dependence is not parthood and require an exact dependence rule when a distinct dependent individual is actually needed. Reject BFO classification or official status as the admission gate.
Modular ontology-design-pattern work, including MODL, and the emerging LLM-assisted ontology-engineering direction	Reusable small modules reduce duplicated modeling; the newer direction makes modularity important when assisted changes become cheap and frequent.	Pattern discovery and adaptation still cost work. The LLM paper states a research direction, not evidence that this pattern’s eight conditions or result architecture is best.	Adopt existing-governor reuse and bounded modules in steps 2–4. Treat LLM assistance as a reopen pressure only, never as the load-bearing admission basis.
Current operational OBO Foundry principles	Scope, versioning, textual definition, reuse, identifiers, and operational conformance make shared ontologies maintainable.	These governance and publication checks do not by themselves settle world-side kind identity, membership, dependence, or the difference between a local classifier and durable FPF kind.	Adapt explicit scope, reuse, version, and reopen boundaries in the decision and registry. Reject conformance to a publication regime as proof of admission.
OWL 2 semantics and ISO 704:2022	OWL cleanly separates classes, individuals, properties, and semantics-free labels; ISO 704 separates objects, concepts, definitions, and designations.	These are mature lineage baselines, not a current low-effort method for deciding FPF’s durable/local/non-kind boundary or its identity dependence.	Adopt class/individual/property separation, same-individual inclusion, and naming-after-object recovery. Reject a class axiom, label, definition, or designation as sufficient admission.

Selected non-dominated contribution. None of these lines supplies the same progressive cost boundary. E.24.UK first reuses an accepted kind, then tries one bounded C.3 classification, then recovers a direct relation or other non-kind object, and only then admits a new durable kind for repeated cross-pattern reliance with an exact membership or dependence rule. At comparable authoring effort, this reduces ontology commitment while preserving exact identity, non-member, reliance, and reopen tests. The gain is not universal superiority over a foundational ontology; it is a better effort/traceability trade for FPF pattern repair.

The shared E.24 decision is part of that gain. It prevents the ontic and public-kind questions from being answered by two incompatible cards. The U.Kind case retains the independent root admission and returns direct rule use without an additional durable ontic; the separate U.SubkindOf settlement remains under its own direct relation and receiving-use grounds. In the capability case, recovery returns qualified holder-ability claims and rejects an unnecessary additional kind. In the WorkPlan case, the same episteme gains dependent membership without a second plan. A role or phase near-miss stays with a direct relation or local kind; HighRiskPump@Turnaround2026 stays a local C.3 distinction; and public spelling waits for F.18 after the object is settled. A source may model a pressure quality or an obligation-bearing relation as a separate dependent individual. FPF does so only when a direct rule identifies that individual and its exact dependence. A measurement value, assertion, participant pair, agreement document, or relation record cannot admit it by representation alone.

The main remaining failure risks are also explicit. The progressive route can under-admit a distinction if a bounded use hides later cross-pattern reliance, or over-admit it if repeated wording is mistaken for stable membership. Reopen when a stronger current alternative offers the same identity assurance at lower effort, when an admitted kind loses its member/non-member or continuity test, or when a worked counterexample changes the same-individual, identity-dependent, local-kind, or non-kind decision.