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

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 14:36:52 UTC · snapshot created 2026-10-03 14:38:14 UTC · last check 2026-10-03 15:30:10 UTC

E.10:21 - Closing notes (governance and purity)

  • Notation-agnostic. E.10 is a wording-use governance pattern, not a scanner or template. Apply it in prose, sketches, or formal models.
  • Where checks belong. Convenience checks belong to Tooling; E.10 itself stays notation-agnostic. Conformance code belongs in SCR-LEX or RSCR-LEX as referenced above.
  • Acts and tokens. LEX applies to tokens; USM applies to acts: mint, rename, and use. Conformance: LEX.TokenClass(t)=c ⇒ USM.Scope(usage) ∈ AllowedScopes(c) (§ 7.5).
  • Guards honoured. DevOps Lexical Firewall and Unidirectional Dependency remain intact.
  • Reserved “plane”. Only CHR:ReferencePlane uses the bare word plane. E.10.D2 is the EntityOfConcern and Description-episteme boundary plus specification-use gates, with publication faces, publication forms, PublicationUnits, carriers, and renderings kept separate; all other category talk is expressed as Characteristics in a CharacteristicSpace when scale semantics are declared.

One-line memory: “F.19 reads the claim; E.10 opens only the unresolved lexical branch.”