Mytholder (mytholder) wrote,
Mytholder
mytholder

Now We Are Here, General Transmission #15

Like a previous message, this is passed on secretly. It's from Cogburn, one of the senior security staff.

Oh, and a few people were wondering about Eugenie Kale, who was mentioned in Cogburn's last message. Nothing official has been said yet, but there are rumours about someone having died when the heat shield collapsed during the first aerobraking. Others might know more...


As agreed, we're going to take this opportunity to shut Propero down temporarily and give the old computer a solid overhaul, to ensure that the glitches and odd behaviour we've seen aren't the results of sabotage. However, we need to deal with the Flight crew, who have an unreasonable attachment to the AI and don't trust the rest of us.

We've got several options, but they'll all need the co-operation of the crew. We've designated these five plans Operations SANDMAN 1 to 5.

SANDMAN 1: We seize the entire St. Andrew. This will require the deployment of all our security forces, and we may need to bring troops up from the surface too. We take control of all key systems, and place the Flighters and any other suspect crew in confinement in the hydroponics bays until we've established that the ship is safe.

SANDMAN 2: Propero's computer cores are all located along the zero-g drive spine, and the spine's connected to the rest of the ship by the axial links, of which there are thirty-six. We send a team down to the spine, and take control of several axial links. We then override the controls for the other links, sealing them off leaving us in control of the spine.

SANDMAN 3: As above, but we don't bother with taking control of the whole spine, just the computer cores. We use a much smaller, more covert team, with a larger reserve force ready to go in if problems arise.

SANDMAN 4: We get Engineering to send in a team, tagged as maintainence. When they're at the core, they quickly turn Prospero off. It's done before anyone notices there's a problem.

SANDMAN 5: We vet the flight crew for loyal members, then confide our concerns to them. Given Dr. Tupper's assessement of them, I feel that this would be a mistake.

What Security Measures Should Be Used?

Seize the ship by force; declare martial law
2(7.7%)
Seize only the computer cores
0(0.0%)
Send a small team in to secure the core, using force only if necessary
10(38.5%)
Attempt a covert shutdown without seizing control of any sections of the ship
9(34.6%)
Inform the Flighters of our concerns first
5(19.2%)

Tags: now we are here
Subscribe

  • Fish Typo, How I Have Missed Thee

    From High Guard: 'The size of spacecraft allowed depends on the size of the docking clam.' In other news, In Bruges is fantastic. Beautiful…

  • Typo of the Day

    Being "attacked by an undead monster" might cost you 1d4 Sanity. Being "attached by an undead monster" is probably worth a lot more Sanity loss...

  • Typo of the Day

    A Corpse Tree might attack a victim with a Vampiric Root, but is unlikely to use a 'Vampiric Roo' instead. You only find Vampiric Roos in very silly…

  • Post a new comment

    Error

    default userpic
    When you submit the form an invisible reCAPTCHA check will be performed.
    You must follow the Privacy Policy and Google Terms of use.
  • 13 comments

  • Fish Typo, How I Have Missed Thee

    From High Guard: 'The size of spacecraft allowed depends on the size of the docking clam.' In other news, In Bruges is fantastic. Beautiful…

  • Typo of the Day

    Being "attacked by an undead monster" might cost you 1d4 Sanity. Being "attached by an undead monster" is probably worth a lot more Sanity loss...

  • Typo of the Day

    A Corpse Tree might attack a victim with a Vampiric Root, but is unlikely to use a 'Vampiric Roo' instead. You only find Vampiric Roos in very silly…