| `planning_configuration` | Autonomy Engine's Configuration file (if c2 needs to update its respective platform directly)| No |
| `mission_plan` | Mission plan generated by Autonomy Engine per platform | No |
| `encoded_mission_plan` | Encoded/serialized platform-specific mission plan | Yes |
| `encoded_platform_status`| Encoded/serialized platform-specific platform status | Yes |
| `platform_status` | Decoded/de-serialized generic platform status | No |
| `encoded_observation` | Encoded/serialized observation data from platform for Autonomy Engine | Yes |
| `observation` | Decoded/de-serialized observation data from platform for Autonomy Engine | No |
| `acknowledgement` | Decoded/de-serialized acknowledgement message from the Hydrosurv Adapater | No |
Each message below will be treated as the `payload` that are wrapped in a `full_message_format` that includes a `message_header`:
*`mission_plan`: these would be two message types, i. encoded (platform-specific serialized message) and ii. parsed, human-readable message.
*`platform_status`: these would be two message types, i. encoded (platform-specific serialized message) and ii. parsed, human-readable message.
*`observation`: this would be desired scientific data sent by the platform
*`acknowledgement`: level of acknowledgment where an acknowledgement is sent when a message is i. received, ii. sent to the next destination (e.g. platform in the water).
