Technote imminent.

How do we want to handle review of this? We've got something in place, and it's not "complete", but it's enough to start writing an API against (as we've done). Should we ask for a third party to read it over for clarity?

My opinion is that there isn't much value in a review. It's a working document that describes the system we're building and helps us coordinate between each other. And we're continuously improving it. As some point we could put it out for review when the framework has stabilized.

That works for me. Should we merge and close it now, and add tickets for other future changes as they come up? (e.g., defining provenance, checking industry standards for "service level agreement" names, which this is very similar to)

We've got coherent enough text to start building an API based on this design. Names and API details are likely to evolve, but this is a good start.