Transmission received
Code recognised as A-230-951-KUCOM
Decrypting.... Recipient:Naval Operations Headquarters Sender:Itto Kaisa Kiriyama Haruki Date:20.01.835 AS Subject:After Action Report - Jump Drive Expedition Priority:High
As part of a mission to test our capabilities with the experimental jump drive technology, the IKN Harukaze took part in an expedition using Tohoku as the main staging point. We were instructed to not divulge any information to personnel not of Gold Class clearance about our destination. The primary goal was to secure and retrieve the long-lost IKN Niyodo back into Kusari.
Unfortunately, intelligence reports have uncovered Liberty's motives for the Niyodo. Fortunately, our fleet arrived just in time, but not upon learning the existence of a heavy lifter called "Argonaut-3". After analysis was done, our priority soon changed to retrieving the lifter back to Kusari for analysis. We were prepared for a possible conflict with Liberty, however they brought a whole fleet determined to secure the ship in their hands.
While we suffered numerous losses attempting to retrieve the Argonaut, it jumped to Kepler, where we faced an unexpected threat in the form of Lane Hackers. With most of our fleet battered from Liberty's unprovoked attack, they forced us to retreat to Shikoku, where the IKN Harukaze is undergoing repairs for the time being. Reinforcements sent into the border were sufficient to deal with a surprise Liberty attack in Galileo. Eventually, the Argonaut was last seen headed to Liberty, but further intelligence shows that the Hackers were in control of it.
Though the end result was quite unfortunate for our side, we are fortunate Liberty has not seized the Argonaut for their own purposes. In the meantime, I recommend increasing border security in case a future war breaks out between Kusari and Liberty.
Transmission received
Code recognised as NT-X49a-NOH-DirexC-9310
Decrypting.... Recipient:Naval Operations Headquarters Sender:Santo Kaisa Mizui Naruhito Date:06.10.835 A.S. Subject:IKN-Numazu Priority:High
Sixty-Sixth's Itsumaden reporting in. I bring terrible news.
Following proximity alerts of a large warship near Heaven's Gate, a standard sweep was conducted. The wreckage of the IKN-Numazu was located slowly drifting towards the Izu Field, seemingly destroyed in battle with either Order or Dragon forces.
Ichigaya and the Arch report no communications or calls for aid by the vessel, albeit they were able to confirm it was scheduled to arrive at Ichigaya later today. A local KOI contingent and Ichigaya's salvage wing are already about tow the remnants to the drydocks. They have requested from me to inquiry about the possibility of utilizing the wreck for one of their next experiments. Personally, I would say that we let them. The near magical results of the past years make me believe that they will find better use for the wreckage than salvaging it at Yokohama.
Apologize me overstepping the ranking order, but I urge the NOH and command to facilitate new standard routines given the frequency of assaults surrounding the Arch and our current distraction due to Liberty's foolish games. The Sixty-Sixth will remain at the Arch to assist the KOI in repelling hostile incursions, but we are unable to muster the amount of warships that may be required for this task. We are spreading our forces thin but we cannot falter.
In service of Kusari, Santo Kaisa Mizui Naruhito
66th Tokubetsu ensei-ka
Transmission received
Code recognised as NT-X49a-NOH-DirexC-Alpha-129cO
Decrypting.... Recipient:NOH Sender:Shido Kijima, NOH Date:21.02.836 A.S. Subject:Hiratsuka's Last Will Priority:Low
For documentation purposes only as explicit wish of the deceased.
Name of the deceased: Issei Hiratsuka
Rank: Santo Kaisa
Assigned to: S-NGD, IKN-Myoko
Main assignment: Squadron leader of the 2nd Ryusei training wing
Last assignment: Unannounced check-up on modular installations in Galileo
Cause of death: Suffocation
Further, the circumstances which led to his untimely demise as documented by Hiratsuka-san during his final hours:
[23:50 Sirian Time] Roughly three hours. The pod suddenly started to signal falling pressure in two of the three oxygen tanks around an hour ago. Unless a patrol finds me out here soon, I think this is it. I had a good run, twelve years. Just three more to go. I ponder why a Dragon pack leader is in Galileo but it is too late to wonder now. We'll meet in hell, Neshoen Clan member, and then I'll have my answers.
To whoever retrieves this pod, I merely ask for you to get me home to Planet Junyo so that my wife can hold a proper burial.
To my commander, please inform my colleagues about my fate. I haven't seen many of them in recent years but I believe they deserve to know.
[1:37 Sirian Time] In ever lasting service to Kusari's people, Santo Kaisa Hiratsuka Issei.
Hiratsuka's escape pod was retrieved at 4:56 Sirian Standard Time by a KOI patrol in vicinity of the modular installation called "SpaceTech Station". By the time of retrieval, oxygen supplies were already depleted since at least three hours. The escape pod was in terrible shape, first investigations draw the conclusion that the pod was damaged as a consequence of the fire fight, yet the oxygen supplies were intact. This suggests a later, deliberate and cruel execution of Hiratsuka-san by an unknown third party. Such cruelty is inacceptable and the S-NGD is already drawing possible reactions should this mark the beginning of a new trend.
The burial will be held at the Sotome Shrine on Planet Junyo. For his outstanding, long time service with no faults and his courage to stand up against an enemy few would dare to face alone, Hiratsuka will be awarded the Order of the Rising Sun during the ceremony.
In service of Kusari, Shido Kijima
Naval Operations Headquarters
Transmission received
Code recognised as NT-NOH-DirectL-0923-RpE3
Decrypting.... Recipient:NOH Sender:Goryō
Subject:Situation Debrief
The border situation deteriorates further with every passing week.
Responding to the emergency call of the IKN-Tsushima, a small wing of fightercrafts led by myself arrived to Galileo.
We were met with a small token force of Liberty Navy vessels loudly arguing with a sizable Zoner convoy carrying Iridium, which passed by ourselves a little earlier.
This scene took place straight at our border, next to the Shikoku Gate. Following a brief heated exchange during which the Zoners almost settled on carving their path through with violence, they returned back to Kusari space.
Not long after, a Liberty Siege Cruiser bearing LPI identification codes emerged from the Shikoku Gate. A lengthy conversation emerged, which threw so many waves that eventually the Fleet Admiral of the Navy's First Fleet made an appearance. Following a debrief, she classified the Siege Cruiser a containment breach and folded to our pressure to let us scuttle the vessel to ensure a proper data wipe. Concerningly, they insisted on an evacuation effort of the crew they themselves marked as infectees. Due to this circumstance, we must assume that either this vessel was a deliberate test of our borders integrity or that the Republic attempts to handle living thralls through the LSF. Both options are extremely concerning and must be taken into consideration for our future steps. I insist on a KOI led investigation in the near future.
Following the scuttling of the Siege Cruiser, plenty more unlawful contacts than the few who "enjoyed the show" earlier. A skirmish was inevitable and Liberty's forces, whilst some were disgruntled by the fact, accepted an order given to join forces to deter criminal elements. It didn't go as planned, at all, apparently. Seeing the increase of maintenance listings and the dispatchment of towing vessels from the Tsukishima Yards. Oh and I need someone to check the old warehouses. I need a new Tora-class now, this is non-negotiable.
As you are all aware, tragedy struck a while ago when Lane Hacker affiliates leaked incomplete schemata of the Kishiro Jump Drive Project as a consequence of Liberty's interference during the IKN-Niyodo retrieval. Ranging from our politicians to Kishiro's experts, everyone kept on stressing the risks attached to these uncontrolled, incomplete leaks and any devices constructed based upon them. Our estimates saw that such devices will require at minimum a year of highly dangerous trial and error by third parties prior to a "functional" third party device appearing.
A vessel utilizing a device clearly belonging into the "trial and error" phase was spotted and subsequently dismantled upon my orders within New Tokyo today.
The ZDF-Hinaichigo, a Zoner operated Crayterian Battlecruiser holding Approval by the Ministry of Economy for passage, attempted to activate a potentially highly dangerous volatile Drive knock-off in orbit of New Tokyo itself at 21:45:26 Sirian Standard Time.
Prior to issuing orders for its destruction, we probed the situation a bit and revealed a few interesting details:
The Zoner Community in the Omicrons constructed and subsequently sold the device on Freeport 11 to this self-identified 'Research Vessel' - We urge the KOI to investigate this lead immediately.
The Captain, one Kashiwaba Tomoe, of the vessel did not understand the risks attached and described the devices usage as "unreliable but a nice party trick".
According to the Captain, the device utilized by this vessel allegedly suffered from graviton wave emissions which they attempted to counter-act through additional shielding. The immense collateral its activation in New Tokyo's orbit could've caused showcases that we need to tighten our regulations and show no mercy to fools playing with technology they do not understand in the slightest. We may have just avoided millions of casualties by pure chance.
Following the vessels dismantling efforts, carried out to a large part by the auxiliary fleet vessel IKN-Yamaguchi, a sample of the fuel batteries in use by the Zoner vessel could be retrieved. They're being sent to Ichigaya for further studies. Due to the severity of the incident, we will inquiry with the Defence Ministry and the Ministry of Economy to immediately revoke this "Zoner Defence Forces" group's permission to transit Kusari territory in capital-class vessels.
In light of these developments, this report acts as debrief to all forces regarding future amendments. Coordination with the KOI and feedback from Kishiro is still pending, but it is crystal clear that we need to take a harsher stance against illicit Drive copies much sooner than anticipated.
Any vessel in possession of a Jump Drive not explicitly belonging to the Keiretsu, Naval Forces, KOI or listed distinctively in the License Database is a valid target and marked for immediate disposal when encountered within Kusari sovereign territory. The Admiralty advocates for the KOI to target vessels operating with Drive copies far beyond Kusari territory in an effort to mitigate the catastrophic risks the usage of these unstable devices represents.
In humble service of His Imperial Majesty, Okamoto Goro
Kaigun Gensui
1st Major Fleet: Matsumoto