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

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:30:19 UTC

C.32:12 - Relations

  • Builds on: C.30 for the exact described holon, obtaining ArchitectureRelation occurrences, their selected U.Structure participants, and separately identified ArchitectureClaim content; C.30.P, C.30.ASV, A.22, A.6.F, A.6.M, C.32.HCS, C.32.ACS, C.32.ACE, C.25, C.31, C.31.ASAP, C.16, C.16.P, E.22, E.23, C.19.1, C.30.LCA, C.30.TFS-REL, E.18, A.3.4, A.15, and local patterns for recovering source-side architecture referents.
  • Uses: C.30.ILC when a residual starts the candidate work; C.32.MLAO when residual-reducing multilevel framing is being used; C.32.CONWAY when exact influence-source and transformed-side architecture content must be co-synthesized without inferring acting, Work, or transformation facts; C.32.FAIL when a candidate needs repair before explicit comparison, selection, local choice, or decision; C.32.ACE when candidate eval results are needed before later comparison or selection; C.33 when a source, description, view, decision record, eval report, handoff, or realized observation captures only part of selected structure; C.34 when candidate or source structures need preservation adequacy or correspondence adequacy; C.35 to recover the kind and assess the adequacy of a generated or discovered result before candidate palette use; C.29 when mathematical-lens use is being claimed.
  • Patterns for the next questions: A.19.CPM for explicit comparison claims, A.19.SelectorMechanism for set-returning selection claims, G.5 for selected-set result declaration, C.18 and C.19 for archive, front, or pool-treatment policy, C.11 for fixed local choice, C.30.AD for architecture-description work, E.17 for a source-backed publication face and source return, E.24.PUB for the publication occurrence and audience availability, and C.32.PAD for project architecture decisions.
  • P2S docking: C.32.P2S uses C.32 for the candidate-synthesis stages after problem pressure, selected structures, architecture characteristics, and structural uncertainty have been recovered; C.32 continues to define the candidate palette.
  • Routes to: C.32.MWA when one usable practice-architecture answer must be synthesized from several structures that do not line up one-for-one; C.32 retains general candidate-palette construction.
  • Boundary: Use C.32 to construct a candidate architecture palette for one grounded architecture question over selected structures of a described holon. C.35 may support C.32 by recovering a generated or discovered result’s kind and assessing its adequacy for candidate-palette use, but C.35 does not select candidates, publish sets, or decide the project architecture. Evidence, assurance, gate, release, work authorization, Method rules, ethical mediation, and causal claims use their own patterns when those claims are being made.