Project Outline:Dissect and analyze captured Kusari Battlecruiser Wreckage Note: First step is to pull and backup whatever data I can from the wreck and from the Argonaut. I briefly ran a remote access on the Argonaut before it left Kepler, using Ames' distress signals as a carrier. I wiped the comms data, but I didn't wipe the actual access token, and since the Liberty Navy tried to order a self-destruct on it, the Liberty Navy also have an access token on the system.
list_target: missionOBJ: "Enter Earhart through Cold Lake Supergate. Incise and attach IKN-Niyodo to central lifting arms. Extract through Tau-23. Return to Juneau Shipyard."
Note: Sure enough, access token. I pulled a lot of preset definitions on Earhart, the end destination of the Supergate. Seems there's a lot of individual "objects" in Earhart. Also got a name for this wreckage, the IKN-Niyodo. Speaking of, what Liberty was after was probably this powercore, or whatever it powered.
Note: Yeah this was horrible. It reads roughly the same as some of the old Jump Hole theories, but there's pretty significant differences. What it does give me, though, is a single point at origin if I have the Mactan decoder solve it. Which means whatever it is is an actual thing that we can look for. If I get cleared for higher level Network Access, I'll roll out an update to set our scanners to passively search for anything that matches these energy output equations. Any Minified Spyglass Scanner or Spyglass Network Scanner that's up to date should give me data kickbacks if they can find whatever this math describes.
Project, Cont.:Further Investigation Note: We need eyes on the Supergate somehow. Hell of a tall order. The Nyodo's reactor maintenance machine kept track of how the reactor was outputting energy, and gave me a monster of an equation. It looks like a lot of things, but most of all it kind of looks like a messed-up Jump Hole. Once I get higher access, I'll set the Spyglass Network to hunt out anything that matches these equations.
The Argonaut's onboard system is pretty damaged, but I was able to pull a mission description and some definitions. Liberty went in there to hunt out the Niyodo, and Kusari came to stop them. I don't have anything positive on how they're exiting the system, but there's designated exits that are set to confirm when observed. So, quantum jumpgates. Needs an active observer to decide where they're going. I dunno. The more I think about how the machine was supposed to carry out its mission, the more pissed I get. Whatever Liberty Navy is doing, it's unoptimized and they're bad at it.
Project Outline:Analyze Argonaut-3 Wreckage Note: Pulling a light skim for anything relevant I can get out of this Liberty Navy token. After that, I'm probably going to have to go find an access token from an LSF. That's not going to be fun.
group_info access_LN->setmission: = "Defend the Argonaut-3";
group_info access_LN->setmission: = "Escort the Argonaut-3 to Alaska";
route_set(&group_info access_LN->priority, 1); Alaska , Earhart , Tau23 , Kepler , Colorado , Ontario , station_UNKNOWN
if (command = setaccess : ≤1)
group_info = access_LN;
return { "Access Denied"
mod group_info = *First Fleet , *1st , [LN]
return { "Access Denied, loser. Go get your clearance up, not your interference up."
}
}
return unit: group_info , open_page;
Note: Nice to see the LSF versus LN friction is still going strong. I can see the point where Cypher Team's code injection took over the navigation system. Also can see that the operation didn't go as planned. The route was expected to go through Tau-23, and ended up in Kepler unintentionally. Getting anything useful out of this thing is going to require higher access, though, I probably need to shoot down one of the LSF pilots that was there and snag some temporary login keys from their ship.
Project Requirement:Obtain an Access Token or Access Credentials from an LSF Pilot that was present at the engagement.
Project Outline:Niyodo Terminal Update Note: The brute force from the Mactan Network got something out of the Niyodo. Ten months, hell of a lot faster than I thought it would. Too bad cracking open the data killed my soul. It's Kruskal–Szekeres tunneling. Kusari's new toy is a significant sin against the fabric of spacetime, and is nothing like Ageira jump gates and is only marginally related to the bootleg jump drives seen kicking around Sirius these days. Instead of a swirl of subspace like Jump Gates and Jump Holes are, and a forceful punch into subspace like the average jump drive, these things are directly shredding spacetime at their location and stitching it to spacetime in another location.
These numbers suggest that the Region III problem that, you know, threatened spacetime paradoxes to tear apart the fabric of reality just... don't exist? Or, rather, they have a physical coordinate that is labeled with "danger" reports and a combat emergency response. Which suddenly makes sense with the Cold Lake gate "√-1 space" calculation, and the Argonaut's pathing response. This paradox space is a real place filled with enemy guns. That's horrible to think about.
That nonsense aside, this is a disaster case in every meaning of the phrase. Kruskal–Szekeres based wormholes always had theoretical limits due to the parabola defined by the Schwarzschild radius. These calculations don't have that. The singularity wall is just a pair of parallel lines. A door. All they would need is a machine putting enough energy into the entrance point, and one putting enough energy into the exit point, and they have a deploy-anywhere hassle-free Jump Gate that they can just... drop a fleet through. And getting the machine there is a case of just using the drive to jump there. If these calculations hold any kind of truth, which they obviously do because all of this came from Liberty and Kusari fighting using Cold Lake tech at the very least, Kusari is on the verge of bringing an absolute end to positional warfare. Blockades, ambushes, defensive lines, they'll all just cease to have meaning because you can instantly fly your full fleet to the enemy's capital.
Project, Cont.:Disaster Preparation Note: Who the hell do I tell about this? How would I even begin to run experiments on this? Should anyone ever run experiments that threaten the fabric of reality? Well, obviously Kusari did, I suppose that's a foregone conclusion.
I've done my research on the Technocracy and Sapphire Raven. I can't trust any single one of them farther than I can shoot them. Rogues wouldn't know what to do with it besides make a jury-rigged prototype and slap a price tag on it, and it's not like Hemlocke is kicking around anymore to keep them from shredding their molecular structure into quantum nothingness. The Outcasts would want something that can be used, and frankly I don't think this is usable. De Marco would just hand it over to the Xenos, Lovelace probably would too given the Ontario business. Order never gave me a clear answer about those Liberty Bastets, so they're probably in bed with each other.
Kusari has the key to Sirius-domination, I've snagged the spare from under the doormat, and I don't see an ally we can reasonably trust with this. Damnit, how much would it cost to force every Rogue to get a doctorate in Hyperspace Research?
I'm backing up all the calculations I've pulled thus far through the Mactan Network to Amarillo Base. If there comes a time where we need to build something that uses these equations, the data will be on both of our drydocks. I'm also releasing a patch for the active Spyglass Scanners to check subspace pings for the readings these calculations should be giving us. At the very least, we'll have an early warning system for when Kusari uses these things.
I hope wifey made mac and cheese, I'm going to need it after this.