GitLab

Ultimately I think we should separate the state management from the planning_configuration so that sending a configuration is not an implicit command to start the autonomous control. In the short term we probably don't want to give ORI a new thing to do. We already have an active switch on each platform in the squads.

Specifications allowed states:

ALLOWED_STATES = [
    "draft",
    "in_review",
    "approved",
    "rejected",
    "preparing",
    "ready",
    "start",
    "pause",
    "stop",
    "completed",
]

Options

1. the planning_configuration as an implicit start but then use a new state message to handle pause/stop
2. add a state property to planning_configuration and resend the config each time the state changes.

The advantage of 2 is that it doesn't rely on state in the adapters to know what they're starting/stopping.

• Add state to root planning_configuration as an enum start,stop,pause to match specification states?