»route.nn: "Crucible"

[Geno]

EFUSE MACHID STATUS: ONLINE
NEURAL UPLINK: ONLINE
CONNECTION STATUS: ONLINE
ENTRY POINT: H7 MASTERDECK (STATUS: □︎■︎●︎♓︎■︎♏︎)
VERIFYING CHECKSUM... OK
MASTERDECK START ATTR = 0X1273000
FLAT DEVICE TREE START ADDR = 0X12B1E800
LEN1 = 0X3EE800
LEN2 = 0X43F980
MAGIC = 0XEDFE00
EFUSE MACHID IS NOT SET.
USING MACHID 0XF81000 FROM CLOUD STORED BACKUP
DEVICE TREE MASTERDECK/PRF_RESERVED_END
RELOCATING RIGID DEVICE POSDISK 1
LOADING POSDISK 1 TO 05008000... OK

USER ID: LAZURITH
transmission point of origin: INVERNESS
currently connected to: ⧫︎♒︎□︎◆︎♑︎♒︎⧫︎⬧︎relay

⚠ Executing autoencrypt.bxt script - 11.32 MiB
⚠ Executing autoburner.cmrd script - 812.34 MiB
Securing encryption through designated parameters...
Pinging designated relays...

⚠ AUG-O-LE00 connection established.
Transmitting visual data...

// FILE INFORMATION: \\
File name: Let's get this over with
File size: NaN: MiB
File type: Visual recording, including (0) attachments

---

Hey.

I've only just realized that the dire situation Valravn is in might be in need of being addressed soon. To this end, I'll be at your side to get the project done. As per... mmh. Can we even call it an agreement? I guess it's just me doing my part, at this point.

Let's get down to brass tacks. You're my project leader, and I'll-- what's my role, here, even. Supervisor? Advisor to a Supervisor? Blue shirt? (Please don't make me work as a blue shirt, or I'll just pack my bags and leave. As much as I like those guys for carrying the entire project on their backs, I am just not built for heavy lifting. I'd rather leave that to the cranes and the heavy loader units.) Nevertheless - these are my demands. If I am to put some real elbow grease into this, I'd really like it if you could present the following:

First of all - clearance access. I need to move around freely and without restrictions; across the logistics area, all of R&D naturally, both Lab-A1 to A-3, as well as the drydock access for when we'll finalize the tests at the later stages. I know Val like the back of my hand, because I've lived here for years, knowing where to go for what won't be a problem, so long as I can actually do it. Oh, and while we're at it; Tier 3 access to the holo-library database for more research and additional cross-references, just in case we're going to run into a brick wall.

I want a rundown of the current stage of the project. I'd like to know how far along your team has been at it, the progress that's been made, and what else needs to be refined and ultimately accomplished.

I'd like to know if there are decrypted, individual serial blueprints of both of our little monsters. I'd like to have schematics to work with - especially about the SL reactors. Those are going to be the bread and butter of the Twins, naturally. Just let me know who's got access to them and I'll bug them about it.

I want a brief list of names of go-to supervisors I can speak to. I've thought about it for a minute, and ideally, in this team I'd really like to have engineers I can share and adjust my theories with, a material quality assurance officer I can rely on, a few quartermasters to confirm, energy weapon R&D nerds and a good, goddamn mocha coffee machine from Val's Level 3 cafeteria.

Oh, and last but not least, a restored access to the R&D database. Where else will I be able to share my findings, otherwise? Unless, of course, you would like to have the whole finalized report in some other codex section. That's up to you.

I hope I didn't ask for too much just now. Let me know if I am allowed to keep this line open for any further inquiries.

---

Playback terminated.
Running end-stream paragraphs.
Running burner paragraphs.
ERROR: exception at 0x00007f found
ERROR: exception at 0x000001 ♐︎□︎◆︎■︎♎︎
☜︎☼︎☼︎⚐︎☼︎?︎ ⧫︎♒︎♓︎⬧︎ ♋︎♍︎⧫︎♓︎□︎■︎
♍︎♋︎■︎■︎□︎⧫︎ ♌︎♏︎ ◆︎■︎♎︎□︎■︎♏︎

END 05F68000... OK
BYTES TRANSFERRED = 11676665 (B22BF9 HEX)
‎‏‏‎// UPLOAD STATUS
‎‏‏‎ ‎‏‏‎‎‏‏‎ ‎‏‏‎ ‎‏‏‎‎‏‏‎ ‎‏‏‎ ‎‏‏‎ ‎‏‏‎ ‎‏‏‎ ‎‏‏‎ ‎‏‏‎ // COMPLETED
‎‏‏‎ ‎‏‏‎‎‏‏‎ ‎‏‏‎ ‎‏‏‎ ‎‏‏‎‎‏‏‎ ‎‏‏‎ ‎‏‏‎ ‎‏‏‎ ‎‏‏‎ ‎‏‏‎ // SHUTDOWN

[Crucible]

...neural.uplink detected...
...starting encryption...establishing connection...
identified: AUX-CRB-764 'Crucible'

...TRANSLATING DATA...

Lazurith, I apologize for the delay in my reply. I've been busy lately with defense concerns, and the project has been dragging in other areas that mean not much progress has been made. Regardless, we can establish the baseline for you now.

Your role in the project, should you choose to accept it, would be as an engineer and consultant. We would bring you on as part of the engineering team, answering to the chief of the project. Being engineering staff, you shouldn't have to get your hands dirty--your job would be to draft up plans in collaboration with the other engineers, and most importantly, get the Star Lances online. I don't care how you do it for your first run--you could have a station-bound power plant hooked up to the weaponry with proverbial jumper cables, for all I care. What I need first is proof that they can still fire. Once that's done, you'll focus on making them compatible with our standard ship-based power plants.

As far as clearance goes, you'll be cleared for access to all materials and projects that are directly related to the twins, including all weapons research we've conducted in the past. You'll also have general access to materials classified as Sensitive or lower. Anything more than that will need further approval--not because I don't trust you, but because that's what standard protocol is these days. If you have specific projects you want access to, feel free to request it. It'll most likely be approved as long as it's not unreasonable. You'll be assigned some labs to work with, alongside the rest of the team. R&D won't be your oyster, but you'll have no less access than anyone else in your position, and further access can be approved on a case-by-case basis, as necessary.

For Labs A1 and A3, I need to know what you need from them, specifically. We can get that clearance out of the way immediately if you just let me know your reasons.

As I hinted at before, the project's in its early stages at the moment. Right now the team is making a full audit of the ships and their components so that we can obtain an accurate report of the materials that we'll need to bring them back to operational status. This includes an assessment of our drydock facilities to see if we have what it'll take, or if we'll have to go elsewhere.

For blueprints, you will be cleared to access those materials. I'll send you the dossier once you agree to the terms.

For access to the R&D database, you'll be cleared to access materials that are relevant to the project, as I said. Since you're working on commission, I can't promise blanket access, but the file for this project will be open to you, and you'll be able to submit materials as necessary. If you want blanket R&D access, I'll need to talk to the rest of the Inner Phalanx--however, I can tell you right now that they probably won't agree to something like this unless you return to the Technocracy, given the potential security risk. Again, this isn't about you specifically--it's about protocol. If we made an exception for you, it would set a precedent that could lead to future security breaches.

Let me know if you can agree to these terms. If you have any more questions, feel free to ask. I'll keep this channel open.

---

...transmission complete
...terminating stream

[Geno]

EFUSE MACHID STATUS: ONLINE
NEURAL UPLINK: ONLINE
CONNECTION STATUS: ONLINE
ENTRY POINT: H7 MASTERDECK (STATUS: □︎■︎●︎♓︎■︎♏︎)
VERIFYING CHECKSUM... OK
MASTERDECK START ATTR = 0X1273000
FLAT DEVICE TREE START ADDR = 0X12B1E800
LEN1 = 0X3EE800
LEN2 = 0X43F980
MAGIC = 0XEDFE00
EFUSE MACHID IS NOT SET.
USING MACHID 0XF81000 FROM CLOUD STORED BACKUP
DEVICE TREE MASTERDECK/PRF_RESERVED_END
RELOCATING RIGID DEVICE POSDISK 1
LOADING POSDISK 1 TO 05008000... OK

USER ID: LAZURITH
transmission point of origin: INVERNESS
currently connected to: ⧫︎♒︎□︎◆︎♑︎♒︎⧫︎⬧︎relay

⚠ Executing autoencrypt.bxt script - 11.32 MiB
⚠ Executing autoburner.cmrd script - 812.34 MiB
Securing encryption through designated parameters...
Pinging designated relays...

⚠ AUG-O-LE00 connection established.
Transmitting visual data...

// FILE INFORMATION: \\
File name: Alright already
File size: NaN: MiB
File type: Visual recording, including (0) attachments

---

I agree with these terms. There, take that to the bank.

I'd like to order a copy of your finest dossier fascicle, please. I want to get this done as soon as possible.

---

Playback terminated.
Running end-stream paragraphs.
Running burner paragraphs.
ERROR: exception at 0x00007f found
ERROR: exception at 0x000001 ♐︎□︎◆︎■︎♎︎
☜︎☼︎☼︎⚐︎☼︎?︎ ⧫︎♒︎♓︎⬧︎ ♋︎♍︎⧫︎♓︎□︎■︎
♍︎♋︎■︎■︎□︎⧫︎ ♌︎♏︎ ◆︎■︎♎︎□︎■︎♏︎

END 05F68000... OK
BYTES TRANSFERRED = 11676665 (B22BF9 HEX)
‎‏‏‎// UPLOAD STATUS
‎‏‏‎ ‎‏‏‎‎‏‏‎ ‎‏‏‎ ‎‏‏‎‎‏‏‎ ‎‏‏‎ ‎‏‏‎ ‎‏‏‎ ‎‏‏‎ ‎‏‏‎ ‎‏‏‎ // COMPLETED
‎‏‏‎ ‎‏‏‎‎‏‏‎ ‎‏‏‎ ‎‏‏‎ ‎‏‏‎‎‏‏‎ ‎‏‏‎ ‎‏‏‎ ‎‏‏‎ ‎‏‏‎ ‎‏‏‎ // SHUTDOWN