fpf.tools
Library / First Principles Framework (FPF) - Core Conceptual Specification
Jump to passage
In this reading
Source · lines 108033–108044

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:40:10 UTC

F.9:17.2 - Regression checks

  • RSCR-F9-E01 (Same Bridge, changed use). Reversing direction, changing the use rule, or changing tolerance reidentifies the C.2.1 claim, not the Bridge.
  • RSCR-F9-E02 (Same claim, changed evidence). Stale or stronger evidence changes the descriptive A.10 evidence-provenance path or local disposition, or the B.3 branch, without reidentifying the fixed claim.
  • RSCR-F9-E03 (Required but missing assurance claim). If a direct domain rule requires an assurance claim and none is current, return RelianceDisposition=assurance-needed or block the use. Do not manufacture a positive claim or a generic safety-case record.
  • RSCR-F9-E04 (Profile change). A changed relation condition or endpoint reading identifies another profile and occurrence candidate.
  • RSCR-F9-E05 (Packaging change). A changed card, registry entry, publication, form, or carrier leaves the Bridge and fixed bounded-use claim unchanged unless their own discriminators changed.
  • RSCR-F9-E06 (Positive proposal versus occurrence). An affirmative claim with passing reliance proves no comparison Work, assertion, publication, direct relation, or operation application.
  • RSCR-F9-E07 (Polarity versus reliance). Negative claim polarity and a non-passing reliance disposition remain different facts.
  • RSCR-F9-E08 (Reliance versus authorization). A.10 pass or B.3 supported-for-use does not imply permission.
  • RSCR-F9-E09 (No inverse or composition). Neither an asymmetric inverse nor a direct A-to-C Bridge follows without its own profile and obtaining test.