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

A.19.SPR:4.2 - Where the repaired claim belongs

What the sentence meansUse this pattern or record
position in a declared CharacteristicSpaceA.19, with A.17, A.18, C.16, and C.16.P when construction is hidden
reusable transition law, trajectory, or dynamics modelA.3.3
exact system-role assignment with no state condition claimedA.2.1; do not treat assignment as readiness
by-value assignment-state condition, obtaining assignment-state relation, or assertion episteme about eitherA.2.5, keeping SystemRoleAssignmentStatePredicate, SystemRoleAssignmentStateRelation, and SystemRoleAssignmentStateAssertion distinct
evidence, currentness, reliance, or evaluation concerning an assignment-state assertionA.2.4, A.10, or the direct evaluation pattern; the assertion episteme does not become its subject
work-entry use of an assignment-state claimA.15.5 or the direct receiving pattern; A.2.5 supplies only the exact assignment-state input
language-state position for episteme or publication wordingC.2.2a and A.16.* after C.2.P when source-publication recovery is needed
source use, source currentness, source publication, or source-use dispositionC.2.P, E.17, E.9.DA, or source-use field named by value
evidence path state, evidence relation, or reliance dispositionUse A.10 to recover the exact source, independently established support relations, currentness and bounded use; use the direct defining pattern for the particular support relation or reliance decision.
assurance result, assurance claim, assurance input, or engineering-justification useB.3
constraint or local CVA.20 or the direct constraint pattern
ambiguous readiness or ready wordingE.10.MOVE until the governed value is recovered
work-entry readinessA.15.5
distinct gate decisionA.21 only when an OperationalGate(profile) consumes declared checks and publishes that decision
release or permission claimthe direct release or permission pattern; a readiness value establishes neither
publication use, publication face, form, or unit value, source-finding useE.17, E.17.0, E.17.AUD, or publication pattern governing the claim
Description episteme admitted for specification use or specification refinementA.7, plus the specification-granting neighbouring pattern named by value: A.6.2, C.2.3, A.21, C.16, E.17, E.10, or another named pattern
temporal claim status or temporal-use classificationC.27, retaining dynClaimPosture only as a declared C.27 field
mathematical-lens use admissibilityC.29, retaining LensUseBoundaryValue only as a declared C.29 field
DRR decision-adequacy result or source-use classificationE.9.DA
pattern-quality result or pattern-quality review statusE.21, with E.19 only as review or admission profile
administrative, review, dispatch, release or admission, or source-control statethe project-side administrative, review, dispatch, release or admission, or source-control record; not pattern prose unless the pattern’s own EntityOfConcern is that record