Library / First Principles Framework (FPF) - Core Conceptual Specification
Jump to passage
In this reading

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 10:39:28 UTC · snapshot created 2026-10-03 10:40:04 UTC · last check 2026-10-03 10:55:17 UTC

E.10:0.2c.14 - sign, concept, denotat, and school-semiotic labels

Do not import the school-semiotic triad as architecture ontology. When a source or review text says sign, signifier, signified, concept, denotat, representamen, interpretant, or sign vehicle, apply the composite recovery order before the term appears in FPF-facing prose.

Possible recoveries include:

  • U.Episteme or episteme species named by value;
  • selected EntityOfConcern, grounding, reference-plane relation;
  • U.View, U.EpistemeView;
  • publication form, generic publication face, declared MVPK face, or PublicationUnit;
  • carrier, front-end, or rendering;
  • cue, displayed wording, mark, status display, credential display, provenance mark, signature evidence;
  • evidence record, gate record, work-state record, commitment record, separate assertion or occurrence-description episteme about one exact U.SystemRoleAssignment, or another project-side FPF kind and reference named by value;
  • FPF pattern, pattern section, accepted DRR, FPF publication, or FPF view when the object is on the FPF side.

Use concept only where current FPF already has the relevant concept-set, UTS, local-meaning, or Part F machinery available. Otherwise recover the claim-bearing episteme; the obtaining direct relation and actual participants; the current A.6.5 declaration, participant designation, or C.29 representation and explicit correspondence when one of those is actually present; or the record kind and defining rule named by value.