Here's an idea (if it hasn't already been considered before): In each executing component of an AGI has Control Code. This Control Code monitors a Big Red Switch. If the switch is turned on, execution proceeds normally. If not, all execution by the component stopped.
The big red switch could be a heart monitor on Ben's chest. The AGI better keep Ben alive! And if Ben gets angry with the AGI, he can remove the heart monitor, so the AGI better keep Ben happy also. Several other features could be thrown in: 1. Components will check that calling components have the active Control Code that every component is expected to have. 2. The Control Code checks that certain parameters are not exceeded, such as AGI memory storage and computational resources. 3. The Big Red Switch monitors not only Ben's heart, but other control parameters as well. 4. The Big Red Switch monitors another AGI, which has a focused purpose of looking for trouble with the first AGI. I imagine that the control code would require a tiny slice of the AGI resources, yet still be effective. Implementation details would naturally require a lot of thought and effort, but I think the concept of a built-in "virus" would be effective. Maybe "immune system" would be a more appealing term. Kevin Copple ------- To unsubscribe, change your address, or temporarily deactivate your subscription, please go to http://v2.listbox.com/member/[EMAIL PROTECTED]
