A.16:5 - Worked moves and recoveries

A.16:5.1 - Incident-control line

An operator alert about a production disturbance may follow notice -> stabilize -> route -> operationalize, then reopen when counter-evidence arrives. The alert need not become an anomaly or requirement immediately. Each step names the form and next pattern; any dated response Work remains a separate claim.

A.16:5.2 - Inquiry and admissible retreat

An inquiry cue about a model-versus-observation discrepancy may follow notice -> stabilize -> route -> projection -> formalize. If the framing over-commits while anchors remain unstable, continue with reopen -> sketchBackoff -> respecify, retaining the witnesses and withdrawing only the unsupported closure.

A.16:5.3 - Three identity cases in one line

A raw vibration trace and operator contrast may first be preserved as PumpVibrationCuePack-1; no fictional source episteme is required. Publishing the unchanged cue-pack episteme in a review card and a long-form note is a form-only case under E.24.PUB. If later analysis changes its ClaimGraph from “unexpected vibration” to a bounded bearing-fault proposition, C.2.1 identifies a successor episteme; the move note states the changed claim, retained trace, discarded rival, and any exact EpistemeEditionRelation that obtains.

A.16:5.4 - Retired route or branch

A RoutedCueSet may keep evaluative and abductive routes live. If review later shows the evaluative route unsupported, record that route’s retirement while the abductive route remains current. Do not rewrite the history as though only one route ever existed. A route inside one publication becomes a lineage branch only after a separate successor member is identified.

A.16:5.5 - Premature endpoint capture

notice -> gate decision is not admissible merely because the cue sounds urgent. Recover the missing stabilization, route publication, and applicable endpoint test. Reopen an over-committing requirement label and publish the earlier safe form instead of defending the label.

A.16:5.6 - Silent route drift into Work planning

If an evaluative note starts guiding Work planning, publish a new route selection and operationalization note or use A.15.2 to plan the Work. Name an acting system, Method, system-role assignment, or Work only when the claim depends on that distinction; none is contained in the earlier cue.

A.16:5.7 - Form, pattern, and face stay distinct

“The move publishes a Tech face” and “the move enters A.6.P” omit the actual form. Name the typed publication form first, the object or claim that the cited pattern defines, constrains, or tests second, and the MVPK face only when rendering or review depends on it.

A.16:5.8 - Short compound histories

notice -> stabilize -> route -> projection into U.AbductivePrompt and endpoint admission -> reopen -> sketchBackoff -> route can be summarized only when each intermediate move, changed rule, loss, and independent status claim remains reconstructible. Retreat preserves the earlier endpoint result in the history. When comparing histories, do not treat route -> projection and an unsupported cue -> requirement leap as one “formalization speed”; compare the moves, forms, applicable rules, and independent status claims.