Add new Autonomy message type

Closes #95 (closed)

formats/autonomy.py

+"""
+    schemas: Autonomy related data with Autonomy Engine metadata,
+    configurations and default instructions
+"""
+
+autonomy_schema = {
+    "type": "object",
+    "properties": {
+        "message_type": {
+            "type": "string",
+            "description": "Type of message",
+            "example": "autonomy",
+            "enum": ["autonomy"],
+        },
+        "planning_config_ID": {
+            "type": "integer",

examples/mas-dt/autonomy_engine_control.json

+{
+  "header":{
+    "message_ID": "a127003c-0000-11aa-a1eb-b1cdf2342fdd",
+    "timestamp": "2025-02-07T00:00:00Z",
+    "version": "v2.0.0-beta.11",
+    "source": "noc-c2",
+    "destination": "mas-dt",
+    "delivery_type": "publish",
+    "encoded": false
+  },
+  "payload":{
+    "message_type": "autonomy_engine_control",
+    "planning_config_ID": "b127003c-0000-11aa-a1eb-b1cdf2342fdd",
+    "state": "start"
+  }
+}
\ No newline at end of file

formats/autonomy_engine_control.py

+"""
+    schemas: Autonomy Engine control related data with Autonomy 
+    Engine metadata, configurations and default instructions
+"""
+
+autonomy_engine_control_schema = {
+    "type": "object",
+    "properties": {
+        "message_type": {
+            "type": "string",
+            "description": "Type of message",
+            "example": "autonomy_engine_control",
+            "enum": ["autonomy_engine_control"],
+        },
+        "state": {
+            "type": "string",
+            "enum": ["start", "pause", "stop"],
+            "description": "Autonomy engine instruction to start or stop model",
+            "example": "stop",
+        },
+    },
+    "oneOf": [
+        {
+            "properties": {
+                "planning_config_ID": {
+                    "type": "string",
+                    "format": "uuid",
+                    "pattern": "[0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12}",
+                    "description": "Unique identifier (uuid) for this specification version generated",
+                },
+            },
+        },
+        {
+            "properties": {
+                "planning_config_ID": {
+                    "type": "integer",
+                    "description": "Unique identifier (uuid) for this specification version generated",
+                    "example": 2,
+                },
+            },
+        },
+    ],
+    "required": ["message_type", "planning_config_ID"],
+}

formats/payload.py

         "propertyName": "message_type",
         "mapping": {
             "alert": "#/components/schemas/alert",
+            "autonomy_engine_control": "#/components/schemas/autonomy_engine_control",
             "mission_plan": "#/components/schemas/mission_plan",
             "mission_plan_encoded": "#/components/schemas/mission_plan_encoded",
             "observation": "#/components/schemas/observation",
     "oneOf": [
         {"$ref": "#/components/schemas/alert"},
         {"$ref": "#/components/schemas/acknowledgement"},
+        {"$ref": "#/components/schemas/autonomy_engine_control"},
         {"$ref": "#/components/schemas/mission_plan"},
         {"$ref": "#/components/schemas/mission_plan_encoded"},
         {"$ref": "#/components/schemas/observation"},

formats/waypoints.py

 """
-Temporary message definition to handle the MAS-DT dry-run mode 
+Temporary message definition to handle the MAS-DT dry-run mode
 
 In dry-run the SFMC adapter will receive misson_plan messages from ORI
 These messages will be parsed and compiled into a goto file which will
-not be sent on to the glider 
+not be sent on to the glider
 
-To confirm the message flow is working the SFMC will instead publish 
-a waypoints message back to the backbone which C2 can receive and 
-process - adding simulated waypoints to C2 positions 
+To confirm the message flow is working the SFMC will instead publish
+a waypoints message back to the backbone which C2 can receive and
+process - adding simulated waypoints to C2 positions
 """
 
 waypoint_schema = {

[Trishna Saeharaseelan]

I'm still not sure about this field, but I think it'll be important to have

[Dan Jones]

Doesn't each specification version have a uuid? Can we not include that uuid in both the planning_configuration and in this message to indicate which configuration it applies to?

[Trishna Saeharaseelan]

So, right now, the planning_config_ID is the specification.ID. We could however (which I think makes more sense) change it to specification.version.ID?

[Dan Jones]

Yeah I think I made some changes to one of the messages so it would validate with either an integer or a UUID but I can't remember if it was that one.

[Trishna Saeharaseelan]

Oh yes yes, just double checked. specification.version object has a uuid field. I'll use that (we never used it in the end)

[Trishna Saeharaseelan]

@victord to review this MR as well

[Victor Darvariu]

LGTM, thanks.