A.16:4.1 - Canonical move table
This is the one canonical move table. Later examples apply it; they do not define another move family.
| Move | Use it when | Publication result | Keep explicit |
|---|---|---|---|
notice | a low- or unstable-articulation cue is worth preserving | preservation-worthiness becomes explicit; a first typed preservation may begin | why the cue is worth preserving and which witnesses remain |
stabilize | the noticed cue needs a steadier local shape before route or endpoint choice | PreArticulationCuePack or an equivalent early form may become admissible | cue nucleus, anchors, contrasts, witnesses, and preservation rationale |
route | a stabilized cue has several plausible downstream directions or one route must be selected | RoutedCueSet or another route-bearing publication makes plurality and any selection explicit | live routes, selected route if any, selection reason, and reopen condition |
projection | one aspect of an explicit route must be foregrounded without claiming endpoint admission | a typed route-bounded partial publication on an existing MVPK face | what is foregrounded, what is omitted or lost, and how reopen remains possible |
formalize | articulation or closure can increase under a named later rule | a more explicit symbolic, slot, or normal-form publication | the rule used, changed facets, and any new evidence-generating Work boundary |
operationalize | selected content is ready to face a method, Work, gate, or other operational question | the episteme or project record is docked to the pattern that defines or tests that use | the exact downstream contribution, its guard, and any world-facing Work boundary |
reopen | the current route, frame, or closure no longer holds cleanly | a publication in the same broad family expresses the reduced closure claim | reopened rivals, retained witnesses, and which prior endpoint-use or current-use claim no longer holds |
sketchBackoff | an endpoint-bound or operational form over-commits the available grounds | an exploratory cue-bearing form becomes admissible again | retained anchors and witnesses, withdrawn closure, and the next safe question |
respecify | the broad family remains plausible but its framing scaffold, facet reading, or route specification is wrong | a revised framing or route specification replaces the earlier one | replaced commitments, invariants that stay fixed, and any episteme-identity change |
retire | a cue, route-bearing publication, episteme, or branch is no longer current for the named use because its grounds failed, a successor took over, or a current-use decision ended | retirement or withdrawal is explicit | reason, exact retired object, successor or no-successor note, and preserved history |
The table names moves, not the resulting objects. PreArticulationCuePack, RoutedCueSet, and U.AbductivePrompt are publication forms defined elsewhere. A claim-bearing episteme remains U.Episteme; E.24.PUB separately defines a bounded publication occurrence.
projection means route-bounded partialization. Its result must be a typed publication form; an MVPK face alone or an untyped placeholder is not enough. respecify changes framing, route specification, or a facet-profile reading. Precision repair remains with A.6.P or C.16.Q; recovery of an ambiguous action-oriented claim or question remains with A.6.A.
Do not use A.16 to decide measurement admissibility, Bridge substitution, endpoint ontology, or another subject claim. Name the applicable pattern and test directly; A.16 coordinates only the publication move that makes that question current.