RP Log: Worse Possibilities

From Phoenix Rising Wiki
Jump to navigation Jump to search
Roleplay Log
Participants:
Location(s):
  • XO's Office -- USS Phoenix
Stardate:
  • 126203.0
2023-05-03 22:46
XO's Office - Saucer <USS Phoenix NCC-170100-A>
The large, spatious office sports few personal possessions. The Vulcan occupant keeps a lirpa mounted on one wall, and a kal-toh set sits on her desk. Its rods are in various states of play when visitors come, depending on where she's left off last. The rest of the furnishings are fleet standard issue and include the desk with two chairs before it as well as a seating area near the window.
Out the viewport: The stars streak by as the ship travels at warp.


T'Shaav is standing with her back to the door, at the viewport, gaze directed to the elongated stars of warp speed. She doesn't turn as the door opens.

Worthington enters and snaps to. "Lieutenant commander Worthington reporting as ordered. You wished to see me commander?" he says.

T'Shaav turns after a beat and walks to her desk, gesturing you to a chair. "How do matters progress for you so far?" She inquires quietly.

Worthington takes the offered seat and replies. "I have the computer digging into the life of crewman Jenkens. I am attempting to establish a picture of her life, routines, known associates, and any potential humanist connections," he says. "I'm also attempting to identify who she routinely worked with, and who her date was supposed to be last night. Furthermore, though this likely won't lead anywhere, I'm attempting to pull security records for deck 27 and surrounding areas around the time of the murder. I'm expecting to find those records erased or tampered with, likely in a broader area and timeframe than necessary to cover the culprit's tracks, but still worth a look in case they slipped up. Whoever did this, they knew what they were doing, they were compatent, and they had sufficient knowledge, access, or both to tamper with the biological sensors in the entire stardrive. I'm also awaighting the medical report. I doubt we will find significant DNA evidence given the killer's apptitude thus far, but we can still hope. One thing to consider," he pauses. "All accesses via turbolift or jefferies tube or umbillical between the stardrive and saucer around the time of the red alert, as lieutenant Choma did sense someone potentially fleeing in that direction, and that could narrow our list down somewhat, unless those records have also been erased."

The Vulcan is quieter than normal, and she takes a moment to consider her response. "Who aboard would have the skill as well as the access to commit this crime?"

Worthington considers. "Any of the senior officers, both of us included," he says. "Captain Shulon's espionage experience, commander Coil's various experiences as well. Engineering wise, any engineer with sufficient knowledge and access could have pulled the sabotage off. As for the killing itself, people with security, intelligence, or medical knowledge would be able to ascertain how to torture and kill a person in such a manner as was done. If this person was a humanist or humanist sympathiser, this would likely eliminate non-humans, so you, the captain, commander Coil, commander Ki'Vek, etc. Also, looking at circumstances. Captain Shulon, lieutenant Hauser, and lieutenant Choma were in shuttlebay 2 when the murder happened. I was in the combat simulators on deck 23, showing around our new ensign, ensign Tanner. I then reported to deck 25 to captain Shulon's location when the red alert sounded. Commander Ki'Vek was on the bridge acording to console records, and you were as well during the crisis. Doctor Sawyer's precise location is not accounted for, but he did respond quickly to shuttlebay 2. Plus, he is a known quantity among the senior officers as are just about all of us, so it would be difficult to imagine him doing such a thing. The list of people who could pull off specific parts of the murder is a long one. Narrow it down to all aspects, you would have to account for any cross training that was received. You could not easily account for any informal training or knowledge that could have been obtained however commander."

[Remote Uplink Device (5164): Worthington Uplink Device (16491): commander Ki'Vek, I saw a commbadge alert. I'm discussing the investigation presently with the XO. Do you have something for me?]
[Remote Uplink Device (5164): Ki'Vek: Console of Operation's Office: Affirmative.]
[Remote Uplink Device (5164): Worthington Uplink Device (16491): acknowledged.]

Worthington adds, "Commander Ki'Vek says she has some aditional information. Would you like her to report here to discuss it commander?"

"I would." T'Shaav says.

[Remote Uplink Device (5164): T'Shaav Uplink Device (5164) T'Shaav: Report to my office, Commander Ki'vek.]
[Remote Uplink Device (5164): Ki'Vek: Console of Operation's Office: Acknowledged, Commander.]

Worthington nods and waits.

Lieutenant Commander Ki'Vek arrives from Main Bridge.

T'Shaav is sitting behind her desk. She appears to be waiting, not conversing, until the Selay arrives.

Worthington nods to the selay upon her arrival. "Evening commander," he says. "What news do you bring?"

"Commanders," the Selay greets as she slithers in. Her dark yellow-eyed gaze touches the viewport briefly before she settles into her coils some small distance away from T'Shaav's desk. "Results of the investigation so far which you have requested of me," she says to Worthington, handing him a pad. "In summary, the sensor and security logs for the area in question they have been deleted. This deletion it begins at the same moment that the ship she went to red alert, and the data logs they resume at the moment in which the computer she announced that the bio sensors they were back online."

"At precisely those two moments?" T'Shaav clarifies. "That implies a computer algorithm intended for such erasure to be started given the initiation of certain conditions, and to be limited by the cessation of those condisions. The commencement of red alert, and its co-occurring failure of bio sensors to start, and the restoration of bio sensors as the terminating condition." She turns to Worthington. "Hence, Commander?" She asks, as if expecting him to have drawn a particular inference.

Worthington considers. "The code may have deleted itself from the computer if that is the case, but that would imply that whoever did this had sufficient computer skills to pull it off. Does anyone know how red alert was triggered, or by who?" he asks. "Also, I am interested in exactly what security records were deleted during that time period. I'd like to see just how thorough our mystery killer was."

"The affected records," Ki'Vek says. "They appear to have been limited to the stardrive section, not the entire ship. They also include the footage records of the medical wing and surrounding areas on deck 27. It is worth noting that the victem she was not noted anywhere in that area in the times leading up to the erasure, nor has any unauthorized access to the computer system leading up to the erasure been detected. I'm compiling a list now of authorized access. You will, I assume, want to interview anyone on said list."

T'Shaav regards Worthington for a long beat. Then, Ki'vek. Then, she offers one word, slightly stressing its final syllable. "Killers."

Worthington almost smiles slightly, but holds himself back. "Lieutenant Choma seems to think that they fled to the saucer section, as his telepathic abilities gave him the impression of someone fleeing far away from him. I wonder, can we pull the saucer's records, check all personnel who arrived to the saucer section via turbolift, umbillical, or jefferies tube during the time frame of the alerts?" he asks, then turns to the vulcan. "Killers plural, commander?" he asks. "A distinct possibility, given the wide array of expertise involved."

Ki'Vek tips her head to one side. "Such a list," she says to Worthington. "It, like the list of authorized computer access, would be quite extensive. Phoenix she is a very large ship with constant travel from section to section. Furthermore, once the alert it was sounded, it is likely that hundreds of people who happened to be in the stardrive section at the time were compelled to rush themselves to their assigned alert stations in the saucer." She eyes the Vulcan at the mention of killers in plural, but makes no remark.

"It is a logical probability," the Vulcan says. "I find it unlikely that one being could so arrange matters as for the computer to fail at a specific moment given a specific condition, resume upon some later condition, and arrange all these matters just so while making plans to torture and murder Crewman Jenkins in a given location at a given time." She shakes her head. "I suggest to you that what we may have is a criminal conspiracy, perhaps one killer in the lavatory, but with confederates elsewhere awaiting his, her, or its signal." She nods to Worthington. "Indeed, killers, plural, since, if this hypothesis is correct, anyone involved would be just as guilty of her murder under the law as the person in the lavatory who broke her neck. Thoughts?"

Worthington nods, considering. "If that note is a warning and not a red herring, well, the humanists were great at conspiracies, and we know that there are survivors that managed to escape the demise of hauser's flagship. We haven't heard from them sense, so I'd expect they've bene keeping a low profile. It seems that crewman Jenkins also was newly assigned to Phoenix during the cardassian crisis." He ponders. "Commander Ki'vek, I know that both of those lists are long, the saucer access list and the list of those people with the type of access required to effect the computer issues we saw, though what if we cross referenced those lists? We still do not know a lot about crewman Jenkins, nor who she was supposed to be meeting. I will need to question those who worked with her, to see if they can shed any light on this. It could be a cooincidence that she is murdered on the night where she is going on a date, but it could also be probative as well." He pauses, thinking. "If we have a conspiracy, our job just got a lot harder. This ship also is not that old. I would start by searching lists of new crew members with the criteria needed to pull this off, to see how many people we have aboard capable of each aspect of the murder, and when said individuals joined the ship. If we had a conspiracy aboard for a long time, why wait to act until now? Logically, we are far from Starfleet, and this is a good time to cause fear and terror. Conversely, if these are conspirators associated in any way with the humanists, they could have done a lot of damage during the cardassian crisis. Just imagine, we're delivering aid supplies, or meeting with a cardassian ship, and someone took over the weapon systems and attacked the cardassians. They could trigger an all out war that would alienate the Federation with our then allies and cause a rather large diplomatic incident. Why wait until we are thousands of light years from home, where their actions will only effect this one ship. They can't coordinate with anyone back home." He ponders. "This sadly leaves more questions than answers."

Ki'Vek nods to Worthington. "Quite so. I will compare the two lists and get a list of any names which they may appear on both. As for the rest, I'm afraid I don't have those answers just yet." She looks toward T'Shaav as if awaiting a possible answer from her to Worthington's questions.

"We know little," the Vulcan says. "As you hinted, Mr. Worthington, even the subject of motive is in question. Perhaps the motive is what it appears to be from the note. Perhaps the note is a blind. We lack evidence either way. Nor can I be absolutely certain of the presence of confederates. but if there be none, then there is one highly placed and highly skilled individual onboard. These are the questions to which you must find answers. Preferably before the next victim dies."

"I will see to the compilation of that list," Ki'Vek says as she uncoils herself. She gestures to the door. "If I may, Commander?" she asks of T'Shaav.

T'Shaav nods to the snake. "By all means, Commander Ki'vek."

Ki'Vek makes her usual partings, then heads back to the operations section.

Lieutenant Commander Ki'Vek goes Out.

Worthington nods. "Indeed," he says. "We will do our upmost to find out who the culprit is. We have a lot of digging to do. I'm still awaiting any final reports out of medical, but in the meantime, I need to start interviewing people down in engineering."

T'Shaav nods, still pensive. "Carry on, Commander."

Worthington nods, rises, salutes, and leaves.