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 05:29:54 UTC · snapshot created 2026-10-03 05:30:57 UTC · last check 2026-10-03 06:45:03 UTC

A.2.4:7 - Conformance Checklist

CheckPass condition
CC-A2.4-1 First-use objectOne exact episteme and one target claim or governed status assertion are named.
CC-A2.4-2 Admitted jobThe statement is only an evidence-use or status-use classification; no U.EvidenceRole, episteme-as-system-role-kind classification, assignment holder, or generic result kind is created.
CC-A2.4-3 Scope and interpretationEffective source scheme when material, grounding holon, claim or status scope, polarity or value, and relevance or status window are explicit when they change the use.
CC-A2.4-4 WorkFor any source-producing, measurement, proof-checking, evaluation, transformation, or receiving Work, A.13 identifies the actual performer and A.15.1 independently admits the dated occurrence. Add F.6 only when the result must also identify the assignment under which that Work was performed. The Method and direct-relation or A.6.1 bindings remain separate.
CC-A2.4-5 Local resultThe domain-local result points to its exact formal, measurement, causal, diagnostic, conformance, comparison, selection, acceptance, gate, permission, commitment, system-role-kind, assignment, or decision governor.
CC-A2.4-6 Result epistemeThe C.2.1 episteme that states the local result remains distinct from that result, carrier, and work.
CC-A2.4-7 Provenance/currentnessUse A.10 and G.6 for source recovery and provenance; use G.11 for currentness when it affects use.
CC-A2.4-8 Receiving useWhen a particular receiving Work or receiving-use relation is asserted, name that Work and relation. Citation or availability alone does not establish actual use.
CC-A2.4-9 Reliance/assuranceA.10 defines the bounded RelianceDisposition. Use B.3 only when an actual named assurance claim is being made. If a direct domain rule requires one for the intended use, state that claim and its required basis first.
CC-A2.4-10 Publication/displayPublication face, generated explanation, credential view, evidence profile, ledger edge, or dashboard cell does not establish status, result, work, gate, permission, or decision by presence.
CC-A2.4-11 Causal boundaryC.28 is the pattern for causal-support components and results; source wording cannot promote simulation or observational evidence.
CC-A2.4-12 Unsupported overreadState the stronger claim not carried by this first-use classification and its reopen condition only when that warning passes F.19:4’s full independent-ground, plausible-reader, contribution, and smallest-clear-correction test.