ARMI has requirements. And there are crumbs pointing to this requirements throughout the ARMI codebase. e.g.

But this is an incomplete picture of the ARMI requirements to the open-source community.

I recommend the following steps:

1. Open-Source the ARMI requirements, and put them in the docs
2. Add SQA docs to the ARMI docs (SRSD, SDID, STR, and SCR)
3. Modify the ARMI PR process so the PR Review always includes a review of requirement/SQA-related changes
   • Institute a rolling SCR with every PR
4. Move from our current "release notes" strategy to something to dovetails or streamlines with the SCR.

On the one hand, this might put a lot of things in that docs that many open-source users don't want to see. One the other hand, it will increase visibility and communicate the ARMI project better to the public.