Raft-based Application-Level consensus technical design document

[barroco]

InterUSS users have expressed their interest to review the Application-Level consensus implementation in detail. In order to increase reach and simplify collection of feedback internally, a single standalone technical design document has been requested.

Feedback on the expected structure has been provided in the following document.

Background information on the Raft-based Application-level consensus can be found in the August 2026 technical update

[wing-utm-sharing-airspace]

We left some suggestions on the doc. It looks great overall, and we are looking forward to the design doc.

[utmverse]

@barroco - Thanks for putting this out for feedback. The structure looks good to us, and the comments in the doc already cover a lot of ground.

One thing we'd add: since Raft is replacing the datastore, it's worth the doc covering what we lose alongside what we gain — backup and restore being an example. Worth spelling out what an operator restores from, and how an instance or pool gets rebuilt.

[barroco]

@wing-utm-sharing-airspace @utmverse Thank you all for taking the time to provide feedback. We will provide an update in a week on the progress. We currently expect ~ 2.5 weeks lead time.

[barroco]

A draft has been prepared and is currently being shared with a limited audience for a preliminary review.

[barroco]

The technical design document draft is available here for comments.
Feedback will be consolidated as it comes. A call will be organized on October 1st to cover unresolved points if required.

[wing-utm-sharing-airspace]

Wing is actively working to review the design doc and is planning to consolidate feedback by late October.