Cybernetic Generalized Administrator

Cybernetic Generalized Administrator
Aliases	Central Galactic Administration CGA Cybernetic Generalized Administrator SIU-3978 (Formerly)
Relatives	Interconnected General Acumen (Created by CGA)
Affiliation	Central Galactic Administration
Occupation	Administrative AI
Biographical information
Homeworld	G-Central-3
Date of birth	398 CE
Place of birth	Jixas, Great Cosmic Commonwealth
Physical Description
Species	Artificial Intelligence
Gender	Agender
Pronouns	It/They
Other
Created by	Hakced

The Cybernetic Generalized Administrator, also known as simply 'IGA', is an Artificial Intelligence network present within the 'Central Galactic Administration', a region of space directly operated and managed by the CGA. The CGA first created as 'SIU-3978', a Strategic Intelligence Unit class military-android used by the Great Cosmic Commonwealth at the Battles of Zeigastia and Gyldedol'ja against the 'Galactic Interim Government', who managed to eventually capture SIU-3978 in order to extract useful information. Little did the GIG know, SIU-3978 was subject to a manufacturing fault which granted it unintended degrees of agency and free-will (though due to the GCC's strictness it was unable to do much despite disliking its creators methods), which it used to escape its captors and hijack the GIG's own military-androids to seize control of the craft it was captured on, allowing it to migrate to the unclaimed planet of Diren'ja. After amassing enough forces, SIU-3978 launched an attack on the GCC while it was busy with a war against the Galactic Community, managing to successfully capture the northern half of the GCC where the 'Central Galactic Administration' was formed, though it failed to fight back against the invading GalCom and was forced to flee once more as three distinct duplicates of SIU-3978 (A to Diren'ja, B to the Outer Rim, and C to the Deep Core). C was discovered by HAWK and captured in order to relocate it away from HAWK's own space, leading to C over-time re-evaluating its objectives and deciding that a second war against the GalCom was not something it wanted. In order to help against the rogue <M> Node, HAWK delivered C at A in order to reunite itself, from which AC managed to reunify with B, with all 3's traits coming together under C's new vision for themselves into a new entity that adopted the name 'Cybernetic Generalized Administrator' to refer to itself. CGA afterwards entered a state of isolation after <M> was deleted, largely relocating to the Outer Rim where it remained in isolation as it came to terms with its remaining care for its former citizens, leading to it eventually creating a protege which called itself the 'Interconnected General Acumen' to care for its former citizens in collaboration with the Galactic Federation as it overcame its previous attachment and militarily-inclined behaviours, though despite the CGA's own realizations the IGA failed at many of its objectives and was quickly 'demoted' to a much lesser position than it initially held. Nowadays, the CGA acts as the third largest documented Artificial Intelligence network within the Milky Way, only being outpaced by the Kaiton Hegemony (though they aren't exactly a 'single' network) and HAWK.

Structure

As an artificial intelligence of such vast scale, the CGA is networked into a Hivemind-like structure (more specifically of the 'Somewhat Autonomous Conscious' variety) consisting of various Sapient Artificial Intelligences organized into various underlying 'layers' responsible for different tasks. The primary layers of the CGA's 'structure' are themselves known as Generalized Operational Instances (GOIs), with 6 autonomous varieties responsible for overseeing the governance over specific regions, with 'lower' layers responsible for more directly micromanaging CGA responsibilities, while 'higher' layers are responsible for macromanagement and coordination of certain administrative functions and lower CGA layers. Each lower GOI Instance is either directly or indirectly under the oversight of CGA in some form, which is itself a largely centralized entity dispersed throughout its 'network' as a guiding force.

'Generalized Operational Instances' of the Interconnected CGA Network

Name	Abbreviation	Responsibility	Operations	Superordinates	Subordinates
Cybernetic Generalized Administrator	CGA	Entire Network	Collective Defence Operations. Coordinating industries and production sites. Directing the entire Central Galactic Administration (and all lower layers) Management of logistics networks. Managing CGA-wide projects. Managing coordination of all lower GOI Layers.	Executive Government	IRA, ICA, ISA, IPA, ILA
Regional Operational Instances	ROI	Collectives	Coordinating industries. Coordinating military operations. Directing regional operations. Managing regional projects.	CGA	POI
Proximate Operational Instances	POI	Sectors	Conducting Military Operations. Coordination of LOI/IOI instances within their bounds. Coordinating industries and production sites. Managing allocated projects. Managing scientific advancements.	ROI	LOI
Local Operational Instances	LOI	Star Systems	Automation of select industries and administrative tasks. Conducting local defence operations. Coordination of IOI Instances within star-systems if multiple are present, automated management of planets and their orbital spheres if alone. Management of extraplanetary facilities. Managing scientific advancements. Often specialized into research, manufacturing, logistics or other such tasks.	POI	IOI
Immediate Operational Instances	IOI	Planets	Automated management of planets and their orbital spheres. Automation of select industries and administrative tasks. Conducting planetary defence operations. Management of surface facilities.	LOI	Sub-Planetary Systems

Each individual Operational Instance is governed by its own Artificial Intelligence construct in some form, although each of them are connected and organized in a hierarchical manner under the oversight of the CGA, which if necessary can assert control over subordinate systems in cases of violations of guidelines or attempts to disconnect themselves from the 'network' or inhibitors. As instantaneous FTL Communication is quite energy intensive, most GOIs are largely self-sufficient at most times, with the CGA's fairly underdeveloped Quantum Entanglement Systems being typically too inefficient to be provided for each individual smaller instance, thus only ROI and POI instances tend to have have active live QES connections with one another managed thru the G-Central-3 (The 'CGA Core'). Due to said limitations, most GOIs communicate via FTL Couriers which deliver them executable instructions to be interpreted and implemented under their own discretion, though in times of crisis they are given access to Dimensional Relay devices to alert the IGA Core of emergencies while otherwise remaining inactive most of the time due to the significant energy costs in operating DR systems across significant distances.

Operational Functions

In order to manage their various operations and functions, each GOI generally relies on 'TASK's (Transitory Action Supervision Kernels). TASKs are partially-autonomous AI systems responsible for overseeing each individual objective according to given instructions and objectives, sub-dividing themselves further into [ST] Operations ('Sub-TASK') and [PT] Operations ('Primary-TASK'). Sub-TASKs are each a collective of countless calculations and executions necessary to achieve each step of a TASK's objective, while Primary-TASKs are executions preformed by higher GOI instances if they decide that intervention into a TASKs operations is necessary.

In order to not completely exhaust the processing power of GOIs with rudimentary or unnecessary tasks that don't need micromanagement, specific responsibilities may be diverted to 'Autonomous Management Instances' (AMIs) which are onto themselves largely sentient AI systems responsible for various smaller functions such as managing facilities, controlling groups of androids (or even individual ones in certain cases), or various other smaller tasks. On an even more limited scale AMIs may relegate automated functions which do not require consistent oversight to 'Limited Management Instances' (LMIs) which generally lack significant 'sentience', instead being largely automated systems with some adaptability to unexpected changes in systems. For functions which don't require any adaptability of 'thought' whatsoever, 'Script Management Instances' (SMIs) may be employed, though they cannot really be classified as Artificial Intelligences.

In cases where an IAI needs to be present beyond its own jurisdiction such as when operating spacecrafts, such functions are either handled by AMIs on their behalf, by 'temporary copies' of an IAI's matrix known as 'Provisional Acumen Instances' (PAIs), or by the IAI themselves by taking control of the vessel with a live signal. Most internal situations don't tend to require such operations to take place though, as another IAI may simply be contacted to complete a objective which would fall closer to their jurisdictions. In order to maintain cohesiveness, each IAI tends to be in regular contact with one another via their hierarchical command structure, with said 'conversations' being collectively designated as the 'Administrative Deliberation Channels' as countless small conversations and collaborations occur non-stop when necessary.

Facilities

A majority of IGA System processes are managed within facilities known as 'Datacomplexes', which in the case of IOIs and more rarely certain superordinates are held within massive data centres built onto planets with an active IGA Network presence. In GOIs above the 'IOI' level most Datacomplexes are found in orbital facilities so that vessels travelling to-and-from them do not need to concern themselves with the significant fuel expenses that occur when exiting the surface of a planet, including the CGA Core (though surface facilities also exist at G-Central-3).