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

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 08:25:59 UTC · snapshot created 2026-10-03 08:26:43 UTC · last check 2026-10-03 09:45:10 UTC

E.10:9.4 - Coordination map (how LEX plugs into the rest of FPF)

  • With E.10.D1 — Recovering What “Context” Means in Use. E10-CTX-1: When context changes the statement or next action, recover what supplies the boundary—for example, a value, relation, scope, scheme, situation, or use defined by the relevant pattern. E10-CTX-2: For source-local meaning, state the exact source, expression, effective scheme, and local sense. Create F.17 cells when stable addresses are needed; use F.9 only for an obtaining direct Bridge between two exact cells, and keep every proposed use and reliance claim separate.

  • With E.10.D2 (EntityOfConcern and Description-episteme boundary and specification use and refinement discipline). Speak in the right EntityOfConcern and Description-episteme boundary and specification use. E10-EOC-DESC-SPEC-1..3 apply: the EntityOfConcern is named directly; Description suffixes name Description-episteme use; Spec suffixes name specification use on a Description episteme; a work assertion or description is a separate U.Episteme about one Work individual and is not the occurrence; a state assertion is a separately governed claim about a state and is not that state; an evaluation-result episteme is neither the evaluated object nor an occurrence. Upgrade a Description episteme to specification use only when checkable acceptance or another specification-granting gate named by value exists.

  • With E.10.ROLE, A.2, A.2.1, and A.15 (system-role-kind, assignment, Method, and Work alignment). Bare role has no default Tech reading. A local system-role kind classifies independently admitted systems; classification, assignment, and Work remain separate. U.Method is a way of doing; U.MethodDescription is a claim-bearing episteme about one admitted method that passes A.3.2. A performed occurrence is dated U.Work: A.15.1 admits it first from its actual performer basis, Method, time, and containing System; F.6 follows only for precise assignment-bound attribution. A compact attribution account keeps the Work basis and all performers named or recoverable and may omit only an assignment identifier unused by the receiving claim after attribution is established. Assertions, descriptions, logs, and records about the occurrence are separate epistemes.

  • With F‑cluster (Unification) and UTS (F.17). Recover each source-local cell under its effective scheme. A comparison row may cite direct Bridges, losses, contrasts, and separately warranted use claims; the row creates none of them. UTS is the human-readable term publication.

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) (see § 7.5).