Skip to content

Implement repeatable control transitions and evidenced cancellation #1364

Description

@Brad-Edwards

Execute reusable mixed-control policies while distinguishing an accepted control change from the outcome of cancelling work already in progress.

Acceptance criteria

  • Instantiate transitions against the current participant/episode state, validate controller authority and occurrence coordinates, and preserve ordered replay and concurrency rejection.
  • Permit repeated control cycles within one episode. Reject stale proposals and invalid validity coordinates without weakening occurrence checks.
  • Integrate cancellation with supervised execution and backend acknowledgements. PREVENTED, PARTIAL, and TOO_LATE outcomes require the corresponding evidence; target kind alone is insufficient.
  • Verify repeated cycles, concurrent proposals, restart, cancellation before admission, and races with executing work. Keep control-state changes and operation outcomes separately inspectable.

Prerequisites: #1363, #1362.

References: Diagnosis, Diagnosis.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    area:runtimeRuntime and control-plane codeenhancementNew feature or request

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions