yrindor (![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png)
yrindor) wrote in ![[community profile]](https://www.dreamwidth.org/img/silk/identity/community.png)
writetomyheart2021-01-20 11:05 pm
yrindor) wrote in writetomyheart2021-01-20 11:05 pm
Entry tags:
[Team Three] Interstellar Jam
I've been reading the Murderbot Diaries recently, and I love the narrator, so I decided to play around with that for the first time. Muderbot Diaries, G, 400 words.
Weird didn't begin to cover what I was seeing. Weird was what humans said when they found their communication equipment under the sink or when the entertainment feed was playing a different program than they expected (it was never actually weird; humans just have notoriously bad memories sometimes).
This, however, was actually weird. I wasn't created to be an expert in astrophysics or stellar formation (and it's not a skill I've ever felt compelled to learn), but the transport vessel was. Like all bots, transport vessels don't communicate in the way humans do, but part of being a SecUnit means knowing how to read them too. A good SecUnit protects its charges, and that means making use of all possible sources to monitor for problems. I'm definitely not a model SecUnit--my hacked governor module should be the first sign of that--but outsourcing has its merits--namely more time to watch the entertainment feed.
Anyway, the takeaway here is that when a bot starts acting weird, there's a problem. Nothing in the system diagnostics suggested a problem with the vessel itself, which means the problem was with whatever was happening on the other side of the window. Like I said, I'm not a scientist, and SecUnits are usually consigned to cubes in the cargo hold for transit, but it doesn't take an expert to know that stars aren't usually supposed to explode.
Correction: stars explode all the time--there'd be a lot of unemployed stellar physicists if they didn't--but stars in the path of transit vessels don't explode. No one except researchers wants to navigate a stellar debris field, and it's probably a liability in the contracts--not that I pay any more attention to those than I have to.
Anyway, the survey packet for this sector hadn't indicated anything of this sort. It wouldn't be the first time I'd been given incomplete information, but it was definitely one of the more inconvenient locations. At least there weren't any humans on the vessel, and in the grand scheme of things, no one would miss a rogue SecUnit and a creaky transport too much. I didn't seem to be receiving any weird orders to my hacked governor module this time, so it probably wasn't sabotage, just plain bad luck.
Unfortunately, I had a contract to pick up, and that meant I needed to get to the next transit ring, exploding star or not. So much for catching up on new shows en route.
You're up, ziskandra!
Weird didn't begin to cover what I was seeing. Weird was what humans said when they found their communication equipment under the sink or when the entertainment feed was playing a different program than they expected (it was never actually weird; humans just have notoriously bad memories sometimes).
This, however, was actually weird. I wasn't created to be an expert in astrophysics or stellar formation (and it's not a skill I've ever felt compelled to learn), but the transport vessel was. Like all bots, transport vessels don't communicate in the way humans do, but part of being a SecUnit means knowing how to read them too. A good SecUnit protects its charges, and that means making use of all possible sources to monitor for problems. I'm definitely not a model SecUnit--my hacked governor module should be the first sign of that--but outsourcing has its merits--namely more time to watch the entertainment feed.
Anyway, the takeaway here is that when a bot starts acting weird, there's a problem. Nothing in the system diagnostics suggested a problem with the vessel itself, which means the problem was with whatever was happening on the other side of the window. Like I said, I'm not a scientist, and SecUnits are usually consigned to cubes in the cargo hold for transit, but it doesn't take an expert to know that stars aren't usually supposed to explode.
Correction: stars explode all the time--there'd be a lot of unemployed stellar physicists if they didn't--but stars in the path of transit vessels don't explode. No one except researchers wants to navigate a stellar debris field, and it's probably a liability in the contracts--not that I pay any more attention to those than I have to.
Anyway, the survey packet for this sector hadn't indicated anything of this sort. It wouldn't be the first time I'd been given incomplete information, but it was definitely one of the more inconvenient locations. At least there weren't any humans on the vessel, and in the grand scheme of things, no one would miss a rogue SecUnit and a creaky transport too much. I didn't seem to be receiving any weird orders to my hacked governor module this time, so it probably wasn't sabotage, just plain bad luck.
Unfortunately, I had a contract to pick up, and that meant I needed to get to the next transit ring, exploding star or not. So much for catching up on new shows en route.
You're up, ziskandra!