A.16.2:16 - Retreat Package Discipline

A retreat is trustworthy only when it makes visible what changed, what survived, and which exact route, endpoint, publication, current-use, or independently established relation claim no longer holds.

A.16.2:16.1 - Minimal retreat note

A retreat note should make explicit:

• the source form and the separate route selection, endpoint-use disposition, publication availability, current-use status, and actual relation claims that matter,
• the triggering mismatch or counter-evidence,
• the move kind,
• the target form or target family,
• the retained witnesses,
• the withdrawn assumptions or route claims,
• the required downstream updates for any affected governing pattern,
• and the successor / no-successor status if a branch is retired.

A.16.2:16.2 - Retreat is not erasure

Retreat preserves continuity: a high-closure formulation or one that had passed a named endpoint test for a stronger use was adopted, then shown to over-commit in stated respects, and therefore backed off or withdrawn admissibly.

A.16.2:16.3 - Partial retreat

Some retreats withdraw only one route claim or scope assumption, or remove one framing scaffold or operational hook from the current use. In those cases name the surviving core rather than resetting everything.