Library / First Principles Framework (FPF) - Core Conceptual Specification
Jump to passage
In this reading

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 05:29:54 UTC · snapshot created 2026-10-03 05:30:57 UTC · last check 2026-10-03 07:05:20 UTC

A.2:12 - SoTA-Echoing

Practice lineSource and statusFPF mutationPractical consequence
Current foundational-ontology work separates role-like classification, relation participation, aspects, and situations instead of treating them as one category.Almeida, Guizzardi, Sales, and Fonseca, gUFO, 2026 preprint; current comparator, not an imported hierarchy.Use local C.3 kinds for work-facing classification, direct relation species for assignments, A.6.5 for participant slots, and separate state and episteme-use relations.Different classifications and assignments do not create system subtypes or role parts.
DOLCE separates endurants, perdurants, qualities, abstracts, dependence, and constitution but does not itself settle FPF system-role-kind or assignment identity.DOLCE 2022 axiomatization; bounded comparator.Preserve system, kind, relation occurrence, Work, quality, and episteme distinctions under their FPF governors.A borrowed category label cannot replace the local identity and predicate law.
DDD makes model applicability local and Context Mapping a method applied to actual model-use boundaries.Evans, Domain-Driven Design Reference (2015) and current context-mapping practice.Use a selected BoundedModelUseStructure only in the receiving claim it changes; keep the Method and performed Work separate.A plant assignment needs its local kind and species, not a universal context participant.
FPF relation and episteme discipline separates description and publication from evidence, reliance, source use, and the systems performing Work.Current C.2.1, A.6.REL, A.10, A.15.4, and E.17 line.Require an admitted system for system-role classification and keep each episteme in the relation that makes its use relevant.A team can use a standard as a constraint source without making the standard a performer or role holder.

A modeling notation does not decide the identity of a system-role kind, classification judgment, assignment occurrence, participant slot, responsibility relation, or Work.