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 12:55:10 UTC

E.17.EFP:4.4 - Working bounded-use matrix

ClassClaim/source relationAugmentation boundaryUsually bounded facesUsually bounded publication-form useUsually forbidden uses
SourcePinnedExplanationsufficient expression of the exact source edition for the declared use; whole-source coverage is not claimedno claim-level augmentationPlainView, TechCardsource inspection, navigation, or bounded restatementan assurance, gate, evidence, or work claim not separately established
SourceLinkedExplanationReconstructionsame source ClaimGraph with a connective recovered by a stated derivation from source claims, or by an exact relation occurrence already reported there and independently shown to obtainno new relation by class labelPlainView, TechCardbounded explanation while the exact derivation or source-reported relation remains recoverableuse for which the source, scheme, derivation, source relation claim, or obtaining basis is unavailable
DidacticRetellingsufficient source form, or form of a separately identified target connected under A.6.3 or another applicable patternpedagogy does not hide target identity or relationPlainViewdidactic or onboarding usepolicy, assurance, gate, or source-replacement use
SpeculativeRetellingform of a separately constituted B.5.2 hypothesis epistemecausal or counterfactual claim belongs to the hypothesis ClaimGraphPlainViewclearly marked exploratory useevidence, assurance, gate, release, or policy use

This matrix assigns no evidence relation. An ordinary EFP result needs no A.10 path. Exact evidence, trace, pin, or provenance details open only when a named claim, dispute, derivative transformation, or receiving reliance consumes them and its applicable pattern or project record requires them.

ExplanationFaithfulnessProfile ordinarily stays on publication face/form. Any appearance on interop publication form remains source-pinned and structure-preserving, and does not smuggle explanation-specific semantics into interop publication. Didactic or speculative restrictions are use-profile restrictions over existing faces, not new face kinds.

Source-pinned explanation on AssuranceLane-facing publication is exceptional rather than ordinary. Unless the exact face or source policy permits that use with visible evidence carriers, source pins, and no added semantics, reviewers treat AssuranceLane-facing explanation rendering as blocked.

DidacticRetelling may carry analogy, scaffolding, or reader orientation without asserting a domain fact. Every domain claim it does express belongs either to the exact source ClaimGraph or to an identified target episteme with an obtaining source-to-target relation. Marking prose non-canonical or trace-free does not erase claim content, create its episteme, or establish that relation. When such analogy or scaffolding sits beside technical content, box or otherwise visibly separate it so readers do not merge it into the technical source; that cue limits likely use but does not establish episteme identity or a source relation.

The compact ordinary result needs only a source locator sufficient to reopen the exact source or target decision. Publish exact claim IDs, pins, trace paths, provenance details, or an A.10 evidence relation only when a named claim, dispute, derivative transformation, or receiving reliance consumes them. A reopenable locator is not automatically an evidence path.

When a reader-fit difference changes the bounded or blocked use, state only the relevant audience, interaction, question, use, or overread distinction. Do not publish or inherit all five reader-model fields for ordinary reader help.