| How should an admitted continuing case choose and evidence its next permissible Work when facts or exceptions change? | The selected line is situation-responsive steering inside the applicable domain Method, with separate permission, chooser, performer, Work, evidence, state update, stop, and return. The serious default is a workflow, case-plan, ticket, or automated loop transition used as the progression result. | The default confuses representation with subject state and choice with performance. Adapt: OPS.6:4.1–OPS.6:4.7 confirm permission, refresh action-changing facts, choose the least elaborate branch, specify performance, and admit state change only from evidence. Reject: one universal case lifecycle, record-to-Method inference, or agent output as progress. | Current FPF A.15.7 supplies the general next-action steering Method and C.11 bounded choice. CMMN contributes discretionary case planning and state representation; DCR contributes condition, response, inclusion, exclusion, marking, execution, and acceptance distinctions. DEMO contributes bounded commitment, coordination, and responsibility distinctions. DORA, harness, and loop sources contribute short-horizon evidence, bounded concurrency, traceable episodes, stops, integration burden, and human continuation. None supplies the case’s domain state, authority, Work, progression evidence, release, or universal Operations Method. | Reopen if a stronger continuation account preserves the same permission, domain-Method, performer, performance, evidence, state, blocker, and return boundaries with less burden, or if a source changes the permissible-action or evidence contract. |