# Overview This project repository is a collaborative workspace. It consists of all messages transferred into and out of the Communications Backbone. Message type schemas will be developed once reviewing each platform's data and statuses defined by each partner. # Message Types * Each message below will be treated as the `payload` that are wrapped in a `full_message_format` that includes a `message_header`. | Type | Summary of File | Serialized/Compiled in Platform-Specific Format? | | --------------------------| ---------------------------------------------------------------------------------------------- | ----------------------------------------------- | | `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 | # Quick Links 1. [Schema Fields Definitions](https://git.noc.ac.uk/communications-backbone-system/backbone-message-format/-/tree/7-message-formats-initial/formats) 2. [JSON Schema Examples](https://git.noc.ac.uk/communications-backbone-system/backbone-message-format/-/tree/7-message-formats-initial/examples) 3. [SoAR README.md](https://git.noc.ac.uk/communications-backbone-system/backbone-message-format/-/tree/7-message-formats-initial/project/SOAR_README.md)