Two more items to add to the TODO list:
1. We need an explicit, deterministic algorithm for satisfying requirements, down to alphabetical ordering of capabilities and node template names. I suggest that the spec actually contain pseudo-code that implementors can build upon. Doing so will also help us ground the discussion.
2. "Dangling requirements". I remain opposed to this proposed feature, but if it is to be included then it must be specced out in the requirement satisfaction algorithm mentioned above.