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

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 08:25:59 UTC · snapshot created 2026-10-03 08:26:43 UTC · last check 2026-10-03 08:35:10 UTC

A.6.P:12 - Relations

  • The direct relation pattern defines or constrains obtaining, predicate satisfaction, and the occurrence-identity rule. After A.6.P recovers that relation, A.6.REL governs demand-driven explicit individuation, application of that identity rule, and occurrence-as-participant use.
  • A.6.0 governs U.Signature and compatible RelationSignature declarations; A.6.5 governs declaration-local SlotSpec, SlotKind, participant ValueKind, and receiving-episteme designation mode.
  • Use A.6.RSIR to distinguish direct participation, declaration, operation, assertion or description, and representation when interface, role, slot, field, parameter, or endpoint wording is the entry cue.
  • A.6.B separates L, A, D, and E claims after the direct relation is recovered. When the next task needs a relation between epistemes or an operation that produces a receiving episteme, identify both endpoints independently under C.2.1. Use A.6.3 for its compatible same-EntityOfConcern construction, A.6.2 for its local effect-free arrow, and A.6.4 for an exact different-EntityOfConcern arrow r, its separate C.2.1 bounded-use assertion q about exact r, and the separate three-valued current-case judgement defined there. If the selected pattern lacks an entry or result condition for the case, stop explicitly and name the missing arrow, use-claim, or application condition. Use A.15.1 for actual authoring, materialisation, checking, or publication Work; keep the arrow, assertion, judgement, application, and Work distinct; and assert an edition or successor relation only after its own predicate is satisfied. Ordinary A.6.P repair stops before these objects.
  • A.6.6 provides specialized recovery for basedness. Service/access wording stays in A.6.P:4.11a until the exact predicate is recovered; cite the pattern that states it when the reference must travel. A.1.SCR applies only after one exact bearer or arrangement claim has been recovered and the decision depends on systemhood; A.1.STM applies only after recovery when the separate question is contribution to use of a named project system-of-interest. Cross-context and whole-part wording may use A.6.9 or A.6.H only when that pattern’s entry accepts the objects named in 4.11 and its result states the direct predicate and participants or an explicit blocker. If either check fails, keep the 4.11 blocker and name the missing predicate or unmet entry condition. A situation record, Card, or bundle does not replace the direct relation, claim-bearing episteme, or representation.
  • A.6.P.WMR defines the method, work, result, production, delivery, acceptance, transfer, and receiving-use boundary and the four result families listed in 4.11.
  • Use A.6.RCD after the reader can name the participants and the sentence the next task needs, but no current pattern supplies its predicate. Broad wording alone is not a missing-governor result.
  • C.2.1 governs assertions and descriptions. A.6.P identifies one candidate episteme E, one viewpoint episteme P, and the conformance question; E.17.0 tests EpistemeViewpointConformanceRelation(E,P). If the next task also asks whether E is a U.View, E.17.0 handles that recognition separately. Viewpoint selection, evaluation, construction, representation, and publication do not establish conformance; A.10 governs reliance, while E.17 and E.24.PUB govern publication.
  • Use C.3 and C.3.1 only if the next claim must quantify over a locally defined participant set, test membership or substitution, or order kinds. Otherwise do not mint a local kind.
  • Use A.1, A.2, A.2.1, A.3.1, A.3.4, and A.15.1 for the direct criteria for Systems, exact local system-role kinds, separate System-classification judgments, direct U.SystemRoleAssignment species, Methods, actual bounded change, and Work.
  • The exact predicates defined in A.10 constrain evidence relations, and those in B.3 constrain assurance. F.9 directly defines Bridge as a species of U.Relation, its two local-sense participants, its BridgePredicateProfile, the condition under which the predicate is true, and its occurrence-identity and recurrence rule. Use C.2.1 separately for assertions, occurrence descriptions, and Bridge Cards; use A.10 or B.3 for evidence reliance or assurance, E.24.PUB for publication, and the receiving object’s own pattern for any use that actually occurs. Use A.6.RCD only when the needed relation is not supplied by F.9 or another current defining or testing pattern after the participants and needed sentence are explicit. C.30.P defines or constrains architecture wording, C.16.P characteristic wording, G.2 palette/front/archive distinctions, and A.6.F function-like wording. Each cited pattern contributes the named definition or constraint; its identifier is a locator only when that reference must travel.
  • A.16.1 and B.4.1 retain cue material that has not reached a grounded relation-bearing claim; B.5.2.0 carries a stabilized open explanatory question that has no selected relation answer; A.16.2 records reopen, backoff, or respecification when a published relation overstates articulation, closure, or framing. Use A.16.0 only when lineage, branching, loss, or responsibility-transfer history itself must be published.
  • Use F.19 for ordinary precise-plain-language repair and its plausible-reader test. Use E.10 for wording triggers, E.10.ROLE to recover the actual branch of bare role, and E.10.ARCH for the shared recovery architecture. Use F.18 for designation after objects and relations are recovered.