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 11:52:20 UTC · snapshot created 2026-10-03 11:53:41 UTC · last check 2026-10-03 12:40:18 UTC

A.16.2:13 - Worked Retreat Trajectories

A.16.2:13.1 - Reopen within the same family

A routed evaluative note may remain within the same family but move from high closure to lower closure when a rival frame becomes a live alternative again. This is reopen, not sketchBackoff.

A.16.2:13.2 - Sketch-backoff to cue pack

An account recovered through A.6.A may assert more than its grounds support. For example, a supposed pulling opportunity may have only a detector cue and no established physical predicate. First select the account-identity case under A.16:4.3 and C.2.1, then express the publication-form change:

source form: physical-opportunity account; move: sketchBackoff; target form: PreArticulationCuePack

Withdraw the unsupported claim and any route selection or endpoint-use claim that depended on it. This changes the account; a change to the physical opportunity or an actual authority relation requires that subject’s own predicate.

A.16.2:13.3 - Respecify without repair-pattern drift

A route-bearing publication may keep the same broad family but replace one framing scaffold or route specification with another. That is respecify, not silent editing, and not slot-explicit epistemic precision repair.

A.16.2:13.4 - Retire an obsolete branch

A route-bearing branch may later become obsolete because another branch now carries the governing pattern and witness support for the current use. The admissible continuation is explicit retire, not silent disappearance.