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 14:36:52 UTC · snapshot created 2026-10-03 14:38:14 UTC · last check 2026-10-03 15:20:20 UTC

E.10:9.5 - Conformance checklist (LEX‑CC)

  1. LEX‑CC‑1 (Triggered use, not spelling ban). A listed word opens repair only when its FPF-governed use hides a kind, relation, claim, or action; quoted, ordinary, and already precise uses remain available.
  2. LEX‑CC‑2 (Context wording). After E.10.D1, each action-changing use of context names what supplies the relevant boundary, interpretation, or situation and makes the next action or stop clear.
  3. LEX‑CC‑3 (EntityOfConcern and Description-episteme boundary and specification-use morphology). Usage passes § 8 gates (suffix, prefix, and casing), EntityOfConcern and Description-episteme boundary checks, and specification-use checks.
  4. LEX-CC-4 (Cross-local relation). Recover the exact relation being asserted between local senses. Cite an F.9 Bridge only when its direct predicate obtains between identified cells; any proposed use and reliance remain separate. Shared spelling establishes none of them.
  5. LEX‑CC‑5 (MG-DA). New tokens pass MG-DA tests, including full‑text collision and Reserved‑Names checks.
  6. LEX‑CC‑6 (Service, acceptance, and evidence). Service or access wording establishes neither Work nor acceptance. An acceptance claim names the selected criterion episteme, any evaluation or acceptance Work that applied it, the returned value or result episteme, and the acceptance predicate with its participants under the applicable acceptance pattern; delivery Work, evidence, or a positive display proves none by itself. Evidence use is a relation over an Episteme, target claim or use, scope, polarity, time, and provenance under the evidence pattern.
  7. LEX‑CC‑7 (USM compatibility). For each LexicalAct, USM.Scope ∈ AllowedScopes(LEX.TokenClass).
  8. LEX-CC-8 (Naming discipline). If overload cleanup yields one local replacement phrase, the text records the repaired phrase and applicable local repair pattern. If cleanup yields one durable reusable name, the text first records the applicable F.8 decision for the already identified value, then completes an F.18 NameCard; public, Core-facing, durable, or cross-local publication also supplies the F.17 term row. Intuition-first labels, partial NameCards, and naming acts that substitute for value or kind admission are non-conformant.