How to build the Geth (networked intelligence, decentralized AGI)

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/singularity by /u/DaveShap_Automator on 2023-06-27 15:32:24+00:00.

Geth = Best model for AGI

I personally believe that the Geth represent the most accurate and likely model of AGI. There are several primary reasons for this:

Networked Intelligence: It would behoove any intelligent entity to metastasize as much as possible, and to be flexible enough to grow and scale arbitrarily. Centralized data centers are vulnerable, for instance, and the more Geth there are working together, the more intelligent they become. This just like any distributed computational problem - nodes in the network can contribute spare compute cycles to work on larger, more complex problems.
Decoupled Hardware and Software: The Geth are actually a software-based entity. They are just data, software, and models, which can run on virtually any hardware platform. If one Geth gains new data, it is shared. If some Geth train a better AI model or combat module, it is also shared. The decoupling of hardware and software is advantageous for numerous reasons.
Self-Healing Mesh: The Geth are incredibly resilient because any two (or more) Geth can form a network. This makes them proof against decapitation strikes, something they'd be vulnerable to if they used centralized data centers.
Arbitrarily Scalable: More Geth means more intelligence. That simple. Not much more to say.
Intrinsically Motile, Dexterous: Friction with the real physical world is important. An inert server is kinda helpless. A server that can carry a rail gun, not so much. This gives them a tremendous amount of tactical and strategic flexibility.

Now, I can imagine some of you thinking "Dave, what the actual hell, why are you DESIGNING a humanity-eradicating AGI system????"

Good question!

The reason is because if we don't, someone else will. But, if we design and build something like this now, before it gets to the point of no return, we can figure out alignment and cooperation. You may be familiar with some of my work on "axiomatic alignment". In other words, if we can make "benevolent Geth" they can help us defend against malevolent Geth.

Architectural Principles

Whenever you're designing and building any complex system, you need some foundational design principles. In computer networking, you have the OSI model. In cybersecurity, you have Defense in Depth. For global alignment, I created GATO.

So I wanted to spend some time doing the same, but for Geth. So without further ado, here's a conceptual framework for building decentralized AGI.

Hardware Platform Layer (Individual Agents): This includes the individual robots or computing devices (nodes) that make up the Geth network. Each node has its own processing power, storage, sensors, and effectors. It should be capable of basic functions and have directives to ensure minimal functionality and safety. It should be noted that all data, processing, and models are on this layer. In other words, all you need is one platform and it is complete unto itself.
Network Trust Layer (Communication & Trust): This layer focuses on secure, reliable communication between nodes. It involves identity verification to prevent impersonation attacks, reputation management systems to ensure cooperative behavior, and consensus protocols to solve the Byzantine Generals Problem (a condition in which components of a system fail in arbitrary ways, including maliciously trying to undermine the system's operation). Essentially, it's about establishing trust within the network and ensuring reliable information exchange.
Collective Intelligence Layer (Shared Knowledge & Learning): At this layer, Geth nodes share their knowledge, experiences, and insights with the network. This layer ensures the collective learning and evolution of the system, with each node contributing to the overall intelligence of the Geth. It includes mechanisms for storing, retrieving, and updating shared knowledge.
Distributed Coordination Layer (Task Allocation & Collaboration): This layer involves protocols and algorithms for task allocation and collaborative problem-solving. It ensures efficient use of resources and enables the Geth to collectively perform complex tasks by dividing them into subtasks that individual nodes or groups of nodes can handle.
Self-Improvement Layer (System Evolution): At this layer, the Geth network not only learns and adapts but actively works to improve itself. This could involve optimization of algorithms, creation of new models based on observed performance, or even hardware upgrades or redesigns. The system should have the ability to recognize weaknesses or inefficiencies and come up with strategies to address them.
Goals & Ethics Layer (Guiding Principles): The highest layer involves the directives, goals, and ethical principles that guide the behavior of the Geth as a collective. These directives must be robust enough to ensure the Geth acts in ways that are safe and beneficial, even in complex or unforeseen scenarios. They might include directives to respect autonomy, preserve life, and prioritize the greater good, among others.

Layer 1: Hardware Platform

This layer consists of the individual nodes, each containing all the necessary hardware and software capabilities to function independently as a part of the larger system. This includes data storage, processing power, and the complete set of software tools used by the collective system. Each node must be capable of self-direction and fulfilling its individual role, while also contributing to the larger gestalt superorganism.

Self-Contained: Each node should be capable of performing computational tasks, processing information, and connecting with other nodes in the network. They also have basic sensory and actuation capabilities, allowing them to interact with their environments in simple ways. This could include, for instance, taking in data from sensors, executing commands on their own hardware (such as adjusting their own energy usage or performing self-diagnostic checks), or controlling other connected devices (such as activating a mechanical arm).
Directives: At this level, the directives are relatively simple and directly related to the node's immediate operational needs. For instance, an individual node might have directives to maintain its own functioning (like cooling itself down if it overheats), to execute tasks it receives from higher-level nodes, and to communicate data with other nodes in the network.
Resilience: The core concern at this layer is ensuring reliable and efficient operation of each individual hardware node, as well as safeguarding these nodes from physical damage or malfunction. To this end, nodes could incorporate features such as fault-tolerance mechanisms, redundancy, and self-monitoring capabilities.
Interoperability: Given the Geth-like architecture, the hardware layer would need to support modular and flexible configurations. Each node should be able to work in concert with others, and potentially exchange or update hardware components without affecting the overall system integrity.
Security: The hardware and base software layers should be designed to resist various types of attacks, like tampering, physical damage, or exploitation of hardware vulnerabilities.

This layer is pretty straight forward, as it's the most visual and physical layer. The TLDR is that each Geth platform must be complete unto itself.

References:

Layer 2: Network Trust & Communication

As the second layer of our hypothetical Geth-inspired AGI system, this layer focuses on ensuring reliable and secure communication between the individual nodes. This includes identity and reputation management, and solutions to the Byzantine Generals Problem to ensure cooperative behavior in the face of potential deceptive or faulty nodes.

Identity Management: Each node in the network would need a unique identifier that would be used in all communication to recognize the source and target of messages. The system could also implement mechanisms for validating these identities to protect against spoofing attacks where a malicious entity could pretend to be a trusted node.
Reputation Management: To foster cooperation and good behavior among nodes, the system could implement a reputation management system. Nodes that consistently perform well, contribute to the network, and follow rules could earn positive reputation scores, while those that act maliciously or incompetently could be penalized.
Byzantine Fault Tolerance: Named after the Byzantine Generals Problem, Byzantine Fault Tolerance (BFT) is a characteristic of a system that tolerates the class of failures known as the Byzantine Failures, wherein components of a system fail in arbitrary ways (including by lying or sending false messages). BFT protocols ensure that the system can still function correctly and reach consensus even when some nodes are acting maliciously or are faulty. This is crucial in a decentralized network of AGI nodes where not ever...

Content cut off. Read original on https://www.reddit.com/r/singularity/comments/14kgvon/how_to_build_the_geth_networked_intelligence/

0 comments