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

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 11:52:20 UTC · snapshot created 2026-10-03 11:53:41 UTC · last check 2026-10-03 12:00:09 UTC

A.2.7:10 - SoTA-Echoing

Current or mature lineWhat it contributesConcrete use in A.2.7
gUFO 2026A current foundational-ontology comparator with explicit type and relation reification distinctions.Keep relation obtaining, occurrence individuation, assertion episteme, and representation separate without importing gUFO’s upper taxonomy.
OpenFGA role-modeling guidance, updated 2026Distinguishes static role-like relations, user-defined role forms, and instance-specific assignments in authorization models.Use it as a software stress case for separating kind relations, assignment inputs, and outcomes; do not make authorization the universal ontology.
Cedar policy constructionEvaluates concrete principal, action, resource, scope, and additional conditions.Keep structure as one premise while the checking system, exact assignments, action condition, and outcome remain visible.
Separation-of-duties practice across safety, clinical work, governance, and authorizationUseful independence claims depend on exact holder, Work, overlap, and applicability conditions rather than title intuition.Put those conditions in the symmetric incompatibility predicate and test actual assignments separately.
FPF C.3.1, A.6.REL, A.6.5, and A.22Supply monotonic kind order, relation occurrence identity, declaration-local SlotSpecs, and dependent structure identity.Reuse the existing apparatus instead of creating another role taxonomy or relation-record ontology.

The software sources are stress cases, not the universal subject. Their transferable contribution is the separation of kind definitions, instance assignments, evaluation inputs, and outcomes.