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

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

C.2.5:17 - Continuing and Withdrawn Authority Handling

C.2.5:17.1 - Authority retention rule

If higher CD carried endpoint expectations, guard claims, or route commitments, a closure drop must say which consequences remain and which are withdrawn. Treat any actual authority-relation change separately under its direct pattern, as required by A.16.2.

C.2.5:17.2 - Admissible retreat record

An admissible retreat through reopen, sketchBackoff, or respecify should retain:

  • the prior closure state;
  • the reason the prior fixation no longer holds;
  • the assumption or route being relaxed;
  • the still-binding remainder, if any.

This prevents false continuity after retreat.

C.2.5:17.3 - Closure versus obligation boundary

High CD may coexist with obligations. When prose treats “closed” as “must now be done”, use A.2.8 to identify the duty bearer, duty, and instituting rule and basis; retain the applicable governingPatternRef or authoritySourceRef for that obligation claim.