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

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.15:12 - Relations

  • A.15.9 coordinates one receiving decision or piece of Work with one bounded result governed by another practice. It first tests an already-available result, requests only a remaining gap, and preserves supplier Method and authority separately from receiver decision authority; it creates no new alignment object or result kind.

  • A.15.7 supplies the situation-responsive steering Method after current Work, its domain Method, and relevant facts are known; it returns the selected action, intended performer, and stop or feedback condition without making the answer into Work.

  • Architecture-work boundary: C.32.P2S and C.32.PAD may cite MethodDescriptions, pattern-use references, exact system-role assignments, separate responsibility or authority relations, readiness exits, and expected structure effects. C.32.ADR may publish those references. A.15 supplies only Method, description, plan, readiness, performed Work, and attribution distinctions.

  • Uses: A.7 for strict distinction among system-role kind, assignment, Method, MethodDescription, plan, Work, and records.

  • Builds on: A.2 and C.3 for exact local system-role kinds and classification; A.2.1 for direct U.SystemRoleAssignment species; A.13 for the precise local agency core and conditionally consumed profile; A.2.2 for capability; A.2.5 for SystemRoleAssignmentStateRelation; A.2.7 for relations among system-role kinds; A.6.5 for relation-slot discipline; A.3.1/A.3.2/A.3.3/A.3.4 for Method, MethodDescription, Dynamics, and Transformation, respectively; A.15.1 for independent Work admission; A.15.2 for WorkPlan; A.15.3 for declaration-local planned-filling content inside that WorkPlan; A.15.5 for readiness; and F.6 for the later performedUnderAssignment relation and holder-equality projection only when precise assignment-bound attribution is consumed.

  • Coordinates with: A.15.4 for work-relevant reliance repair; E.10, E.10.ARCH, and E.10.ROLE for wording recovery; A.6 for boundary and policy claims; A.10 for evidence and provenance; B.3 for assurance; A.20 and A.21 for constraints and gates; C.28 for causal-use admissibility; C.29 for mathematical-lens use; E.18.1 for P2W carry-through; C.32.P2S for architecturing-flow references; and E.17.EFP for generated-explanation faithfulness.

  • Used in: claims that must keep systems, local system-role kinds, assignments, Methods, WorkPlans, Work occurrences, result records, and reliance repairs distinct. A.15 is not a generic process ontology, workflow engine, evidence graph, gate pattern, or publication pattern.