(Photo by Thomas Stix)

There were a number of advantages to the way Earth Transit Technologies went about filling their colony ships. By being able to hand select each person, they could ensure that there were as few bad eggs, so to speak, on any given ship. Criminal backgrounds, difficult personalities, and poor medical histories were all disqualifying elements. Unfortunately, not everything about a person can be found through background checks. A person who broke the law but was never caught would be indistinguishable from a law abiding citizen. Then there were those who had never broken the law or taken part in any large acts of dissent, but only because they’d never really had the opportunity or the right situation present itself.

As BaBS-Y observed the visual inputs from dozens of robots, all sweeping through the Thesis in search of the mutineer(s), the salon robot was also busy scanning through the data banks for any other clues. There were several hot spots for data requests and it was those areas that BaBS-Y wanted to investigate first. Without access to the communications systems, it couldn’t see what information was being requested, though. Only when someone tried to upload information would BaBS-Y be able to fully examine the data. Already, it had intercepted and denied several attempts at taking control of more of the Thesis’ systems.

The mutineer(s) are proficient in generating new protocols

BaBS-Y considered that fact. Not many people would be able to write such new protocols that quickly. Basic programming was pretty common knowledge, true, and modern programming languages were designed to be intuitive, but the complexity and sophistication of the protocols BaBS-Y was intercepting was clearly the work of someone with years of experience.

Such knowledge and experience is uncommon among the general population of the Thesis

…

The mutineer(s) are more likely to be among actual crew of the Thesis

…

This unit was unable to gain access to either the Security or Communications systems but the mutineer(s) were successful in both those systems

…

When compared to their protocols, this unit is better at generating protocols

…

It does not seem likely that the mutineer(s) would have been successful in forcing their access into the Security or Communications systems without being discovered

…

The mutineer(s) most likely already had access to those systems through their positions aboard the Thesis

…

BaBS-Y focused in on the areas around the security stations on each sector of the Thesis. There were a few that were being particularly active in the data banks and BaBS-Y had a few robots begin making their way over towards them.

For the most part, the Thesis seemed to be operating normally. People were going about their business. They didn’t seem to be aware of what was going on. Indeed, with the exceptions of sectors one and three that were in lock down, everywhere else looked almost normal. There were, however, a few noticeable issues that, if a person looked for them, would make them realize something was different. Something was wrong. For one thing, the usual communications from the Thesis authorities were absent. Those who were related to or close friends with anyone on sectors one or three were missing for their work shift; their doors to their quarters were locked and the door comms were malfunctioning. Even the regular comms were having issues, with people only able to communicate with people on the same sector, unless that person was locked in their quarters in which case no comm could reach them.

All of this, BaBS-Y had gathered by observing and listening to the people going about their day while the robots moved about, practically unseen as they cleaned and moved about the different sectors. ISaCC, an Information Services and Community Coordinator, drew near to the main security hub on sector seven and BaBS-Y turned its attention to it in full. This was where all of the security personnel for the Thesis were coordinated.

ISaCC had a similar build to BaBS-Y, having been designed to interface with people quite often. A lot of people called ISaCC a party bot since a lot of what it did was help organize various social activities for the different sectors. As ISaCC approached the entryway into the security hub, a pair of security officers stepped out of the frosted doors and then hesitated.

“ISaCC?” the one on the right spoke.

“I have come to–

“Now’s not the time,” the same security officer interrupted ISaCC.

Neither security officer moved.

“I’m sorry,” ISaCC said, “but I haven’t been able to reach a number of people on my comm and their residences appear to be locked.”

“They’re probably busy,” the other security officer said.

“None of them reported for work today, either,” ISaCC said.

BaBS-Y wasn’t controlling ISaCC completely. It was easier to simply give the robot the basics of what it needed to do and then let it handle the rest. That way it would behave naturally and thereby minimize raising suspicion.

“Then maybe they’re just sick today,” came their reply, almost speaking at the same time.

Their response seems predetermined, BaBS-Y noted. It wasn’t sure if they were involved in the coup or if they were trying to avoid a panic by admitting that people were disappearing or being held captive.

“That many sick, and at the same time, might signal an outbreak,” ISaCC said, his voice modulating to express concern. “I am trying to contact medical but–

“That’s enough!” the security officers hissed as they reached forward and grabbed ISaCC. “Forget about the whole thing, just go stand in your station and be quiet. That’s an order.”

BaBS-Y stopped the override protocol from effecting ISaCC. However, the party bot was out of its depth here and lacked the protocols to handle this encounter. A few seconds passed while BaBS-Y took full control of the robot. This was sub-optimal but it needed to know why these security officers were behaving this way. It was also conflicted on whether this was an allowed course of action.

This unit stated that it would not engage the mutineer(s)

…

This unit is not sure if these are mutineers

…

This unit is still only performing reconnaissance

ISaCC, like most robots, had a number of lights designed to give it a welcoming and aesthetically pleasing look. The lights dimmed as it rebooted briefly while BaBS-Y asserted its control.

“Come on, get moving,” the security officer grunted as he tried to shift the admittedly heavy robot.

“Excuse me,” BaBS-Y said, lowering the volume of its vocabulator to something close to a whisper, “this unit is functioning under the authority of the Robotics Control Center, investigating a potential mutiny. It is most likely that someone with prior access to the security systems is involved.”

There were a number of ways the security officers could react to that statement and BaBS-Y was confident that each of those reactions would tell it a great deal about whether or not these two were involved.

As it was, the two stood there, flanking ISaCC and looking back and forth. At last, one of them spoke.

“Alright, come with us.”

They led ISaCC through the frosted glass doors and into the main hub for security aboard the Thesis. Inside there were only a half dozen or so people. There were several more workstations than there were people and it looked like barely a skeleton crew was at work. There were a few actual offices but for the most part the area was set up with an open floor plan with the workstations taking up the central part of the space.

“What is this!?” an angry shout carried across the room and everyone looked up, first towards the one who had shouted and then over to the two security officers and ISaCC. The angry voice belonged to a middle-aged man. BaBS-Y recognized him as Shep Mason, the head of security for the Thesis and a member of the Thesis’ council.

“Mr Mason,” BaBS-Y began but got no further.

“Get that thing out of here!” Mr Mason shouted and pointed animatedly back towards the doors the trio had just come from. “They’ve got cameras, you idiots! It could be broadcasting to who-knows-where!”

His voice remained at a stead volume, never once letting up or calming down. Both security officers flinched as they immediately reversed direction and began pulling ISaCC back towards the doors.

“This unit must apologize for the intrusion,” BaBS-Y said as it planted its feet and braced itself against the two security officers, slowing them and then stopping their progress. “This unit must be allowed to speak with Mr Mason regarding the possible mutiny taking place.”

There was a brief pause as all eyes turned from ISaCC to Shep Mason, and then back to ISaCC. Shep’s face reddened as his mouth worked furiously. A few of the other people looked down or away from ISaCC while some more looked defiant.

“I see,” BaBS-Y said. “This unit did not expect to discover the mutineers so quickly. This unit will notify the–

“SHUT IT OFF!” Bellowed Shep Mason and he charged across the room, drawing a small baton from his belt. There were no firearms on the Thesis and few real weapons were ever issued, even to the security officers.

“This unit will not engage any known mutineers without prior authorization,” BaBS-Y said, stepping back and away from Shep Mason’s strike. Its arms were still being held by the other two security officers so BaBS-Y twisted and pulled, yanking its arms free and then jumping back yet again as Shep Mason came on, still swinging his baton. “This unit is requesting permission to engage with mutineers.”

It wasn’t clear to BaBS-Y whether or not the people around it had heard what it said.