Multinodal Core: Difference between revisions

From Solas Tempus DB
Tag: Removed redirect
No edit summary
 
(8 intermediate revisions by the same user not shown)
Line 1: Line 1:
The multinodal core is a device that allows sentient AI programs to be transferred between cores at will using the Ansible Transit Protocol.  This is an extension of the Island Protocol first developed in 2155 for use in Guin style computers, state of the art at the time. This communications protocol between networked subspace peers was standard prior to the advent of Duotronics in the early 23rd century.  The Ansible Transit Protocol uses a forced quantum entanglement between subspace nodes over a domain similar to that of a [[transporter]] beam.  The idea first came from a study of how Borg technology is able to maintain the collective consciousness over such vast distances.
[[File:{{#setmainimage:multinodal-core-full.jpg}}|thumb|Full (Version 1)]]
[[File:multinodal-core-slim.jpg|thumb|Version 2]]
[[File:multinodal-core-small.jpg|thumb|Version 3]]
[[File:multinodal-core-micro.jpg|thumb|Version 4]]
The multinodal core is designed to allow an AI to operate synchronously between multiple devices that are not physically connected, with a near-zero lag time between different nodes receiving updated information. To facilitate this, a new communications protocol called the [[Ansible Transit Protocol]] or ATP has been developed.


== Ansible Transit Protocol (ATP) ==
== Full Core ==
This communications protocol governs the establishment and use of forced-entangled subspace transmission beams over multiple adjacent subspace domains. The protocol establishes a subspace lock onto a destination device and forms a unique quantum signature node within both the sender and receiver. Each node is then forced into an entangled state using a quantum inversion tunnel.  This process establishes the nodes to the subspace connection.
A full multinodal core, directly attached to primary power and communications systems, serves as a centralized server node for ATP transfer. To avoid transmission errors, an AI matrix is stored in sync with the central node via forced subspace entanglement. The transmission channel for a full consciousness transfer is initiated from the central core to a destination through the attached communications system. Additionally, the full core is equipped with a fully integrated holographic projection system, allowing an installed AI matrix to directly project itself or any desired data in the local area.


== Nodes ==
=== Ansible Initialization ===
In this case a given node on each side of the ATP is located within the core itself, formed as needed facilitated by access to a subspace transceiver.  The nodes exist within the core as they are adjacent to the [[Encapsulated Computer Core]] which actually runs the AI program, directly feeding information into the ECC. To do this the nodes need to be made in such a way to bridge between the internal subspace domain of the ECC and the outside world.
The full core is capable of initializing other cores through a direct connection to an uninitialized core. Initialization via subspace is theoretically possible but falls outside the protocol's specifications.


== Consciousness Transfer ==
=== Redundancy ===
To properly transit an active AI matrix without the loss of data outside of a local computer system, that program must be sent in a logarithmically tiered series of connections. The ATP is used to establish a layered series of connections so that each overlapping tier arrives in sync to adjacent tiers without the need to suspend or otherwise interrupt the consciousness. This is analogous to transporting quarantine patients between medical facilities where the quarantine unit is several microseconds ahead of the actual patient.
The full core has dedicated power redundancy, as well as its own transceiver array. This array serves as a backup to the connected array, ensuring system functionality even if the primary array is offline. Similarly, the redundant power supply within the core itself serves the same purpose.


The core establishes multiple transit nodes with the same peer over subspace.  Each node is responsible for one, and only one, of the tiered layers. Since consciousness information is continuously changing a single node transfer has the side effect that different aspects of the mind become out of sync with each other.  Using multiple nodes the facets of the mind can continue to change and stay in sync as alterations from one layer to another are sent time-coded there significantly less strain on the AI matrix.
=== Diagnostics / Maintenance ===
A full core can perform advanced diagnostics, automated repair adjustments to smaller cores, and manage damaged or power-depleted cores. Smaller cores are only capable of running basic internal diagnostics on their own hardware and software. The full core can run remote diagnostics on any part of the node array.


Sending the consciousness in tiers this way has the side effect where the original matrix at the origin point becomes internally desynchronous and the matrix no longer has internal cohesion. While all the data and information is still present it cannot maintain and integrity and ceases to function.
== Component Core ==
The second and third versions of the core are designed to be system components for the [[Mark I Humanoid Android Body]] or any other system with size constraints. Primarily intended to be integrated into a single device, they are small enough to fit within the standard android body head. They have their own limited reserve power supply and a simple diagnostic interface if the device is opened. However, they lack an independent transceiver array and rely on external components for that purpose. Although the core can be directly connected to almost any computer terminal, it is not recommended. The core should be installed and not removed unless necessary, as the full system it is installed in should handle all communications to and from the core.


== Practical Use ==
The core interface operates as a simple low-resolution holographic display. Engineers can run diagnostics on the core and communicate directly with the AI matrix when necessary.
This kind of core is primarily used to transfer an active AI matrix safely across vast distances.  While a local network can handle syncing an AI transfer over standard subspace communication bands, distances in excess of 1-2 AU's and the distance over subspace can cause stress on the AI matrix, a new protocol was needed to account for possible problems faced by in-service Androids.


== Dangers ==
== Implant Core ==
While the ATP attempts to correct for transmission issues, it is necessary that both the sender and receiver maintain stable power and access to their subspace transceiver. The loss of a layer or even any significant amount of data within a single layer can end with a catastrophic failure of the AI matrix and thus a non-functional AI. Error correction routines are in place to attempt to mitigate this problem, it is still a real possibility.
The fourth version of the core is designed for direct implantation into very small or cybernetic systems. Initially developed for use in the XIA body to enable synchronous function of the third version's [[MSAI]], the fourth version allows the core to be implanted directly into a cybernetic system. Unlike the third version, the fourth version has an interface to the outside world. It features a nano-holographic emitter that enables simple diagnostics to be projected even outside the host device or body in which it is installed. Engineers can use this capability when an AI may be implanted into cybernetics to run diagnostics that the host may not be capable of running themselves.
 
Both Version 3 and 4 cores rely entirely on the host device or body for power and communications.
 
The Version 4 core is a prototype being researched for medical purposes rather than permanent installation into a living host body.
 
== Consciousness Focus ==
Some AI matrices may find it challenging to operate in multiple node locations simultaneously. The system is not designed to allow an AI to operate in an omnipresent way, although it can be used for that purpose. Instead, the system is designed to enable an AI to seamlessly switch between different node locations near-instantaneously from any distance. The ability of different AI capabilities and complexities to operate multiple instances of themselves within the same matrix may vary.


[[Category:Advanced Technology]]
[[Category:Advanced Technology]]

Latest revision as of 04:25, 7 June 2023

Full (Version 1)
Version 2
Version 3
Version 4

The multinodal core is designed to allow an AI to operate synchronously between multiple devices that are not physically connected, with a near-zero lag time between different nodes receiving updated information. To facilitate this, a new communications protocol called the Ansible Transit Protocol or ATP has been developed.

Full Core

A full multinodal core, directly attached to primary power and communications systems, serves as a centralized server node for ATP transfer. To avoid transmission errors, an AI matrix is stored in sync with the central node via forced subspace entanglement. The transmission channel for a full consciousness transfer is initiated from the central core to a destination through the attached communications system. Additionally, the full core is equipped with a fully integrated holographic projection system, allowing an installed AI matrix to directly project itself or any desired data in the local area.

Ansible Initialization

The full core is capable of initializing other cores through a direct connection to an uninitialized core. Initialization via subspace is theoretically possible but falls outside the protocol's specifications.

Redundancy

The full core has dedicated power redundancy, as well as its own transceiver array. This array serves as a backup to the connected array, ensuring system functionality even if the primary array is offline. Similarly, the redundant power supply within the core itself serves the same purpose.

Diagnostics / Maintenance

A full core can perform advanced diagnostics, automated repair adjustments to smaller cores, and manage damaged or power-depleted cores. Smaller cores are only capable of running basic internal diagnostics on their own hardware and software. The full core can run remote diagnostics on any part of the node array.

Component Core

The second and third versions of the core are designed to be system components for the Mark I Humanoid Android Body or any other system with size constraints. Primarily intended to be integrated into a single device, they are small enough to fit within the standard android body head. They have their own limited reserve power supply and a simple diagnostic interface if the device is opened. However, they lack an independent transceiver array and rely on external components for that purpose. Although the core can be directly connected to almost any computer terminal, it is not recommended. The core should be installed and not removed unless necessary, as the full system it is installed in should handle all communications to and from the core.

The core interface operates as a simple low-resolution holographic display. Engineers can run diagnostics on the core and communicate directly with the AI matrix when necessary.

Implant Core

The fourth version of the core is designed for direct implantation into very small or cybernetic systems. Initially developed for use in the XIA body to enable synchronous function of the third version's MSAI, the fourth version allows the core to be implanted directly into a cybernetic system. Unlike the third version, the fourth version has an interface to the outside world. It features a nano-holographic emitter that enables simple diagnostics to be projected even outside the host device or body in which it is installed. Engineers can use this capability when an AI may be implanted into cybernetics to run diagnostics that the host may not be capable of running themselves.

Both Version 3 and 4 cores rely entirely on the host device or body for power and communications.

The Version 4 core is a prototype being researched for medical purposes rather than permanent installation into a living host body.

Consciousness Focus

Some AI matrices may find it challenging to operate in multiple node locations simultaneously. The system is not designed to allow an AI to operate in an omnipresent way, although it can be used for that purpose. Instead, the system is designed to enable an AI to seamlessly switch between different node locations near-instantaneously from any distance. The ability of different AI capabilities and complexities to operate multiple instances of themselves within the same matrix may vary.