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 02:22:15 UTC · snapshot created 2026-10-03 03:38:22 UTC · last check 2026-10-03 04:50:20 UTC

A.2.2:13 - Relations

PatternRelation
A.1Supplies holon and system grounding.
A.2Use for exact local system-role kinds and C.3.2 classification judgments; neither carries capability by label.
A.2.1Use for directly declared species under U.SystemRoleAssignment; an assignment’s holder System may separately have capability.
A.2.5Use for SystemRoleAssignmentStateRelation and Work-admitting state conditions; assignment state is not capability.
A.2.7Use for SystemRoleKindRelationStructure; admission substitution or incompatibility among system-role kinds does not create capability.
A.3.1Governs U.Method; method may require capability thresholds.
A.3.2Governs membership of one already identified claim-bearing episteme in U.MethodDescription; algorithm, procedure, or possession wording is only a cue until the exact admitted Method EntityOfConcern and substantive way-of-doing claim are recovered. An admitted method description may separately state required capability.
A.3.3Governs U.Dynamics, the state-space and transition-law episteme; dynamics may explain or predict capability but is not the qualified holder ability.
A.15, A.15.1, A.15.2Govern method, plan, and performed work alignment; capability is one input to work admission, not work itself.
A.6.5Supplies SlotSpec discipline for capability relation fields and capability-use relations.
A.6.FRepairs function and functionality wording that may hide capability, method, work, math function, or functional-architecture claims.
A.6.RSIRUse it to recover relation, signature, interface, system-role, participation, declaration-position, and slot wording before capability repair when the source sentence is mixed; use E.10.ROLE to select the branch for bare role.
C.27.TA, C.27Use C.27.TA when a positive temporal aspect of capability—currentness, window, rhythm, or drift—is itself relied on; use C.27 for temporal-claim adequacy.
C.2.1, A.10, B.3, C.28, F.10, E.17Govern episteme, evidence, assurance, counterfactual, status, and publication-use relations that may justify or qualify a statement or reliance use about a capability claim.
C.16.P, A.19Govern characteristic, scale, and characteristic-space recovery when capability measures depend on declared measured aspects.
C.25Governs composite quality families and Q-Bundles that may supply slots for capability-fit checks.
C.30, C.32.HCS, C.32.ACS, C.32.ACEGovern architecture-characteristic material, project criteria rows, and eval readings that may constrain capability use without thereby establishing the holder’s ability.
Promise-content and commitment patternsGovern outward promise and commitment relations; a promise or commitment claim may cite a capability relation, but capability does not become promise or commitment.