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:00:09 UTC

D.3:6 - Conformance Checklist

IDRequirementPurpose
CC-D3-1A reusable result is one C.2.1 episteme with one exact EntityOfConcern, ClaimGraph, and effective ReferenceScheme. Edition, form, carrier, and publication remain separate.Makes the reference used by D.4 reidentifiable.
CC-D3-2At least two sides each connect one ethical claim, affected entity, declared level relation or applicable scope, value-frame edition, consequence, and horizon. Evidence use and uncertainty are added when current.Shows what each claim affects rather than presenting a flat inventory.
CC-D3-3Any ClaimScope on the whole description remains separate from side-specific ClaimScopes and Work extents.Prevents the description’s coverage from replacing the scope of a side.
CC-D3-4The tension names the sides and states why they cannot all be met as stated. Any direct relation claim cites its definition and obtaining occurrence, or the exact A.6.RCD missing-governor result.Prevents a reference field from manufacturing a fact in the situation.
CC-D3-5Classification assertion, Method, Work, relation definition, relation occurrence, evidence episteme, evidence use, publication, form, and carrier remain separately typed when used.Prevents the conflict description from absorbing neighboring objects.
CC-D3-6The first useful result is readable without the optional enriched branches, and every added branch changes the conflict or its next use.Keeps D.3 affordable in ordinary project work.
CC-D3-7The next-use statement names D.4, D.5, C.28, C.30.ILC, evidence, assurance, or another receiving pattern by value.Keeps mapping separate from mediation, decision, proof, and assurance.