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 11:52:20 UTC · snapshot created 2026-10-03 11:53:41 UTC · last check 2026-10-03 13:45:10 UTC

E.11.PUR:7 - Conformance Checklist

IDCheckPassing condition
PUR-1Candidate basisEvery evaluated candidate has an inspected Solution and a recoverable expected first result or honest blocker; an exact PUA expectation is required only for an addressable recommendation or result-based precedence.
PUR-2Five aspectsOrdinary judgement considers all five fit aspects in one rationale; reliance-bearing applicability has exactly one finding for each aspect.
PUR-3AggregateA recommendation follows the aggregate applicability judgement under 4.1. If an addressable applicability finding exists, its result agrees and carries a missing-basis boundary when needed.
PUR-4RecommendationThe recommended candidate is applicable and its expected receiving value warrants its full burden compared with the serious continuations, including continuing without a new use. If none warrants recommendation, no candidate is selected and existing obligations remain in force. An addressable ordinaryCompact recommendation has no applicability-finding ref; relianceBearing has one current applicability finding with five fit findings.
PUR-5CoordinationAll members concern the same bounded coordination question and remain distinct candidate uses.
PUR-6Ordering modeUnordered has no pairwise relations. Partial and total order contain only justified pairwise precedence, whose transitive closure is irreflexive; total order also compares every pair of distinct members. A cycle or unresolved required pair blocks that ordering claim.
PUR-7Precedence and readinessEach directed relation satisfies its §4.4 branch predicate. prerequisiteResult cites the exact required content, selected supplier-use basis and expectation; actual closure belongs to a separate readiness claim and may reuse an adequate earlier result. Description or witness changes alone do not change dependency identity.
PUR-8BoundaryRecommendation or coordination asserts no plan, work, gate, decision, authorization, actual Problem, Transformation, or subject result.
PUR-9Problem actualityA Problem-frame fit or ProblemCard is not an actual Problem; a relied-on actual Problem resolves to one C.22.PFR occurrence, while any supporting episteme and the adverse episode keep separate identities.
PUR-10Plain moveNext move names only a recommendation or conditional continuation, without asserting a Move identity, performed Work, or actual Transformation.
PUR-11Earlier-result reuseAn earlier result is reused only after the pattern that defines or tests it establishes that its EntityOfConcern and edition, question and use, relied source and dependency conditions, and qualification or currentness boundary still answer the present concern. Any later A.10 reliance and G.11 currentness assertion remain separate.