<running>/<intended> MUST ALWAYS be valid #4
Description
This “MUST always” is probably too strong and does not consider some cases (e.g., software upgrade), some comments from Rob:
I think that there are certain actions, e.g., software upgrade where systems may struggle to guarantee that always stays valid, and one valid option for handling this is to allow it to become invalid, and then require the first edit-config/edit-data operation to get
<running>/<intended>back to being a valid datastore again.