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

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 11:55:15 UTC

E.10:0.2c.20 - FPF-side and project-side epistemes and publications

Semioarchitecture often talks about two different groups of epistemes, publications, records, and uses:

  • FPF-side material: FPF as episteme, FPF patterns, pattern sections, DRRs, FPF publications, FPF views, support documents and documents with named source-basis, evidence-basis, architecture-basis, or review-basis relations or uses, and review targets;
  • project-side material: the engineer-manager’s project epistemes, publications, views, records, carriers, cues, evidence records, A.20 constraint or adjudication decision records, A.21 gate decisions, optional A.21 DecisionLog records, B.3 assurance or engineering-justification records, commitments, one A.15.1 dated Work occurrence admitted under U.Work plus any separate episteme about it, C.11 ChoiceResult values, C.11 decision records, and A.6.A action invitations.

Do not blur them with source, artifact, object, material, target, pattern, or broad semiosis. If both sides are being used, split the sentence to make the relation explicit when a relation claim is being made, the admissible-use boundary when a boundary-use claim is being made, and the project-side FPF kind and reference named by value when that side is being used. Record the corresponding values in relationClaimSlice, admissibleUse, and projectSideFPFRef, respectively, only when the receiving claim needs those named fields. For an unused side, record absence only when a named receiving use must distinguish it from missing information.