handle all outstanding @todo annotations in Lando model

[kiniry]

Our Lando model has over 200 outstanding @todo annotations in places where we have to drop in definitions/explanations for domain engineering model elements.

These explanations are not strictly necessary for the first implementation of the model, but need to be complete for final delivery of the system. We use them, in part, to check the completeness of the domain model and to generate the final glossary for the system.

This issue will track our progress on updating these explanations.

• acronyms.lando 78 remaining
• architecture.lando 31 remaining
• dataflow.lando 13 remaining
• glossary.lando 86 remaining
• hardware.lando 19 remaining
• requirements.lando needs to be filled in

[kiniry]

I'm taking care of these during report polishing.

[kiniry]

I was unable to finish these in time for the final NRC release, so I am removing their milestone and will label them Someday.

[kiniry]

I'm using GPT-4 to revise these specifications now. I provided a prelude to explain HARDENS and RDE, then bootstrapped its understanding with an EBNF grammar of Lando and an explanation of our approach to domain engineering, then provided each partial specification in turn, reviewing the output for inclusion here. Here is the resulting transcript of my co-design with GPT-4.