Adding qualification assertions to brane-chk #271
Description
(This issue assumes that #270 has been merged)
Currently, the brane-chk's StateResolver accepts workflows happily before passing them to the checker. However, they are much more meaningful if the checker can assume the information in them is correct. As such, consider adding assertions before running a workflow:
- Check if users are who they say they are (requires user auth to be done)
- Check if datasets have been created yet
- Needs to define a difference between hypothetical questions (i.e., does the original input exist and does the workflow describe all steps to get to the direct ones?) VS concrete questions (we're now at this step in the workflow, do all the inputs really exist?). Maybe we even want to change the base policy to reflect this.