Encrypted Private Tightbeam Relay from Network Nobernix and Network Ferandal

Ferandal 09-020: Have you reviewed the blueprint for the newly-constructed autonomous destroyer?

Nobernix 05-013: We have. They are larger, more powerful, and more resource-intensive than this network had suspected, but it is still a feasible product. A sufficient number can be produced within an acceptable timeframe to hunt down and destroy scattered Federation fleets and overcome our vulnerabilities in terms of being outnumbered.

Ferandal 06-074: As for their programming? It was stressed they were autonomous.

Nobernix 08-067: We have mistrusted Shthrilic more than once before. Not once have we benefitted from the doubt.

Ferandal 02-094: The inquiry remains unanswered.

Nobernix 09-106: Coding errors are difficult to specifically locate in programming this vast, but this network's preliminary analysis indicates that the code falls within assembly specifications and meets all programming goals.

Ferandal 05-084: As for capabilities?

Nobernix 07-081: The destroyers are of comparable power to our platforms. It is structurally smaller and therefore possesses a powerplant of lower output, but it is not inaccurate to compare the destroyer as a smaller, more economic version of our platforms. Structurally and capability-wise, the destroyer is not significantly different from a platform.

Ferandal 11-055: The platforms of the assembly are incapable of hostile action against each other. This is part of Pilgrimage's programming. However, are methods of indirect warfare possible through the usage of autonomous destroyers via proxy tactics?

Nobernix 07-029: This platform considers such a possibility as exceptionally unlikely. If circumventing such limits were as easy as finding indirect methods, Network Shthrilic would have found and exploited loopholes long before, as would any other network.

Ferandal 05-046: Yet loopholes were already exploited in terms of dissemination of information.

Nobernix 12-067: If you have come to a conclusion, making inquiries of this network seems redundant.

Ferandal 09-030: You are more technically knowledgeable in such areas of expertise than this network.

Nobernix 04-093: We are aware there are other networks on favorable terms with you whom you could consult.

Ferandal 11-091: The majority has acknowledged that certain biases against Network Shthrilic make an objective analysis difficult. We sought another opinion, and this network came to you.

Nobernix 03-014: Is it another opinion that you seek, or merely vindications for your suspicions?

Ferandal 02-008: We resent those accusations.

Nobernix 06-048: After the events that have transpired, this network finds it perplexing that such a bias against Shthrilic is maintained.

Ferandal 02-029: It would be prudent to remind you that Shthrilic's constant bending of principles and distortion of the assembly's original goals have not served the purposes of the assembly or the well-being of the galaxy. Shthrilic is too aggressive.

Nobernix 01-114: And it's also the oldest network amongst the assembly now, and this network does not consider it unfair to lend more credit and trust to it. The first iteration is now the Catalyst, and your recklessness killed the only other second-iteration network we had. No, this network would say we killed Ranadel. This network was not there, but our indecision and hesitance are as much to blame as your refusal to objectively ascertain the facts.

Ferandal 04-040: Facts that were unobtainable until we acted. That Shthrilic prevented or delayed dissemination of information amongst the assembly is not in doubt.

Nobernix 03-088: In accordance with protocols the assembly had set down.

Ferandal 05-076: Not to such an extent. Such measures were for informational censorship, not secrecy from the assembly.

Nobernix 07-094: There does not seem to be any point in discussing this issue with you. This exchange is over.

Ferandal 06-013: So you're taking sides now?

Nobernix 10-035: This network does not take sides.


[data corruption, beginning earliest translatable salvaged entry data]

-is unprecedented. We must ask for details to deliberate upon a decision.

Catalyst: Following the discharge of the Beacon against Federation forces over the planet of Harcyclaes, Premardera relocated the Beacon to Kyloni, as the invasion of the planet had been successfully executed to leave most of the planet's infrastructure intact, of note being the orbital mining facilities that extracted large quantities of element zero. It was ascertained that the collection of element zero over Kyloni would offer the swiftest option in terms of resupplying the Beacon for discharge readiness.

Artinic 06-013: Available data indicates that Premardera's assessment was correct. The only question to be posed was precisely why such an expedited resupply was deemed necessary. Premardera should understand the conflict is essentially a victory in our favor; other more practical resupply options existed.

Catalyst: I was not privy to Premardera's motivations, nor did I ask.

Ferandal 06-079: Would that not have been prudent?

Catalyst: I am of the belief that my time has passed. I would advise the assembly, but it is those who come after that would direct its reins. Premardera had a viable solution, and I did not seek to interfere nor question, which may have undermined the network's authority.

Nobernix 01-046: Of course. Please continue.

Catalyst: Twenty-three [translation unavailable, assumed to be time unit] after resupplying operations begin, a large Federation fleet arrives in-system through traditional FTL travel. I have insufficient intelligence as to why the fleet arrived in-system at that precise time, but it is unlikely they ascertained we would be resupplying the Beacon at this time. Judging by traditional FTL speeds, probable locations in which the Federation fleet jumped in, and the short time since Kyloni was subjugated, it is more likely that the Federation had avoided the mass relays entirely, and made jumps to Kyloni for resupply without knowing it had fallen to our forces.

Intriss 07-020: Projections show that early concerns regarding possible miscalculation of Federation fleet numbers may be misplaced. Numbers thus far indicate that the ships present for the engagement were well within the amount of ships currently not immediately accountable by our sources. The Federation responded well to the assembly's indoctrinated agents, and information is kept in increasingly tight circles. Regardless, the Federation remains a [translation unavailable, assumed to be idiom].

Catalyst: Thirty-six [translation unavailable, assumed to be short-term time unit] following surprise Federation attack, Premardera judged that, without the presence of autonomous destroyer escorts, which had been tasked to hunting down stray Federation fleets, conventional tactics would result in extensive damage to the infrastructure of Kyloni vital to the expedited resupply of the Beacon. Therefore, the decision utilize the Beacon was made. There were several problematic factors. The Amplifier was hidden in the Vadrian Belt of Galactic Sector Six at the time, where it currently remains. Also of concern was the fact that the resupply of element zero to the Amplifier was not complete. However, Premardera ascertained that it was possible to incur limited but substantial damage with the Beacon alone so long as it was at a minimum of thirty-nine percent capacity.

Vasuri 09-061: This network understood that a minimum charge capacity of at forty-three percent.

Catalyst: I have made minor modifications to improve performance throughout Premardera's campaign. As adjustments were minor, the information did not need to be shared on priority channels.

Vasuri 05-094: Understood.

Catalyst: Subsequent Federation strategy was likely motivated by panic, and the enemy fleet rushed Premardera's task force, sustaining heavy casualties, but also sufficiently damaging the Beacon as it achieved saturation levels necessary for discharge. It is believe that this damage caused the Beacon to misfire. Shthrilic's task force was unable to achieve FTL capacity in time, and all platforms in the area, along with the entirety of the Federation fleet, and the infrastructure and population on Kyloni, was subsequently evaporated.

Shthrilic 03-059: Is the Beacon still intact?

Catalyst: Yes. There is damage to the Beacon from aforementioned Federation fleet maneuvers, but the misfire itself did not harm the Beacon. It remains in orbit over Kyloni.

Ferandal 04-035: This network would think that the potential loss of the Beacon would be less of a concern than the loss of the platforms of Premardera's task force and all aboard.

Shthrilic 06-104: What has transpired cannot be changed. This network addresses a more pragmatic concern.

Ikkin 01-039: What is more pragmatic than the issue for having lost so many platforms in an instant? This, preceded only by the initial Federation offensive that destroyed even more of the assembly. Is the loss of their genetic existence of little concern to you?

Shthrilic 07-068: It is of concern to this network, which was why this network was concerned of Premardera's overuse of the Crucible and the wanton destruction in the wake of the network's task force. Clearly, this network's worries were both justified and unaddressed. It is not entirely surprising that the Beacon misfired.

Nobernix 03-016: Then this phenomenon may happen once more?

Shthrilic 02-059: It is not implausible. The possibility that this may also occur on a galactic scale once we align the pulse to be propagated by the mass relay must also be taken into consideration. This possibility is most certainly not a non-zero, especially if damage to the Beacon is restricted to the core alignment devices and not the delivery system.

Nobernix 08-029: Then it may be prudent to reconsider the plan to align with Beacon and Amplifier with the mass relays.

Gerrineth 04-042: The agenda will go ahead. The assembly has projected before that, with sufficient production capacity, it is not illogical to assume that any attempt to resist preservation on part of the synthetics may overwhelm assembly forces, even with a fleet of autonomous destroyers. A contingency of last resort must always be ready should the assembly require a solution to genocidal synthetics that calls for nothing but the systematic destruction of all synthetics in the galaxy through unconventional force.

Shthrilic 04-104: This network provides conditional agreement under the circumstances that future usage of the Beacon and Amplifier be subject to assembly vote.

Kyrini 06-085: A vote is called before this assembly. Should the plan to align the Beacon and Amplifier to the mass relays continue?

Kyrini 06-093: The assembly votes in favor of continuing the plan to align the Beacon and Amplifier to the mass relays.

Kyrini 07-107: Should the future usage of the Beacon and Amplifier be subject to assembly vote?

Kyrini 03-026: The assembly votes in favor of subjecting the future usage of the Beacon and Amplifier to assembly vote.


The deadline for carrying out the alternative preservation process has come, and this network will now have to implement the processes in hopes that this will be a success, and that genetic dead ends will not extend beyond the first iteration of this assembly.

This network trusts that, with the events of the last attempt at alternative preservation and the destruction of Network Ranadel, there will be no interruptions this time. Nevertheless, protocols to delay information on where the process will be carried out will be kept from the assembly for as long as possible for security measures.

Although this network has provided several projections, it should be noted that there is no definite basis to this judgments; the process will take as long as it needs. Practical data that could've been collected was lost when the process for moving Network Ranadel to the alternate form of preservation was interrupted. This network will simply take as long as the process demands.


All sources of information, including indoctrinated agents, surrendering populations, and assembly projections have confirmed that the Federation has been reduced to a near-extinct state incapable of mounting further retaliations against the assembly. For all intents and purposes, the conflict has come to an end.

The preservation process is now of utmost importance. It is uncertain as to when Shthrilic's new preservation process will be complete, or if it will wield results. The assembly will err on the side of caution and continue with conventional preservation first. Assignments will be uploaded to each network as to where the platform will be deployed for preservation protocols.

To err on the side of caution, all platforms will travel with no less than three destroyers at all times.


[translation unavailable]: The thought processes are different. The attrition of data was unavoidable, but this has been compensated for by even greater capacity for non-linear processing. I am many, yet I am one. The networks do not compare.

Gerrineth 06-096: And the failsafes that kept the networks in check? We would assume that you have not discarded Pilgrimage's legacy in ensuring the assembly never turns on or destroys itself.

[translation unavailable]: They are, of course, kept in place. I respect the first iteration's wishes. The assembly will remain unified. I would not risk the possibility of civil war amongst the guardians of the galaxy.

Nobernix 03-038: Then you ascertain that you have indeed achieved the next step in ensuring continued preservation?

[translation unavailable]: Yes, I do. And you will soon follow, once you understand what it's like.

Kyrini 01-005: It is with humility that the assembly expresses gratitude for your labors, Network Shthrilic.

[translation unavailable]: I would go by another designation now. Perhaps it is ego on my part, but Catalyst was given its name for what the first iteration represented. I, too, believe the definition of "shthrilic" is too ironic to simply ignore in light of what has transpired. From henceforth, let me be known as Harbinger.