GitLab

Make the acknowledgement a multi-use message for any backbone transaction that requires acknowledgement

• uuid of mission_plan – currently the autonomy engine plan ID (integer) ​
• add a enum type detailing the type of acknowledgement​
• make platform_ID optional​
• add a human message field?

2 initial MAS-DT acknowledgements are

• Accept proposed changes to specification
• Send plan to gliders

Does the pilot acknowledgement of the specification have to go through the backbone at all?

Could that all be done within the PI app with the specification only being sent to the backbone once that agreement is reached?

changed the description