Ling's Project Log

[Mr.Ling]

...hack.initiated...connecting.to.Spyglass.Network...decryption.in.progress...
...Deceiver.Mr.Ling.recognized...encoding.transmission...
...uploading.data...

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.

Argonaut-3 Terminal

access: group_info: *Liberty Security Force ; *Kusari Office of Intelligence ; *Liberty Navy ; *Kusari Naval Forces{

group_info_SHORT: *LSF ; *KOI ; *LN ; *KNF
group_info_TOKENS namblocks: =Cipher-44 ; =LH~Ling.Ling ; =Cipher-9 ; =LNS-Arctic ; =[LN]-LNS-Constellation ;
group_info_TOKENS unreadable: 19
log_append Y/N: N

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."

setfunction: "Cold Lake Supergate" ∈ orbital335252_LI
setfunction: "Extract" ⊂ travel_functionFLEE ; travel_functionDEFEND ; travel_functionESCORT
setfunction: "IKN-Niyodo" ∈ object532344_EH

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.

Niyodo Hoshu Tanmatsu

conduit_preset:

:end_preset

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.

End log.

...encryption.in.progress...disconnecting.from.network...hack.terminated...