Very rough start to very rough draft of DRP criteria.

[TallJimbo]

I think the goal here is for this to read like a high-level summary of our V&V plans, but I'm not sufficiently familiar with those plans -
especially at the point in time this criteria is supposed to reflect - to write that summary.

I'm happy to take pointers on the direction I should take this, or just wait until other DM content is in and the answer to how this should fit in is more clear.

[cclaver]

Jim, your assumption is correct. This document is mean to serve as a "road map" to the overall V&V plans. This is also the place where we can define limits on some requirements that are open ended - however, these too would be in the V&V plans.

Think about this as something we would hand to someone in DC when they ask "Are you done?"

[TallJimbo]

I think my biggest question is where this is meant to sit in the timeline - in I tend to think of DR1 as my team's big end-of-construction milestone, even though that's across the construction/ops boundary, both because the team itself will have a lot of continuity and because most of our external-stakeholder interactions are with scientists who care about DR1 but don't care much about the ORR (and we're definitely not going to stop working on things between ORR and DR1!). But I know there are plenty of others in DM who do understand that timing question, and I think the best thing for this PR is to have it mostly sit here until they have time later this week to help with integrating it with what they had planned to write.

This is also the place where we can define limits on some requirements that are open ended

This, however, is something I can try to improve in the meantime; I'm certainly aware of some things that are not going to really be testable with less than a year of data (and many more that won't really be testable if commissioning is cut too short), and I can try to summarize those here.