How can we organize the process of handing off the storytelling engine to Dave? The basic task here would be for Dave to take over three tasks: programming the storytelling engine, supporting Jenn with new function calls, and handling the statistical analyzer. Dave would then handle tuning issues, using the analyzer to identify problems and working with Jenn to correct them.
My problem with this is that the engine, while operational, is still in need of fundamental design work. Am I certain that all aspects of the engine are complete? What about the whole lies element? and secrets? Am I certain that that damn plan purging facility is as solid as it should be? And what about the entire diurnal cycle &emdash; is that the most efficient way to handle this? Perhaps Dave's role should be more analytical at first, just trying to get a grip on the functioning of the engine, looking for flaws in the design or places where we could tighten it up.
Still, I'd like to hand off some responsibility to him, and he's expressed a strong interest in the statistical analyzer. I could hand that task off to him, but then what would happen to the engine? Perhaps the thing to do here is to separate the engine from the analyzer and have him handle a library function that the engine controls, so I retain direct control over the engine for the time being.