fpf.tools
Library / First Principles Framework (FPF) - Core Conceptual Specification
Jump to passage
In this reading
Source · lines 19480–19491

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 16:02:47 UTC · snapshot created 2026-10-03 16:03:51 UTC · last check 2026-10-03 16:25:20 UTC

A.6.RSIR:11 - SoTA-Echoing

This pattern does not introduce new external SoTA sources beyond the source uses already admitted by E.24 for ontic introduction. It applies those source uses to the narrower RSIR recovery problem.

Practice or source lineWhy it matters for RSIRFPF adoption in this pattern
Modular ontology design-pattern work, including MODL, MOMo, and commonsense ontology micropatterns such as Shimizu and Hitzler 2024 and Eells, Dave, Hitzler, and Shimizu 2024.Current ontology-engineering lesson: use small reusable ontology structures without copying local slot doctrine across patterns.Adopt and narrow: RSIR does not become an ontic registry. It recovers the current governed object, leaves participant meaning and actual participation with the direct relation pattern, uses A.6.5 only for a current RelationSignature SlotSpec, uses C.29 or the exact representation pattern for positions and correspondence, and uses E.24 only for durable ontic decisions.
Ontology-interoperability lifecycle work such as Qiang 2025 and 2026.Current caution that overlapping labels and conflicting local concepts become expensive if not settled before reuse, matching, and validation.Treat interface, slot, function, Method, concern, and bare role as recovery cues until the current EntityOfConcern, direct relation and participants, declaration, any representation position and correspondence, and direct pattern are named by use; bare role starts at E.10.ROLE.
Process-representation ODP work such as Norouzi, Hertling, Waitelonis, and Sack 2025.Current warning that process and workflow ontologies often hide implicit patterns from domain users.Adapt for RSIR source labels: “process”, “workflow”, “method”, “function”, “parameter”, and “interface” may remain useful source labels, but they do not carry FPF-governed content until the direct method, work, transformation-flow, role, slot, publication, or evidence pattern is selected.
gUFO, UFO, and OntoUML role, relator, situation, and high-order type practice, including Almeida, Guizzardi, Sales, and Fonseca 2026.Current foundational-ontology warning against flattening system classifications, assignment occurrences, participant meanings, declaration-local slots, representation positions, status classifications, and evidence uses into one taxonomy.Use only as a bounded comparator. FPF recovers exact local system-role kinds and direct U.SystemRoleAssignment species separately; direct patterns retain participant meanings, A.6.5 retains declaration-local SlotSpecs, C.29 retains positions and correspondence, and episteme uses retain their direct relations.
Current engineering architecture practice around functions, ports, modules, interfaces, signatures, and views.Accepted internal-practice constraint from A.6.M, A.6.F, A.6.0, E.18, C.30, C.30.ASV, C.30.AD, and C.30.TFS-REL: these words are related but do not name one root kind.Adapt as a positive recovery map: preserve interface and function language as recognition cues, then recover module-interface, signature, functional port, transformation-flow, architecture-of, structural-view, architecture-description, API publication, protocol, or plain source-label use by current claim.