>Your statement is what I mean. "Thinking things through" should be done during design. Once you have built system, its much harder to compensate for design fla

>Your statement is what I mean. "Thinking things through" should be done during design. Once you have built system, its much harder to compensate for design flaws. I agree with this fully. This is something that would need to be solved before building such a system. A great example of a system which learns from history, but which also supports changes in behaviour is: http://worrydream.com/MagicInk/#engineering_inference_from_history http://worrydream.com/MagicInk/#engineering_inference_from_h... The linked example is specific to one application, but he continues to detail what he thinks would make for a general solution.