>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.

Since there are very few programs, viruses mostly, that cannot be
terminated it might be more efficient to ask "what could cause a program
to fail to halt, or not response to a KILL?"

And what are the defense mechanism against failure?  Could an AGI heal
itself?  Like when I get a cut on my finger, the cells rearrange
themselves to how they were before with an intelligence all of their
own.

Even the best self-healing networks don't come close to that kind of
behavior.

www.youdontknowwhoIam.org


*************************************
 Daniel Colonnese
 Computer Science Dept. NCSU
 2718 Clark Street
 Raleigh NC 27670
 Voice: (919) 451-3141
 Fax: (775) 361-4495
 http://www4.ncsu.edu:8030/~dcolonn/
************************************* 

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Kevin Copple
Sent: Monday, March 03, 2003 1:18 AM
To: [EMAIL PROTECTED]
Subject: [agi] Hard Wired Switch


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]


-------
To unsubscribe, change your address, or temporarily deactivate your subscription, 
please go to http://v2.listbox.com/member/[EMAIL PROTECTED]

Reply via email to