I have tentatively called this AI HAL as my name is David but that could change in the future.
HAL (AGI) would consist of a number of interconnected HAL (server) programs running on a number of computers. The HAL language would be used to implement a model based AGI. This model based system could include any number of other types of AI systems including NNs, agent based, and any other system that could communicate over sockets with the HAL language. Some parts of HAL could use specialized hardware in such subsystems like vision or sound analysis. Learning could be accomplished by any number of methods including case based, genetic algorithms, etc. HAL (programmer) is just an identical version of HAL (server) that includes a programmer interface. HAL programs are created from within HAL as HAL executes.
The unique features (at least as a group) that make HAL unique as the tool for creating an AGI are the following:
My financial proposal for this AGI called HAL would be using 3 sets of players:
1. HAL partners would contribute 50% of all computing resources used by HAL (server) in their businesses. These computer resources would be used to operate HAL. These partners would contribute significant time to programming and teaching HAL and in return, the partners would equally share in 50% of HAL's revenues. No royalties would be paid by the partners for use of HAL in their commercial businesses. All revenue from commercial work using HAL by the partners would go to the partner creating that commercial venture. HAL would require 1 unit of computing resource for every 5 copies of HAL (programmer). All computing resources used by HAL would continue to be owned by the partner providing the resource. Decisions made on behalf of HAL would be done by the partners equally or by a partner so designated by a majority of the partners. HAL would get computing resources, programming and teaching time from his partners, as well as 50% of royalties obtained from commercial use of HAL by non-partners. The exact legal structure of the corporation that would embody this partnership would make getting in on the HAL project at an early stage both financially lucrative and with a minimum of risk and financial outlay.
2. HAL royalty users would pay an (as yet) unspecified royalty for commercial use of HAL. In general, these royalties would be a small part of the commercial project and would be designed to encourage many developers to use HAL. 50% of these royalties would be kept for HAL and 50% would be divided by the HAL partners.
3. The public would be encouraged to use HAL in return for unused computer and hard drive resources. I think that HAL could quickly have control over huge numbers of unused CPUs and huge amounts of unused hard drive space using this method. The benefits received from HAL would be paid for by a resource that is not being used now at all. HAL could provide a huge number of services in a redundant network of thousands of computers. Unlike most languages, HAL (language) can only access the directory it is started in and a few sub-directories of that directory. No virus or other program in HAL could ever affect, change or harm any programs or data on the rest of the computer. The public would be assured that no illegal work would ever be done on their computers.
Some questions that have been asked of me about HAL:
Question: Would I (the creator of HAL (language)) consider making HAL an open source project?
No. I am always open to listening to others point of view but my initial reaction is that I don't think open source is a good idea. I think that the best programs are written by a single person but I would be open to discussing any constructive suggestions for enhancing the language. I don't say this for any proprietary reasons. I have found that one programmer makes a better program quicker than even 10 or more programmers because of all the detail communications that entails. I would be willing to turn over legal rights to the language, to the HAL corporation owed by the partners and HAL. (HAL's 50% would have to be administered by others until he could legally look after it himself.) If the partners found that I wasn't the best person to continue to develop the language then I would turn over the source to someone else to continue the development. I am not interested in having a coup, so there would have to be some safeguards but I am not closed to my not being the developer of the language HAL.
Question: Who would program HAL (AGI)?
HAL (AGI) would be programmed by many people but I see the partners being heavily involved early in making programs that make programs within HAL. Most programming after this step wouldn't be actually creating the code directly but more like teaching a child about the world and different domains. The internal structures and programs would normally be created by HAL himself. I have many ideas about how to make the inner core of HAL but I am very open to others viewpoint on this. I think that a central core system can be created so that many approaches to AGI can be conducted simultaneously without prematurely shutting down potential techniques too early. So far, no one system has been shown to create an AGI so for anyone to say "let's put all our eggs in one basket" is probably a little naive.