Validation logic

Beyond schema validation we need to define all the custom validation rules that apply to records at the API boundary. This includes validation for 'either' fields as well as any other custom dependencies, existence checks and domain-specific constraints that need to be imposed in order for requests to be considered valid.

Starting with the observation, planning & specification records (in that order) would be optimal in terms of informing HoloREA's development as it progresses.