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 08:25:59 UTC · snapshot created 2026-10-03 08:26:43 UTC · last check 2026-10-03 09:25:05 UTC

F.0.2:4.2 - Source-basis branches

Source situationAuthoring moveBoundary
An admitted maintained synthesis already integrates a fieldRecover every occurrence that can change the receiving question. Follow its cited sources where a load-bearing distinction or limit depends on them, and compare current alternatives that could change the answer.The synthesis is a valuable conceptual map, not independent confirmation of its own integrated claims.
Several independent sources answer the questionGive each source an explicit role: proposed contribution, rival explanation, counterexample, boundary, evidence limit, or current alternative.A reading list or source count does not establish coverage or relevance.
An identified G.2 pack already existsReuse its identified source claims, editions, alignment records, and provenance when they answer the bounded question.Pack conformance, a fusion record, or a coverage measure does not establish the receiving-framework claim.
An earlier DPF supplies a lessonClassify the lesson as direct FPF reuse, a bounded FPF improvement proposal, or a domain/local claim retained in the receiving DPF.Precedent does not create ecosystem law or prescribe package shape.
A derived lookup proposes FPF or DPF contributionsReturn each result to the authoritative pattern body and edition. Report a partial result when a source is unavailable, stale, or incompletely indexed, and widen the search when a known contribution is absent.A lookup result aids discovery; non-return is not evidence that a contribution is absent.