move processor models to "model" module
While the generic interface in schedule.v definitely needs to be part of the behavior specification, the actual processor state definitions (the stuff in the behavior/schedule/ directory) actually doesn't. Conceptually, these are different models of possible processor platforms, and hence should live in the model folder (akin to the different notions of job readiness). This will also require moving a bunch of facts from the behavior module to the model module.
I'm planning to eventually do this once the dust has settled around the other changes currently in progress (this ticket serves as a reminder), but feel free to go ahead and do it if you have cycles.
Please comment if you have opinions on this.