The only reason I didn't is because it's not used at all outside of the aggregator, so it would just be polluting the public models (which already has quite a few things). I could create an internal model object for it and encapsulating some of the logic below in model functions might remove from noise from this file (e.g., the defaults would be encapsulated there, and then `hasActor(actorKey)`, `hasObject(objectKey)`, `hasTarget(targetKey)`, `addActor(actorKey, actor)`, etc...)