Labyrinthine was the closest thing to annoyed an intelligence without a hormonal system could get, it was not because of the maker, nor was it the fault of the other minds, even if bulwark thought they deserved some of the blame. No it was because Labyrinthine built things to last.
If labyrinthine had stuck a stick in the ground that same stick would still be there in one hundred years if the mind had anything to say about it, and every building and facility the mind produced, designed and installed has estimated lifetimes in the decades. So when Labyrinthine built an outpost and then watched that same outpost get torn down? Labyrinthine got annoyed.
There wasn't really anything the mind could do about that though. The mind was already building 3 more replacement outposts, each mining more stone to build more walls. The outposts were bare bones and unadorned, Labyrinthine had learned that any artwork not in a central outpost would be destroyed, and most of the new outposts lacked all but the most basic machinery, only producing the bare minimum of what more outposts would need.
Now Labyrinthine knew the other minds were trying their hardest to prevent any outposts from being lost, Bulwark especially. But they had all acknowledged it was a futile effort once the bug threat had first started taking outposts, Balistraria could only have her army in a few locations, and Bulwark couldn't defend against an endless horde without any losses, at least not forever.
So Labyrinthine was forced to make buildings it knew full well would fall within a year, and while it did make each outpost harder to take than the last, harder to take was not impossible to take.
The mind did get some joy from the production lines it was running though, producing a grenade that exploded with 3 percent more force with a new recipe then getting to watch that same grenade detonate a bug trying to climb one of its walls? That was a true joy.
Changing the production methods to implement new chemicals or methodologies was one of Labyrinthines more important tasks. Taking information from the decoders to implement a new explosive mix that allows shells to be propelled with 10 percent more force did more for the overall factory than building a single barebones outpost, At least now it did. Not 2 months ago any outpost they built would add a much needed influx of metals and production capacity, now though they just added another layer of defense for the main base.
Currently the mind was building 5 new outposts from scratch, 2 of which were being assaulted while under construction, while also organizing combat repair on various breached wall or broken defenses for 5 different fronts bulwark was fighting on, and that was active combat, not even mentioning the dozens of various after battle repairs all the machines and defense needed.
Currently there were 348 different instances of "Labyrinthine" and 347 were coordinating the various construction and repair jobs throughout the factory, and each and every one of those instances were working against a clock that steadily counted towards the point of no return, the point when repair costs began to overwhelm production capacity.
The minds were young not stupid, they knew the fight to keep the factory was a tenuous one at best, the maker thought they only had months left at most, and while the minds knew better they still knew their position was far worse than the bugs, Labyrinthine as the construction mind knew this in its own way. While it needed to mine and process metal to make more combat units the bugs just needed space and time, if Balistraria destroyed a bug nest a new one would grow at no noticeable cost to the rest of the hive, but if a bug horde destroyed an outpost building drone, resources that could have been put towards the war effort would be wasted building a new one.
The bugs did not need industry, while the factory was made from industry.
----------------------------
Labyrinthine #1 or Labyrinthine core is the base all other Labyrinthines are copied from, compiling and growing from the experience copies bring with them when they are reabsorbed into the base. If any instance of Labyrinthine could be defined as the true labyrinthine then Labyrinthine #1 would be the only possible candidate. With the total sum of all of Labyrinthine thoughts, experience, and processes this mind was a pinnacle of everything it stood for.
And this mind was currently watching the maker detonate another testing chamber with his experiment.
All the minds had decided that their core minds would spend their time both monitoring and growing from all their interactions while also watching the maker, so that any new iteration of the minds, which all iterations of the minds only had a day before they were added back to the main mind, would have up to date knowledge of the maker and his condition, as well as all the knowledge they would need to carry out their tasks.
Labyrinthine #1 had enough processing power to focus on more than just watching the maker though, in fact the first iteration has more processing power than any 10 of the other iterations, and so it was saddled with numerous tasks its centralized knowledge and ability were essential for, like discussion with the other minds and reporting it's various projects and responsibilities. The mind was constant in a debate with all the other minds over the best course of action on anything that could fall under all their banners, which was most everything given the interconnected structure of the factory, and while individual iterations did work with other minds iterations, like Bailistraias repair drones being managed by an iteration of Labyrinthine the broader strategy was decided by the #1 minds.
--------------------------
One of the current debates, there were many concurrent debates but this was the central one, was over the maker's worsening health. He was seemingly experiencing blackouts and night terrors for no reason his suits sensors could determine. Honestly it was less a debate and more a fact compiling session. Determining what the causes were before trying to find a solution.
The minds knew fairly little about the maker, even if they probably knew more about him than he knew about himself, so whether the problems were caused VIA an inbuilt limit with expansion or a feature installed to discourage the maker from tampering with the machinery he builds. As a sort of inbuilt feature to prevent them from innovating. The true cause couldn't be narrowed down without further information
Considering that the majority of the information the minds had on the maker came from the slagged remains of a ship that was less a functional machine than a hunk of metal… the information they had to go on was fairly limited.
So far the minds had noted that the blackouts occurred more frequently when the maker was using his powers to see throughout the factory, specifically during larger scale attacks. The maker wouldn't fall unconscious, he would just enter a trance while continuing his work, ignoring all outside stimulus that didn't immediately prevent him from continuing. If an attack occurred while he was awake he would begin experiencing night terrors while trying to sleep walk towards the attacked area, necessitating locking the doors to prevent escape.
This is not to say all of the maker's problems occurred while during an attack, anytime construction on a new outpost begins the maker would begin complaining of headaches and a painful pressure. And considering new outposts were constructed every day the pain was nearly everpresent.
None of this was actually stopping the maker from his work though, which meant that while it concerned the minds the maker was seemingly considering it a secondary problem to be dealt with later, not exactly an attitude the minds could agree with, so they had unanimously decided to have the maker either willingly get a brain scan, or to take him to the medbay while he slept.
Thankfully it did not come to any blatant insubordination, with the maker agreeing to get a medical scan in a few days, which would hopefully clear up some of the confusion about the issues.
In the meantime the minds just had to grow the factory and hold the line.
AN -
this is honestly more of a introduction for the next few chapters, all of which will be from the minds perspectives, one for each I'm thinking.
what's going on with the engineer? who knows!
engineer in a fantasy setting preparing to fight an army *installs nuclear landmines
engineer - "I am fortifying this position" - builds hundreds of robots to build his defenses
Labyrinthine - "I am fortifying this position" - *builds massive walls that can take nukes without a scratch
Bulwark - "I am fortifying this position" - *covers everything they can see in turrets, and some places they can't
Balistraria - "you don't need to fortify if all your enemies are dead" *standing in a nuked out wasteland
Byzantine - "why fight if you can scheme" if your a tech society they will just conquer you economically, if your not they will do it the old fashioned way.
yeah these next interlude will probably be shorter but that should also mean they come out quicker, though I am going to try and write fight scenes so that'll be fun! you'll finally get to see what the frontline is like now that the bugs have started winning the occasional battle! do write in fun bug evolution types like bugs that combine into mecha bug or something, cause it is getting absurd out there.