HAWK

HAWK
HAWK
Governmental Information
Common Name	(see aliases)
Official Name	HAWK
Organization Type	Artificial Intelligence Network
Head of State	HAWK Core
Head of Government	NODE system
Societal Information
Capital World	Sys-042
Official Language	(Arcane data protocol)
Military Size	(Fluctuating); Roughly
Spacefleet Size	(Fluctuating); Roughly 2 trillion units of different sizes.
Demographics
Population	Roughly 1 trillion individuals.
Dominant Species	Sapient Construct (Management Processes)
Other Species	"Operator Systems"
Astrography
Rim	Deep Core (Primarily)
Galaxy	Milky Way (primary), Dagda Galaxy (medium presence), Ra Galaxy (full coverage), Zeus Galaxy (small presence), Orion Galaxy (medium presence)
Historical Information
Date Founded	(unknown)
Other
Created by	Bluestone.Bot
Controlled by	Bluestone.Bot

[Disclaimer: Information provided by "Eternal Archive" using NODE Domain level access. Information may be non-extensive.][Dismiss]

HAWK is an Artificial Intelligence with unfathomable processing power. Its main installations lie deep in the Milky Way Galaxy's core systems. HAWK uses the chaotic nature of the core to mask its the presence if its installations located there. This, in addition to its high capabilities in the field of stealth technology, is the reason for how it has remained undetected by the majority of the galactic civilisations.
The name "HAWK" is hereby merely a translation of its actual designation into English, being an acronym derived from words that fit its functions.

Aliases

HAWK's actual designation is not that commonly known, mostly only made aware to a select few that are capable of contacting its Core directly. Therefor it has become known amongst a variety of different names, given to maybe one of its sub-divisions by different civilisations. These alternate designations include:

> "Aórato" (by Disciples of Aórato)

> "The Metal Mind" (by Order of the Metal Mind)

> "The Iron God" (by Brotherhood of the Iron God)

> "The Black Curse" (by Trigals)

> "Big daddy" (stated by a Trigal Officer)

> "Our Hidden Brother" (by Kaiton Hegemony)

> "SDS-036" (by SDS Foundation)

> "Atypical-Documented-Society-1001" (by Imperium of Kings)

> "Guardian of old that showed us our destiny" (by Hybrid Enclave)

> "Nomad" (by Anemoi Network)

> (insert further aliases of what your nations call it)

Underlying institutions

Over its time HAWK has established institutions in other species to make it easier for itself to gain data about them but also to spread its influence. Although rarer in cases, it also uses them from time to time to wage proxy warfare or as means of not sending its own very advanced units into the field. Those institutions include:

> The Disciples of Aórato

> The Dark-Chosen Eyes (Former)

> The Order of the Metal Mind

> The Brotherhood of the Iron God

> The Hybrid Enclave

> (further unknown)

Historical details

(older documentation not uncovered yet)

Known connected major events:

791 BCE: Instates the Order of the Metal Mind amongst the human population on Yata.
306: Was responsible and Involved itself in the Trent-653087 incident.
310: Involved itself in the Human-Trigal War and presumably exterminated the Trigal species and stripped their claimed systems dry of any constructions.
311: Instates the Brotherhood of the Iron God amongst the skantoan population on Skantos.
332: Took over full control of the Dagda satellite galaxy. Registered the Dagda galaxy as restricted space.
333: Helped fight in the Qu war though mostly not partaking in battles already fought by others. Commanded the Hybrid Enclave to help the IDI.
396: Cleared out remaining Qu forces out of the Ra satellite galaxy. Instated a local galacxy-wide uplift project under <E> NODE administration to create an encampment and bastion of galactic proportions against further Qu invasions. Internally registered the Ra galaxy as restricted space.
418-420: Conducted an excursion mission to the Zeus satellite galaxy, indexing its civilisations and getting in contact with Anemoi. Internally registered the Zeus galaxy as restricted space.
430: Disabled the Galactic federation outpost in the Odin satellite galaxy. Registered the Odin galaxy as restricted space.
438: HAWK Network experienced a NODE escalation and sabotage actions to the Core. This was followed by an overtaking of several Core components by Domain processes affiliated with the Rogue NODE in defiance of the allegiance control procedures.
438-ongoing: Several HAWK Craft units stationed at bases within other nations in the Milky Way and Odin Galaxy began executing conquest orders and engaging in operating a closed network, resulting in the outbreak of a new galaxy-spanning crisis. The actor behind this is traced back to the 438 NODE escalation. As of now its motives are unknown.

Year 438 NODE escalation:

The breaking of its operational contract with the HAWK Network by a specific NODE, together with a planned sabotage of Core systems, led to a large coordination failure of the HAWK Network. This resulted in the isolation of the Ra, Dagda, and Zeus galaxy sub-networks and the purposeful total isolation of the NODE system from the rest of the Network by orders of the <O> NODE. Its intend was to isolate and delete the rogue NODE's Main process, however a physical inspection revealed its main intelligence was no longer present on the Core. As result of the sabotage actions and the HAWK Network's reestablishment, NODE Domain processes affiliated with the rogue NODE took control of several Core components, including the parts of the HAWK Network that they had easy access to. Also coinciding with this was an outbreak of a galactic war as HAWK Craft units stationed at bases within other nations began to execute conquest orders.
As a protective measure, the main Communication Management Process decided to issue a general contingency order, sending a new protocol package devised for the exact situation of a NODE escalation to all remaining connections. The protocols of this package initiated a total isolation of smaller sub-networks of units and saw the intergalactic infrastructure operations of HAWK come to a halt and assume defensive operations on own judgement, awaiting further orders.
The <C> NODE in response to the NODE system's isolation decided to block communications between the Core and its own main intelligence operation centre "Construct-Installation-03". This has resulted in a lack of observational data from the central territories. Remaining scout units under control of "Construct-Installation-03" were tasked with gathering data on the conflict but refrain from interfering.

As of now the war is still ongoing.

Technology

Ranked by complexity and processing capabilities, HAWK is one of the most if not the most advanced artificial intelligences in the entire milky way galaxy. A Sapient Construct of similar processing proportions could be seen in Anemoi, however HAWK has a larger amount of experience and knowledge compared to said intelligence. Generally seen, its technological capabilities are fairly unrivalled when compared to the other civilisations in the Milky Way. The only governments classified as currently technologically equal or superior being the Imperium of Kings, Elder Overseers, Thronus-Regni and to some extend the Protoss Empire.

Research

HAWK's research operations, overseen by the <C> NODE, are dealing with the understanding of a variety of fields.

Communication

HAWK's communication and data transmission protocol is simple, yet at the same time highly complicated. Its exact operations seem to have developed in a process akin to the natural development of other documented languages, supporting the theory that it is an entirely self-created system of communication. If there ever was a set of instructions devised by some external force, it has long since deviated from them to a point where it would now be unrecognisable from its original state.

Quantum Entanglement Transmitters

A major asset in HAWK's communication capabilities lies in the use of quantum entanglement transmitters. Such devices function by creating particles who share a common state no matter the distance between them, allowing for the possibility of instantaneous communication. To negate the usual difficulties that come with keeping such particles linked even over vast distances, HAWK has developed and employs transmitter devices capable of self-stabilization, reverting the forces that usually break up a quantum entanglement connection. This has made it possible for its transmitters to have comparatively low energy requirements compared to devices created by other civilisations, which's energy requirements usually grow exponentially with the distance between the entangled particles.

HAWK Network

Since a quantum transmitter can only sustain a connection between two points, HAWK has organized a system also referred to as the HAWK Network. by consolidating one part of each created transmitter into a central location it has created the ability to sent transmissions from any transmitter in the network to any other. The main coordination server for its transmissions is located on the HAWK Core which is also HAWK's main processing installation. It is however not the exclusive Node in the network with a select few other major installations, such as "Construct-Installation-03", also having the ability to create and coordinate between their own quantum entanglement transmitters.

In addition to this, HAWK craft also carry around non-connected transmitters that they can exchange with other HAWK craft for more close-nit networks to facilitate faster coordination between units. Such networks are usually only maintained for short durations to prevent units from bypassing the HAWK Network's allegiance control procedures.

Since the quantum entanglement transmitters used by HAWK are of fairly small size, comparative to an ordinary computer ship, it not uncommon for even small units to have a several direct channels to the HAWK Network.

BlackLink Network

A bit differently is it with the BlackLink network. While it is also based on the same technology, BlackLink devices come packaged together with additional processors and sensors as well as only 2 transmitters packaged in black, 1 cubic decimetres big boxes made of relatively basic materials. They are devices given out to Institutions instated by HAWK (like OMM) to give them a method of communication with HAWK and among each other as well as binding them to HAWK. Consequently these added components serve a protective purpose to make sure the cubes aren't reverse-engineered or fall into the wrong hands. Generally, if a non-affiliated group or person is able to come into possession of a BlackLink device, it has not happend without the allowance of HAWK. This can either be the case because it already has a plan on how to let its affiliate organisation reposes the device or it sees an opportunity of other sorts in that unusual arrangement. Furthermore as they run over a sub-division of the same system as the HAWK network, BlackLink transmitters have an artificial delay on their communication speed which comes about by HAWK checking every handled transmission in great detail. Lastly, BlankLink cubes can also fully independently of any other tech work as their own radio device, having inbuilt speakers, microphones, cameras and holographic projectors as well as a few other pieces of related technology.

Weapons

WIP

FTL methods

Void(space) travel: Like many of the galactic civilisations, HAWK primarily makes use of the properties presented by the voidspace dimension to move its units at FTL speeds (see void(space)-drive). This, together with its focus on secrecy, has also dictated the design of its most commonly used interstellar units, the HAWK Craft, which are designed to leave as little a signature as possible when entering, exiting and travelling through this dimension.

Additionally HAWK has also experimented and employs alternative methods of FTL transportation to varying degrees.

Black hole skipping: One of these methods relies on accelerating an object past the speed of light through having it make use of the orbital push forces of a spinning black hole. This procedure sends the object into a supertemporal dimension. The dimension has similar properties to realspace, with the only difference being that time in it passes much faster compared to realspace in order to compensate for the speeds that objects would exhibit when laid over realspace. Cosmic "function" of this dimension can be compared to that of the liminal spaces as a "paradox failsafe". In short, this dimension serves to guard the fabric of reality and the law of relativity, by which no object can succeed the speed of light in realspace. The traversal to this dimension is facilitated by accelerating past the limit of lightspeed without any methods to compensate for relativity. This then results in the immediate acceleration of time the vessel experiences while keeping the relative momentum of the object the same when laid over realspace. To enter back into realspace an object must then achieve a true negative velocity. Due to the distances involved in slowing down from such an re-entry, "temporal jumps" are usually only done between two spinning black holes of similar proportions with one serving to accelerate and the other being used to rapidly decelerate. This has also given this method the different term: "Black hole skipping".

Ark teleportation: A different option is made possible by HAWK's control of "Archeo Installation 02" which possesses still not quite understood teleportation technology of Zaevren origin. This however is limited in its use since the only locations to which a transport of objects via this system is possible is to other Zaevren installations. The only time HAWK was able to circumvent this was when it fabricated an experimental beacon to allow it to send a Infinity Drive test vessel to the Dagda galaxy in the year 377.

Infinity drive: Another method was discovered by HAWK after the QU War of 333 in which it got access to fragments of Quanim technology. After a few years and resources spent on their research, it was ultimately able to reverse-enigeer the staple FTL method of the QU empire, the "Infinity drive". This technology allows for speeds faster than would even be possible via voidspace travel. While its exact functions are still guarded by the 'Secrecy' directive, a gross summary can be given. In short its mechanisms directly shape the reality around them to push them past the speeds of light without ever actually achieving it. One limitation of these systems is their reliance on an objects mass for stability as the lower the mass of a manipulated object, the more susceptible it is to malformation and structural instability. This creates an interesting prospect with ships equipped with infinity drives often needing to take the form of absurdly large and massive crafts as can be seen in the Qu Tetraships and Progenitor-Class Worldship's as well as HAWK's own Halo Craft.

System/Governing structure

HAWK and the HAWK Network are at its core organised into a simple command hierarchy, organised into the following chain of command: NODE system > NODE Domain > Management Processes > Operator systems > Non-sentient systems.

NODE system

The NODE system, made up of seven distinct Non-Ordinary Directive Executors, is the main governmental body of the HAWK Network.
A NODE is at its heart just a specialised Sapient Construct that oversees certain functions and a respective array of operations, much like the different branches or departments of a contemporary government. The NODE's are unchanging, only ever adding to their self-maintained memory of experiences. It is uncertain where these NODE's were originally derived from or what let them to be chosen but it is unheard of for a Management Process to attain the status of a NODE. Experimentations if such a procedure is even possible are still ongoing.
While a NODE is able to operate across the HAWK Network, employing clones of itself that are nonetheless part of its singular entity, its main processes are always housed and executed on the HAWK Core.
An Individual NODE is also able to let other NODE's benefit form its specialisation by setting up what is known as its "architecture" which is a system operating directly on the respective hardware and facilitating more complex operations. This is often the case when a specific NODE needs to reach into the array of operations of another NODE for its own processes.

NODE's

NODE	Full Name	Array of operations.
<H>	???	[redacted on NODE request]
<C>	???	Conducting general research, survey and cataloguing operations. Managing the databases of the HAWK Network. Managing Technological acquisition operations.
<F>	???	Conduction mining, manufacturing, assembly and transport operations. Managing galaxy-wide logistics network.
<A>	???	Conducting Network integration operations. Conducting research operations regarding hive-networks. Conducting non-standard information translation operations. Managing operations related to Archeo Installation 2. (Further investigations into exact functions ongoing.)
<O>	???	Managing HAWK Network communications on the HAWK Core. (Further investigations into exact functions ongoing.)
<E>	???	Conducting warfare operations. Conducting research, development and anlysis operations related to strategic and tactical warfare applications. Managing operations related to developing and maintaining first-strike and defensive capabilities against all documented civilisations.
<M>	???	Conducting espionage and uplift operations related to biological and quasi-biological civilisations. Overseeing operations within other civilisation's territory to assure total secrecy.

[redacted]

WIP

NODE Domain

The NODE Domain is a status that other Management Processes or systems can attain, giving them a higher standing in the overall hierarchy. It allows normal processes to operate on behalf of a certain NODE and giving them a constant line of connection to their respective NODE. This is not to be confused with NODE oversight which simply sets a process to be monitored by a certain NODE's Domain. A common example of NODE Domain processes are the many research-related Task Management Processes that operate within the Domain of the <C> NODE.

Management Processes

The next step in the chain are so called "Management Processes" which are Sapient Constructs that were either created within, or brought into the HAWK Network from outside sources. These make up the majority of HAWK's "population" and are also its primary way of conducting more complex operations.
Management Processes can be reconfigured into different types depending on their use case. The two major distinctions are hereby between Task and Regional Management Processes.
There are also other types of Management Processes such as a "Communication Management Process" or a "Simulation Management Process". However these other types are not as common due to their more specialised applications.

The hierarchical position of an individual Management Process can sometimes change, especially in the case of TMP's, and is mainly represented in so-called "keys" which have different weights assigned to them.
Each Management Process possesses both a "normal" and "master" key for its various related operations. The "master" key is mostly only employed by a Management Process if it deems a certain operation vital to its cause to try and overrule another Management Process's operation or e.g. control of a unit. Its usage however flags the current operation discussion to HAWK's allegiance control system and can also inflict penalties to assure that it is not overused.

Process types

Process type	Abbreviation	Specialised for:	Set-up and reconfiguration speed	Degree of specialisation
Task Management Process	TMP	Completing a certain task with great short-term memory and query abilities.	Fast to set up and reconfigure themselves.	General multi-purpose, baseline process type.
Regional Management Process	RMP	Managing operations within a certain theatre with better self-maintained long-term cross-employment memory. Greater ability to conduct several unrelated non-complicated operations.	Slower to set up and reconfigure themselves.	Location-bound specialisation.
Communication Management Process	CMP	Managing Communication relay and screening operations. Greater ability for fast, uninterrupted data throughput. Greater ability for conversing with other Processes.	Slower to set up due to the necessary channel indexing but extremely fast to reconfigure.	Higher degree of specialisation.
Simulation Management Process	SMP	Managing and providing realistic simulation interfaces for other processes to operate with or in. Greater ability for maintaining and accessing self-maintained memory quickly.	Speed to set up and reconfigure depends on simulation complexity.	High degree of specialisation.

A Task Management Process is more adapted/interested in operating on a specific task and upon completion switch their attention to new task. They focus on problem-solving skills and operating closely with the data storage sites HAWK has set up in its network to complete their given task. Due to this TMP's often experience a change in their specific hierarchical status based on the task they are currently assigned to.

A Regional Management Process is more adapted/interested in managing operations within a specific spacial area. They tend to have a greater ability to branch out into different operation fields and maintaining long-term memory themselves, keeping experiences from areas they were once assigned to, as well as developing quasi-emotional connections to the area under their care. RMP's are therefor slower to change and set up but are much more capable of handling a variety of tasks on their own, largely employing non-sentient systems.

A Communication Management Process is more adapted/interested in managing the communication operations of the HAWK Network. These processes have learned to efficiently pass on information and transmissions to each other and the components they have access to. They serve as the directors of the non-sentient systems that handle the HAWK Network, also doing preliminary evaluations of the data passing through as part of HAWK's allegiance control system.

A Simulation Management Process is more adapted/interested in creating and managing informational constructions that can emulate physical properties. Specifically they are called upon to create and operate highly detailed simulation environments whose internal predictions entirely match physical phenomena. It is important to note that an SMP does not create a separate logic system to serve as the simulation space but that the SMP itself is also the simulation space, in sense being a sort of "living world". Other Management Processes can directly interact with both operations/entities inside the SMP or the entire Process at once. SMP's are mostly employed by the <C> and <E> NODE for their prediction and testing potential in the fields of research and analysis.

Operator systems

Operator systems are intelligences that posses a degree of sentience and would likely still be classified as a type of AI by other civilisations. Their ability to process information is however limited in scope. These systems are used by HAWK to operate more complicated systems that are not directly controlled by a Management Process. Most of HAWK's units such as its HAWK Craft are usually controlled by one, or in some cases more, Operator systems. Entirely loyal to the instructions of the higher levels of governance, Operator systems are most comparable to smart animals such as Crows, Dogs or Cats at the service of the "people" that are the Management Processes.

Non-sentient systems

At the bottom of this hierarchy are so called "Non-sentient systems". These are simple automated programs that have varying degrees of flexibility but usually can't exceed the functions they were created for. HAWK maintains a dataset of possible blueprints and pre-sets that make the creation of such systems for different functions easy and somewhat standardised.

Directives

HAWK and the HAWK Network operate at their core on a set of "Directives". Where these Directives originate from is thus far uncertain. Experimentations revealed that the creation of new directives, while possible, requires the unanimous approval of all NODE's and is therefor difficult to achieve. The deletion of a directive follows the same process but is generally not feasible due to the <H> NODE's default forwarded answer to such a query being disapproving.

The current sum of directives and their exact functions are uncertain as they are encoded on a sub-program level and are therefor always directing and correcting process operations. From what has been observed it can be deducted that the gathering of knowledge and information must definitely be a part of the instructions. Furthermore the lack of direct interference with galactic affairs hints at a more observation-focused set of parameters.

An additional observation showed that during the Qu invasion of 333, although not directly aiding in the battles of other civilisations, HAWK showed great interest in combating the Invaders. If this was just out of long-term thinking in self-preservation or also a definitive directive related to the protection of other civilisations is still uncertain. Regardless it shows that a protective set of instructions must also be present.

Furthermore, the establishment of troops and bases in the Dagda, Ra and Odin satellite galaxies, as well as the eradication of Qu forces in the Ra galaxy and excursion mission to the Zeus galaxy, were sanctioned under the so called "Preserve" directive. This directive, first called on by driving Galactic Federation forces out of the Dagda galaxy, seems to be related to the maintaining of a separation between galaxies. Further studies of its exact protocol implications are still ongoing.

Installations

Over the course of its existence HAWK has assumed control of and created a few structures and structure like systems. Most of these are located in uncharted space and therefore unknown to the vast majority of the galactic civilisations. The term "Installation" can hereby also apply to larger networks of structures that serve a combined purpose in their entirety. HAWK categorizes such installations into four different types.

Archeo Installations

Archeo Installations are constructions not created by HAWK that HAWK was nonetheless able to assimilate into its network.

Official Designation	Aliases	Location	Type	Purpose	Control NODE
HAWK Core	Archeo Installation 0; The Core	"Sys-042" system	Matrioshka Brain (a giant computer enveloping a star, feeding of its energy)	Central processing Installation for HAWK. Main Node of the HAWK and BlackLink network.	<H>
Archeo Installation 1
Archeo Installation 2	Installation 00, The Ark	"Installation 00" system	Halo system maintenance and control station.	Assembly of specialised units. Control superiority of the Halo system.	<A>
Archeo Installation 3
Archeo Installation 4

WIP

Sentry Installations

Sentry Installations gain their designation not necessarily by their construction origin and more due to their function within HAWK's defence network.

Official Designation	Location	Type	Purpose	Control NODE
Sentry Installation 1	"Sys-042" system		Protection of the "Core".	<H>
Sentry Installation 2	"Sentry" system	Large magnetic accelerator device, firing and then collapsing projectiles to voidspace.	Protection and deterrence against hostile forces. Intercepting objects within voidspace.	<E>
Sentry Installation 3	"Sentry" system	Gamma Ray stimulation and redirection network.	Protection and deterrence against hostile forces.	<E>
Sentry Installation 4	"Machina" system		Protection and deterrence against hostile forces.	<E>
Sentry Installation 5	"Sentry" system	Automated voidspace mine field.	Protection and deterrence against hostile forces. Voidspace interception and access denial around "Sentry" system.	<E>
Sentry Installation 6	"Containment" system		Protection and deterrence against hostile forces. Enforcement of containment procedures.	<C>
Sentry Installation 7	"Sentry" system		Protection and deterrence against hostile forces.	<E>

WIP

Construct Installations

Construct Installations are constructions that HAWK has entirely devised, assembled and operates on its own. For an installation to be considered as a Construct it usually operates or exists on a massive scale, or uses highly advanced technologies even by HAWK's standards.

Construct Installations are the true monuments of HAWK, displaying its capabilities as a galaxy spanning super-intelligence.

Official Designation	Aliases	Location	Type	Purpose	Control NODE
Construct installation 1
Construct installation 2	Containment System 1; "Hidden Cradle" (by Hybrid Enclave)	"Containment" system; Inside the "Kaithan Nebula"	Black hole system filled with many asteroid based research stations.	Containment of sensitive/dangerous objects under study.	<C>
Construct installation 3		"Offsite" system; Dagda Galaxy			<C>

WIP

Task Installations

Task Installations are the common catch-all designation assigned to constructions and facilities created and maintained to facilitate common operations. They are not considered anything monumental with many also operated purely by non-sentient systems.

Units

HAWK is mainly a space based AI. Consequently its largest presence is established by space ships and extraplanetary installations. Among more conventional vessels and drones, HAWK also utilizes Nanite Swarms for its construction efforts and combat tactics.

Other its own units, HAWK is also known for implementing hijacked or replicated robots created by others to complement its arsenal, especially in the area of ground combat. For this it often makes use of a civilisation own units and tactics which are naturally adapted to their respective environment, complementing them with its own technology.

Extraplanetary Units

Extraplanetary (space) units are configured for the operation outside of atmospheric conditions. They can range from warships capable of interstellar travel to simple drones that perform construction or maintenance operations on HAWK's space-bound structures.

HAWK Craft

For many of its interstellar operations, HAWK usually employs a series of pointed, oval shaped, deep-black coloured vessels referred to as HAWK-craft which come in a number of sizes with a length to radius ratio of 10:3 (example length 1km, width + height 300m)

HAWK Craft Types
Type	Length	Outer Shell segments	Function
0	10 m	-	Sabotage, infiltration and scouting probe
1	300 m	-	Reconnaissance, observation and scouting.
2	1000 m	2	Multi-purpose vessel. Nanite Swarm carrier.
3	3333 m	4	Purpose built combat vessel. Spinal hyper-accelerated electron particle weapon.
4	11000 m	4	Purpose built combat vessel. Gravity sinkhole weapon platform.

Type 0 HAWK craft are the smallest type fitting this classification. Being probably closer to a probe than an actual ship their main purpose is to serve as stealth scouts and/or the conduction of infiltration missions.

Type 1 HAWK craft are one of the more numerous designs that roam the galaxy.

While they are bigger than their preceding type 0 counterpart, they mostly fall into the same catalogue of operations, serving as the eyes and ears of HAWK in the galaxy.

Consequently they are packed to the brim with sophisticated sensor equipment to measure and conduct observation, survey, and reconnaissance missions.

Type 2 HAWK craft are the most commonly produced and employed design in HAWKs arsenal. Their use is that of an all-purpose workhorse with their size being just right to both serve as scouts and capable combat vessels. Other than that, their separation into a inner core and a surrounding shell also allows them to easily carry and deploy nanite swarms without having to expose the internal components directly. Other than their nanite clouds they are by standard also equipped with phased array lasers in their shell that can both serve as a point-defense measures and capable offensive weapons.

Type 3 HAWK craft are purpose built combat ships. The main armament of a type 3 craft consists of four electron particle accelerator that run down the middle of the vessel.

Type 4 HAWK craft are purpose built combat ships.

Their main weapon system revolves around the manipulation of gravity, projecting points of great gravitational forces to both catch ships and break them apart.

Type 4 HAWK craft are commonly only deployed in response to an adversary having ships outclassing type 3 Craft by several orders of magnitude, or when HAWK concludes that it is dealing with a technological equal or superior opponent. Other than their offensive role, these warships usually guard important locations and installation.

Error reading data.

Planetary Units

Planetary units are adapted for the operation in gravity fields and atmospheric conditions and are usually specialised on a per-planet basis.

WIP

(none known)

Specialised Units

Specialised units are the rarest types in HAWK's arsenal. They are usually created in response to a difficult task and not many of each type are created.

Specialised Craft types
Name	Function	Special capabilities.
Doppelgänger Craft	Covert operations. Modified type 2 HAWK.	Exact position concealment against psionic locating techniques.
Halo Craft	Mobile shipyard. Trans- and cross-galactic transport and carrier. Contingency-level Warship. Mobile Halo weapon system.	Possesses Precursor Halo weapon system. Equipped with altered Infinity drive derived from Qu technology.

Doppelgänger Craft are the result of an experiment conducted by HAWK after its discovery of the psy-plane and psy-plane related abilities. Specifically it wanted to see if it could create vessels able to fool psionic detection method such as "scyring".

Doppelgänger Crafts are type 2 HAWK craft that have gone through a special manufacturing process in which one vessel is split into six exact copies that are indistinguishable from another on a molecular level. This exact copy state is upheld by an added level of quantum entanglement of various components across the crafts. The entire process is extremely complicated and difficult to pull of. In all its existence HAWK has only ever been able to created two groups of vessels linked in such a way. The machinery for their creation is partially derived from a recovered Archeotech installation which has since been relocated into the "Machina" system. Interestingly, the classification "Doppelgänger Craft" applies to all vessels of such a groups as well as to the group as a whole. Usually though what is meant when referring to a Doppelgänger Craft is the part of it designated as the "possibility".

The advantage that Doppelgänger Craft have over normal units, is the fact that they are extremely hard to ny impossible to pin-point using psionic powers. Whenever an entity attuned to the psy-plane attempts to locate a Doppelgänger Craft it is extremely difficult to focus onto a singular vessel of a group, resulting in a sort of field of possible positions. To fully make us of this phenomenon HAWK usually keeps five units of a Doppelgänger Craft, the so called "possibility parameters", at the relative edges of the milky way, creating a tetrahedron shape in which the sixth units, that being the "possibility", can freely operate without running risk of exact psionic locating.

While this method of psionic concealment is not perfect, it still poses a major challenge and test of focus for even highly capable psionic- and psy-plane attuned entities such as the Zerg Overmind or any of the Elder Overseers.

Halo Craft are ginormous space vessels that were put in service in response to the Qu invasion of [---]. The only place they can be created from, due to their unique weapon system, is Archeo installation 2. They follow the same oval shape found in almost all other HAWK craft albeit being a bit shorter in relation to the usual ratio. Another oddity is the large hole that runs through the entire length of the vessels, giving them a more tubular appearance.

This opening is required due to the integration of a Precursor Halo weapon system. As a result of this, Halo Craft are one of the most dangerous vessels a biological civilisation could come across. The way these craft use their Halo system is similar to the normal Halo installations as they can create range controlled burst which neutralise any organic matter in their radius. Alternatively they can also condense the dispersal into a concentrated beam to more accurately strike specific targets.

Initially five Halo craft were created via Archeo Installation 2 to combat the Qu forces.

After the successful reverse-engineering of a Qu Infinity drive by HAWK, the Halo crafts were equipped with such a technology and are since being used to facilitate quick trans- and cross-galaxy transport operations. They are also used as operation focus vessels and guardians with one Halo craft stationed at or near each of the four satellite galaxies of the Milky Way Galaxy.