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 07:15:14 UTC

A.15.PROD:4.2 - Recover the smallest exact base

The practitioner MUST use only objects needed by the selected branch:

Working nameExact object and governorRequired contribution
productIdentitySpecificationone exact C.2.1 predicate-definition episteme whose subject pattern states the identity rule; any continuing-edition relation to another specification episteme is stated separatelystates the identity rule before inception without pretending that a future entity exists
identity-specification applicability basisone named applicability predicate with its actual participants and boundary facts, or one filled local compound claim selected under A.6.RCD disposition 2applies the exact specification episteme to the candidate basis, subject context, and candidate inceptionBoundary; it introduces no universal applicability relation
producedEntityone exact U.Entity, designated only after inceptionis the entity whose identity rule first became true
productionMethodone exact U.Method under A.3.1states the governed way of doing, intended production effect, applicability, and relevant identity or completion criterion meaning
currentWorkone exact Work individual admitted under U.Work by A.15.1designates the world-side dated occurrence. Recover every exact actual performer through A.13, then let A.15.1 independently admit the Work from its history, at least one obtaining enactsMethod relation, extent, and at least one obtaining locally declared containing-system relation. Only when this production claim also consumes precise assignment-bound attribution name the obtaining occurrence of the exact declared U.SystemRoleAssignment species and the separate F.6 relation through the same A.13 assignment. Missing or failed F.6 preserves the Work and lowers only that attribution. Name an additional enactment, binding, resource-use, or affected-referent relation only when the production claim uses that independently obtaining fact; none is a field stored in the occurrence.
productionWorkone exact Work individual admitted under U.Work by A.15.1designates either the same occurrence as currentWork or the exact larger Work occurrence of which currentWork is a declared proper part
actualTransformationone or more independently identified U.Transformation occurrences under A.3.4names what changed without becoming the work or the produced entity
work-to-change basisone named domain predicate with exact Work and transformation participants and obtaining case facts, or one filled local compound claim selected under A.6.RCD disposition 2establishes that selected actual changes are effects of exact work; coincidence is insufficient
completionSubjectthe exact state-bearing entity or continuing referent judged by the completion criterionkeeps the criterion’s subject explicit instead of applying a product-state test to Work
productionCompletionCriterionone exact C.2.1 predicate-definition episteme whose subject pattern states the state-satisfaction rule; any continuing-edition relation to another criterion episteme is stated separatelystates what state of completionSubject counts as satisfying the production requirement at the candidate boundary
production-work closure governorone declared subject predicate or one filled local A.6.RCD claim that connects exact criterion satisfaction for completionSubject to closure of exact productionWork at the boundarystates why the Work is complete; criterion satisfaction alone does not supply this link
local assertionone C.2.1 epistemecarries only the state-satisfaction claim or the production-work-completion claim needed by the selected question

A neighboring object enters only when a named predicate or filled local claim connects it to the selected Work, entity, or claim and omitting that connection would change the named action or decision. Otherwise keep method descriptions, work plans, objectives, commitments, product specifications, evaluation results, and E.24.PUB publication occurrences, forms, and carriers separate. None is constitutive of every production occurrence.