@calingribble I get what you're saying. And I'm really trying to come up with good a technical reason, but... here's what I got.

```
1) I've been told (and I believe) it's good to have your architecture map to your business logic. So if there are seasons in the business logic, there should be seasons in the architecture. 
2) I also have this idea where an admin could pick a season to work within where all data as scoped to that season. While it's currently not a requirement, it would be cool.
3) By making the season object, the creating and setting of dates is obfuscated from the user. This way we still get ability to work with dates without requiring the user to set the date perfectly. 
```
I know those aren't great answers, but it's what I got.