Data validation project design conversation

[jdangerx]

Overview

We need to have a plan before we jump into this data validation project. Plus the plan has to fit roughly into 75 hours, less the design time (and needs to take review / adjustments into account!)

Success criteria:

• short document that lays out the product design of the system: what specific use cases are we solving for? what hard things are we not going to do? how does the user (us, as developers) interact with the new data validation library?
• short document laying out technical design - what components come together to present the high level interface from the product design? how do they interact with each other / what operations do they expose? what data structures do they exchange?

Next steps:

• get people to complain about the data validation system
• decide who needs to "approve" the product design
• synthesize the complaints into the product design
• get approval
• figure out approvers, work out technical design, get approval there too

At the very minimum we should pick @zaneselvans 's brain about his complaints before he leaves, and ideally we should get some input from him in the product design synthesis part.