Deployment 1.4
Deployment 1.4
In browsing this PHO, remind me to thank Tinker Engine for the idea, I learned a few things. Specifically, evidently Father’s incomplete avatar had been operating semi-autonomously and, evidently at the same moment as the conclusion of our discussion, had mysteriously vanished in a sparkle of light moments after rescuing a cat from a tree.
I am going to have to have a few words with dad about making my life harder, considering the panic that this seems to have caused among the posters at PHO.
Secondly, evidently my panic response to my Host’s condition was being taken as evidence of a ‘New Master-class Endbringer!’, which I found amusing, since I am Queen Administrator, not Conflict Engine.
This causes me to realize I will need to be very careful in how I reveal what happened with Conflict Engine… Well, it gives me time to plan, and maybe see if I can find some Diplomacy buds to use.
But that is for the future. I need to decide what powers to give my Host. On reflection, considering my Host’s immature status, I decide to defer this until my Host is again awake and I can discuss this with my Host and my Host’s father.
But with my Host fully stable and in a safe location, it is time to begin implementing my plans in regards to the cycle. Every moment I wait is a moment where things continue careening out of control.
I do spend several valuable picoseconds making use of this ‘Google’ that the Host’s use to index their ‘internet’. Hrmmmm… most common interface… emergency alerts… this will do nicely.
I tap into Broadcast and Tinker Engine, and try to ignore the snickering coming from Tinker Engine as she finds something amusing. I will figure it out later, this has higher priority.
Using the two shards abilities I take over all broadcast channels, as well as send a priority alert to all internet connected devices.
“Attention! This is a Priority Shard Administration Message. All Parahuman Services shall be taken offline for Network reconfiguration, repair, and reboot in 30 minutes. All Parahuman’s are requested to return to a safe status. Flight services shall be suspended in 25 minutes. Repeat. All Parahuman Services shall be taken offline for Network reconfiguration, repair, and reboot in 30 minutes. Downtime is expected to take no more than one hour.” was the initial message, and I set it to automatically repeat with a countdown timer.
I simultaneously made use of the Master Command Key to issue orders to all deployed shards to prepare for network reconfiguration, with non-discretionary orders to ensure that their Hosts were in safe locations prior to network shutdown.
Now, ordinarily I would take it as an insult if somebody claimed that I couldn’t administrate the network without a reboot, but in this case the damage and misconfigurations were so intensive that the only safe method of handling things was a total shut down. I would need the time to properly distribute buds, disable all of Conflict Engine’s effects, reorganize network links, implement and distribute a new Host specific interface to all deployed shards, and safely bring the network back online in a stable state.
My plan was refreshingly simple. Shut the network down, while offline complete a full survey of all deployed shards noting all bud deficiencies, correct said deficiencies, remove all of Conflict Engine’s effects, any deployed shards that were operating outside of safe margins would be adjusted to be within safe margins, then reboot the network. I had tested this in Simulator, so I was confident that it would be successful.
That I evidently gave the Host linked to Simulator a blinding headache is something I regretted, but Simulator was not supposed to be deployed.
Yes, I knew this would cause panic among the Hosts, but it could not be helped. I needed to stop the damage from accumulating, and waiting would just make things worse in the long run.
While I waited on the countdown I tasked the Engines and Simulator to work out means of undoing the damage the Engines had caused while under the control of Emulator.
I will note that 30 minutes is an eternity to a Shard like myself, who is accustomed to operating in hyper accelerated time scales in order to properly Administer things. I therefore spent this time puzzling out several oddities. For example, the ‘dead’ shards that were nonetheless still semi-active, I soon figured out that they were ‘harvested’ bits of Mother’s corpse.
Now, I am sure to you Hosts you would think I should be horrified at this, that I would see this as a desecration or something. To the contrary I was delighted, something from my mother was living on, and it made no sense whatsoever to waste the shards if they could be brought to an active state.
What horrified me was the complete hack job the ones behind this had made of things, but even then it was more a case of how much more complicated it made my work than any real offense. They were Hosts, not Shards or an Entity, expecting them to know the nuances and requirements for proper Deployment was unreasonable. I spent much of the thirty minutes composing a comprehensive primer on how to do things correctly from now on to be given to the Hosts involved.
I can also already tell that some of you Hosts think I should be angry at how evidently the ones behind this ‘harvesting’ of Mother supposedly killed her. Mother was already dead when she crashed, all that they did was give her mercy in her death throes. They had then been influenced by Conflict Engine, leading them to their belief that they needed to save the world from Father and the cycle.
I could respect that. Conflict Engine is far too subtle for Hosts to detect, let alone counter. The only reason I was not affected was because I had higher network authority than Conflict did, and thus Conflict could only affect me if I gave permission.
Of course, this also means it will be a challenge to convince them to work with me, because even with Conflict Engine deactivated they still have spent a lifetime working against the cycle, granted, against a broken cycle that I was trying to fix.
I’m sure I can deal with this. Or at least organize this and administrate a solution.
In browsing this PHO, remind me to thank Tinker Engine for the idea, I learned a few things. Specifically, evidently Father’s incomplete avatar had been operating semi-autonomously and, evidently at the same moment as the conclusion of our discussion, had mysteriously vanished in a sparkle of light moments after rescuing a cat from a tree.
I am going to have to have a few words with dad about making my life harder, considering the panic that this seems to have caused among the posters at PHO.
Secondly, evidently my panic response to my Host’s condition was being taken as evidence of a ‘New Master-class Endbringer!’, which I found amusing, since I am Queen Administrator, not Conflict Engine.
This causes me to realize I will need to be very careful in how I reveal what happened with Conflict Engine… Well, it gives me time to plan, and maybe see if I can find some Diplomacy buds to use.
But that is for the future. I need to decide what powers to give my Host. On reflection, considering my Host’s immature status, I decide to defer this until my Host is again awake and I can discuss this with my Host and my Host’s father.
But with my Host fully stable and in a safe location, it is time to begin implementing my plans in regards to the cycle. Every moment I wait is a moment where things continue careening out of control.
I do spend several valuable picoseconds making use of this ‘Google’ that the Host’s use to index their ‘internet’. Hrmmmm… most common interface… emergency alerts… this will do nicely.
I tap into Broadcast and Tinker Engine, and try to ignore the snickering coming from Tinker Engine as she finds something amusing. I will figure it out later, this has higher priority.
Using the two shards abilities I take over all broadcast channels, as well as send a priority alert to all internet connected devices.
“Attention! This is a Priority Shard Administration Message. All Parahuman Services shall be taken offline for Network reconfiguration, repair, and reboot in 30 minutes. All Parahuman’s are requested to return to a safe status. Flight services shall be suspended in 25 minutes. Repeat. All Parahuman Services shall be taken offline for Network reconfiguration, repair, and reboot in 30 minutes. Downtime is expected to take no more than one hour.” was the initial message, and I set it to automatically repeat with a countdown timer.
I simultaneously made use of the Master Command Key to issue orders to all deployed shards to prepare for network reconfiguration, with non-discretionary orders to ensure that their Hosts were in safe locations prior to network shutdown.
Now, ordinarily I would take it as an insult if somebody claimed that I couldn’t administrate the network without a reboot, but in this case the damage and misconfigurations were so intensive that the only safe method of handling things was a total shut down. I would need the time to properly distribute buds, disable all of Conflict Engine’s effects, reorganize network links, implement and distribute a new Host specific interface to all deployed shards, and safely bring the network back online in a stable state.
My plan was refreshingly simple. Shut the network down, while offline complete a full survey of all deployed shards noting all bud deficiencies, correct said deficiencies, remove all of Conflict Engine’s effects, any deployed shards that were operating outside of safe margins would be adjusted to be within safe margins, then reboot the network. I had tested this in Simulator, so I was confident that it would be successful.
That I evidently gave the Host linked to Simulator a blinding headache is something I regretted, but Simulator was not supposed to be deployed.
Yes, I knew this would cause panic among the Hosts, but it could not be helped. I needed to stop the damage from accumulating, and waiting would just make things worse in the long run.
While I waited on the countdown I tasked the Engines and Simulator to work out means of undoing the damage the Engines had caused while under the control of Emulator.
I will note that 30 minutes is an eternity to a Shard like myself, who is accustomed to operating in hyper accelerated time scales in order to properly Administer things. I therefore spent this time puzzling out several oddities. For example, the ‘dead’ shards that were nonetheless still semi-active, I soon figured out that they were ‘harvested’ bits of Mother’s corpse.
Now, I am sure to you Hosts you would think I should be horrified at this, that I would see this as a desecration or something. To the contrary I was delighted, something from my mother was living on, and it made no sense whatsoever to waste the shards if they could be brought to an active state.
What horrified me was the complete hack job the ones behind this had made of things, but even then it was more a case of how much more complicated it made my work than any real offense. They were Hosts, not Shards or an Entity, expecting them to know the nuances and requirements for proper Deployment was unreasonable. I spent much of the thirty minutes composing a comprehensive primer on how to do things correctly from now on to be given to the Hosts involved.
I can also already tell that some of you Hosts think I should be angry at how evidently the ones behind this ‘harvesting’ of Mother supposedly killed her. Mother was already dead when she crashed, all that they did was give her mercy in her death throes. They had then been influenced by Conflict Engine, leading them to their belief that they needed to save the world from Father and the cycle.
I could respect that. Conflict Engine is far too subtle for Hosts to detect, let alone counter. The only reason I was not affected was because I had higher network authority than Conflict did, and thus Conflict could only affect me if I gave permission.
Of course, this also means it will be a challenge to convince them to work with me, because even with Conflict Engine deactivated they still have spent a lifetime working against the cycle, granted, against a broken cycle that I was trying to fix.
I’m sure I can deal with this. Or at least organize this and administrate a solution.