Roadmap discussion: what should AssureLoop support next?

[tendervault]

AssureLoop v0.3 hardware-alpha is intentionally narrow.

Current supported hardware-alpha board:

• ST NUCLEO-H563ZI

Current focus:

• Zephyr firmware
• MCUboot signed image workflow
• SBOMs
• release manifests
• evidence bundles
• update package verification
• hardware MCUboot lifecycle validation

This issue is for roadmap feedback.

Possible next directions:

1. Improve NUCLEO-H563ZI release polish.
2. Add a second board, likely Nordic nRF52840 DK.
3. Improve app/version propagation in lifecycle logs.
4. Add better hardware negative-update evidence reports.
5. Improve release artifact viewer/report output.
6. Add OpenChain/SPDX/NIST SSDF alignment docs.
7. Add more CI/reproducibility checks.
8. Add optional serial capture automation.
9. Add a clearer design-partner evaluation path.
10. Keep the scope narrow and harden the existing workflow.

Questions:

1. What would you prioritize next?
2. Should AssureLoop support another board before improving release reports?
3. Which board or MCU family would be most useful?
4. What evidence artifacts are missing?
5. What would make the project more credible to embedded teams?
6. What should AssureLoop avoid building?

Reminder: AssureLoop is not production OTA, not production secure boot, and not a certification claim.