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 06:15:20 UTC

A.15.PROD:4.8 - Separate recognition from assurance

Recognition branch for ordinary work. Use the three questions in section 1, the branch outcomes in section 4.1, and the ordinary claim rule in section 4.7. Stop with one readable answer or exact blocker; open only the specific semantic replay needed for a negative claim, an earliest-boundary judgement, or an A.6.RCD:4.2 substrate pin.

Assurance branch for authors and high-consequence use. Replay the exact basis in six visible groups:

  • Work and Method. Check exact work identity and every relied-on work-part relation, the actual enactsMethod relation, method applicability, and the intended production effect.
  • Actual change and entity inception. Check every work-to-change and change-to-identity predicate and retain the explicit non-inference from work or method composition to transformation composition.
  • State satisfaction and Work closure. Check every criterion-applicability fact and boundary-state satisfaction fact. Keep the state-satisfaction claim separate from the closure predicate or local claim that closes the Work.
  • Claim epistemes and their current basis. Check the exact identity-specification and completion-criterion epistemes, the named applicability predicate or filled local claim for each episteme at its claimed boundary, any separately current C.2.1 EpistemeEditionRelation, C.2.1 identity, and the evidence-use relations actually relied on.
  • Positive and discriminating cases. Replay both, so removal of one deciding fact blocks only the claim that consumes it.
  • Pinned author substrate. When A.6.RCD:4.2 requires a pin, DPF and FPF authors MUST record the selected substrate and edition and expose direct base predicates, applicability, hidden participants, polarity law, boundary domain and ordering, witness policy, and every earliest-boundary rule used by the claim.

Assurance may warrant reliance on the claim. Work, change, entity inception, and completion remain established by their branch predicates and obtaining facts.

Assurance scope by use. Replay only what the actual reliance consumes. A model or declaration checks exact claim content, one truthful EntityOfConcern, reference scheme, participants, predicates, polarity, and boundary indexing. A conformance use checks that the selected branch reaches one grounded answer or blocker and stops. Pattern review additionally checks the worked and discriminating cases, direct-owner boundaries, checklist, and no-mint disposition. Each assurance use assesses the stated claim; it neither widens that claim nor replaces the branch predicates and facts.