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

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 17:24:51 UTC · snapshot created 2026-10-03 17:30:20 UTC · last check 2026-10-03 19:00:10 UTC

C.30.AD.BA:2.3 - Keep exchange checking distinct from architecture evaluation

An IFC exchange or another machine-readable model is a representation and publication of one or more epistemes. Its schema relations can preserve valuable source structure. Before using it as architecture-description content:

  1. identify every source episteme used, its representation, and the publication occurrence, form, and carrier;
  2. recover the exact actual subject-relation occurrences and A.22 selected structures represented by the relation data being used;
  3. record the source-to-use path into the exact architecture description or view episteme;
  4. state the admissible architecture use and any lost, inferred, unknown, stale, or unavailable relation content.

An exchange checker can use a computer-interpretable specification to evaluate whether declared information is present and shaped as specified. That evaluation concerns the exchange description or publication. It does not make schema relation data obtain in the built asset, constitute a selected structure, grant U.View membership, establish description truth, or show that the selected architecture is adequate for the asset’s functions, constraints, or architectural characteristics. Apply the architecture, characteristic-evaluation, evidence, and assurance patterns for those claims.