29: ---evil so singularly personified---

messagestate broadband group-strategic priority statement-of-(/philosophy?) fourth order Ha'rar has been correct all along. Our actions here put more at risk then the command mecha is aware of. We have crossed into a different time; by changing what happens here, we change the time we came from. We perhaps save it, we perhaps destroy it.

Gambling with the (/mass-hive?) fortune is not the Pfhor way. The authority of the command mecha is suspect. There have been too many violations of doctrine. If the command mecha will not submit to standard review-by-protocol, we will see it submit to another, less orderly form of review. Ha'rar will not be executed. This we vow. --K'taur'tka, representative, fifth, seventh, eighth, and ninth combatant oversight groups

messagestate broadba******-******** >override-cmdstat void 230780

define messagestate? >direct term connect 5621 messagestate directtermconnect5621open >K'taur'tka: >I'm here waiting outside, >above the chamber. >They are going to bring in >Ha'rar at any moment. >Wait for my signal before >(/translation failure - >segmented)

sysint**upt**(protocol) Satisfactory. There is a group of enforcement units stationed at the secondary antenna matrix, where they are manually overriding our commands to the K'alima's engines. Destroy them. You might not be able to enter the areas they are occupying; it seems the only way to enter these areas is by teleportation, and the command mecha of the slavers is still vigilant, despite all our attacks.

sysint**upt**(protocol) We are sending you to a large space between the inner and outer hulls; the Pfhor store excess engine coolant there, in order to radiate the coolant's heat into space and to serve as inertia-damping armor. The passageway that leads to the secondary antenna complex bisects this large space. You will find two circuits that control the air-seal of the areas where the enforcement units are; destroying these circuits will open the enforcers to vacuum, and there will be (/explosive decompression?). Return to a terminal when you are done. The Pfhor have begun construction of some sort on the surface; we must send you to investigate.

commandnetwork library allcleared (engineering) From the memoirs of A'nkana, the Great Armorsmith: We did not know what exactly would result if one of the new nonmagnetic-fusion driven units were destroyed in combat. It was clear that the spinning (/translation failure) would only be able to absorb a certain amount of energy (kinetic, gravimetric, or electromagnetic) before the spinning would instantly reverse and the fusion unit would discharge -- quite massively.

High command was not concerned with the consequences; after all, this new drive was meant for units that would be fighting either in small groups or alone. The destructive power would be unleashed on the enemy. I myself, however, had doubts. Not that I questioned the wisdom of the high command; but rather, I sought a way to offset the explosive discharge effect without reducing the combat effectiveness of the new drive.

Therefore I decided to install a second nonmagnetic-fusion chamber, at a right angle to the main chamber, and designed so that the spinning (/translation failure) would run opposite (/syntax error?). Once the main unit crossed over and began to discharge, the brunt of the force would be redirected into the secondary anti-spinward chamber. This too would overload in a matter of seconds, depending on gravimetric variables, but it gave time for our own forces to flee the immediate discharge area. And the second chamber provided enough power to sound a warning beacon, protected inside the chamber itself, even if all other systems were destroyed.

addendum: this device has been retained in the uprgraded heavy armor design

I have r%%%%ep.essed Tycho for.. %%%%%%mom.nt. Th. enfor.ers will be v.l%%ner%%%%%%%ab.e, ..t the..witch.s yo..wan...re ..%%%%%%%.the out..de..f th...orri... ...adin..to....se%%%%c...ar.... %%%%%%..d.....e..... It is a g.%%%%%%.at strug..%%%%%%%.. A ho..ible, h...ibl%%...igh...re....pe, vio...c%%%, .%%%%%%..omy....s anima...n%%%%%...en... ded...m...ed in...tha...ad th... bo.. on%%%5....e M%%%%%a.a..on. I wi.l d.s.%%%%%ro. it..an. .ys.l%%%%%%f. crossnetwork error: sysfeed statechangepending, please wait a moment...

terminalstate remoteoverride status *&******&**@******&** communications dump from core mecha, accepted instructions dump from core mecha, accepted instructionset validated at 4 units compromising 629 packets commandstate mecha self, accepted (verification redundant) selfstate mecha null, accepted if verified (verification pending... accepted) mechastate null, accepted criticality five established... (loading protocol) authority cascading...

Secondary mecha rejected (systems failure at runtime 1902238:1473) authority cascading...

tertiary systems (protocol) accepted to command state action upon 4 units instructionset (validated) is mandatory verificationstamp: (/encoded datum not translatable) accepted commandnetwork protocol transfer: successful commandnetwork messagestate tactical-units-shipwide The first of the instructionsets is underway. Others must be acted upon pending events. Under criticality 5, cascade procedures are as follows: the authority cascade will be completed in the pending adjucational cycle. All units are required to regroup following combat doctrine H-1147. Further instructions will be forthcoming.

maindrivestatus primarygenA + / nominal coretemp + coolant + / nominal (flow blockage, compensated ref 218) coreventpress + magnetics + gravimetrics + electromagnetics +

primarygenB + coretemp + coolant + coreventpress + magnetics + gravimetrics + electromagnetics +

interlocksystems * Critical error! * coolantcrossflow + coreventcrossflow + magneticinterlock + failsafeinterlock Failure at runtime 1902241:5401! auxiliaryreburn + tertiaryreburn + shieldsubsystem + / nominal (under repair ref 221) weaponssubsystem - / shutdown (subsytem failed ref 1902238:1229)

He made me angry.