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

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 07:42:37 UTC · snapshot created 2026-10-03 07:43:27 UTC · last check 2026-10-03 07:50:10 UTC

C.30.AD:11 - Relations

  • Use C.2.1 to identify every architecture-description episteme.
  • Use C.30 for obtaining architecture relations, selected structures, and bounded architecture claims.
  • Use C.30.P when architecture or structure wording remains overloaded; use C.30.AD directly when the architecture-description use is already clear.
  • Use C.30.ASV to test architecture structural-view adequacy; only E.17.0 conformance admits the same episteme as U.View.
  • Use C.33 to account for captured and lost structure when a description, generated relation graph, ADR-like record, or view set carries only part of the needed architecture content.
  • Use C.34 to test preservation or correspondence when comparing a description with another view, source model, generated output, candidate, or realized structure.
  • Use C.29 for a mathematical-lens or coarse-graining result, C.30.STRAT for level-word admission, and A.22 or C.30 for the separately supported subject structure or architecture relation. Description-side grouping establishes none of those subject claims by itself.
  • Use A.6.3.NAR for a reader-facing narrative made from a description, view set, or decision route. C.30.AD tests description adequacy; A.6.3.NAR handles structure-to-sequence, source carry-through, lost structure, reader use, and return conditions.
  • Use C.30.TFS-REL, C.30.LCA, and C.30.ILC for their named architecture-relation subcases.
  • Use C.32.P2S for a connected architecturing flow when the description carries only part of the selected structure, decision handoff, method expectation, source continuity, return condition, or feedback from actual structure.
  • Use A.7, E.17.0, E.17.1, E.17.2, E.17, and E.24.PUB for generic EntityOfConcern, view, viewpoint, representation, publication occurrence, form, carrier, and MVPK machinery.
  • C.2.P normalizes source-expression, source-to-use, publication-form, and publication-currentness relation-set overreads.
  • Use E.11.PUR for recommended FPF pattern use after reading a description; C.30.AD records only the description-use boundary.
  • Use A.15.5 for work-entry readiness and full-kit condition; use the A.15 family for Work and the direct governor for any needed project-use relation. C.30.AD records only descriptions and their view conformance, set use, correspondence, source paths and returns, freshness, representation, publication use, and specification use.
  • E.10.MOVE restores move-like wording when source prose about an architecture description does not mean a C.30 architecture move or a C.30.AD remaining architecture candidate use.