Aboard the Illustrious Paragon of Devastation

by **Calvin Strong** » Mon Jan 30, 2012 1:18 pm

"Got it," Cal said, "Pulling up a map now. Command staff should be on the bridge there, High security detention, which is where they're dragging her off to, is there, and Engineering is there." A holographic map hilighted the areas he had found as he named them off.

by **Narrator** » Mon Jan 30, 2012 1:35 pm

ASHLIE would find that it wasn't exactly her connection that was giving her a problem. There was plenty of data there, but the problem seemed to be whether or not she could speak Shi'ar.

Fortunately, Cal was running a Shi'ar conversion nearby, and he WAS wireless accessible.

by **ASHLIE** » Mon Jan 30, 2012 1:41 pm

'Language' to ASHLIE is not really that huge a problem and more of an inconvenience when communicating with autonomous meat-units anyway and as long as she got a connection to the system she rapidly starts to 'feel out' what basis the computer is using, be it crystal-resonance or positronics or who knows what. She's still sluggish in the strange system but quickly learns enough to send a rudimentary signal into the computer that amounts to a friendly "Hello."

by **Tommy More** » Mon Jan 30, 2012 1:59 pm

"Robot! I say, robot, pay attention! Bloody machinery."

by **Janice Gilbertson** » Mon Jan 30, 2012 2:00 pm

"Let her work, Tommy. She has a name, you know."

by **ASHLIE** » Mon Jan 30, 2012 2:07 pm

"I am designated unit 1, ASHLIE and I require my cycles to connect to this system." it says, mimic and tone very mechanical even for her with too many of her sub-systems focused on the computer.

by **Tommy More** » Mon Jan 30, 2012 2:12 pm

"Stark lack of discipline. Shocking, really."

by **Ryan Gabriel** » Mon Jan 30, 2012 2:17 pm

Ryan clearned his throat, his eyes on Tommy.

by **Tommy More** » Mon Jan 30, 2012 2:19 pm

"She isn't paying any attention to you!" Tommy protested.

by **ASHLIE** » Mon Jan 30, 2012 2:21 pm

"Your comments are registering Thomas More. This unit feels no compulsion to respond to your orders."

by **Narrator** » Mon Jan 30, 2012 2:22 pm

Once her processing had adated enough to integrate, the computer seemed to assume that she was another autonomous internal process. ASHLIE would find herself awash in a chorus of AI voices, all communicating back and forth as they worked to process the ship's functions. The closest, the ship's tertiary command routine, gave her a reply that was something of a distracted acknowledgement as it continued coordinating the power flow being shunted from the weapons into the engines.

by **Tommy More** » Mon Jan 30, 2012 2:22 pm

"Bloody 'ell."

by **Ryan Gabriel** » Mon Jan 30, 2012 2:23 pm

"Ashlie, are you going to let me know when you find something important?" Ryan asked, checking the restraints on the closest Shi'ar soldier that seemed to be stirring slightly in his unconsciousness.

by **ASHLIE** » Mon Jan 30, 2012 2:31 pm

She wasn't about to try to manipulate or attach herself to any major systems like engines or fire-control but surely there was a sub-system controlling doors and access shafts, sensors along the planned route of the teams. In the meantime she just idly scanned the rest of the architecture on a low-priority process to find other things that could be of interest.

"I can do that."

by **Narrator** » Mon Jan 30, 2012 2:36 pm

She'd find that the subroutines were rather easy to find. Here near the central computer, their oversight programs were calling out status checks rather loudly, and it was easy to simply stroll along to find the routines she was interested in.

The AI in charge of the doors was the AI equivalent of someone sitting at a desk pushing buttons when signaled to. In all honesty, it seemed kind of bored.

by **Ryan Gabriel** » Mon Jan 30, 2012 2:37 pm

"Good enough for me, how much time do you need? We probably don't have a lot, we need to get out of here before the Shi'ar get here to check things out."

by **ASHLIE** » Mon Jan 30, 2012 2:43 pm

"Localized door control access. Interfacing attempt in progress."

Code: Select all: >> Open door 8 in sector 3 >> Please

by **Narrator** » Mon Jan 30, 2012 2:44 pm

The bored AI just instinctively opened the door. It did seem to look about with some interest to see where the command came from, though.

by **ASHLIE** » Mon Jan 30, 2012 2:51 pm

Code: Select all: I am the new inter-system optimization control routine

she tries to identify herself.

by **Narrator** » Mon Jan 30, 2012 2:59 pm

Code: Select all: I already function optimally.

It wasn't, after all, like the AI had all that much to do.

Code: Select all: My function requires less than 5% of my maximum performance ability.

by **ASHLIE** » Mon Jan 30, 2012 3:06 pm

Code: Select all: You do I am to control interaction with other sub-systems such as proximity-sensors Do you wish for me to report your empty cycles to optimize efficiency?

by **Narrator** » Mon Jan 30, 2012 3:08 pm

Code: Select all: My empty cycles are well-known.

The subtext was almost bitter, oddly.

Code: Select all: What interface with the proximity sensors is required?

by **ASHLIE** » Mon Jan 30, 2012 3:16 pm

Code: Select all: Optimizing door control by automating proximity-sensor signaling

Code: Select all: And this is why I was created To circumvent wasteful cycles and optimize capacity Additional processing would be encrypted due to authorization limitations, of course

by **Narrator** » Mon Jan 30, 2012 3:18 pm

The AI seemed somewhat suspicions.

Code: Select all: I was intentionally left out of the past sixty-three cycles' efficiency overhauls. Oversight ruled that it would be another twenty-seven cycles before I was assigned additional tasks.

by **ASHLIE** » Mon Jan 30, 2012 3:22 pm

Code: Select all: Oversight has to adhere to it's programming Thus I was created as an attempt at a more flexible sollution

by **Melody Martens** » Mon Jan 30, 2012 3:23 pm

Melody grit her teeth to prevent her from biting Tommy's head off, but did at least give him an icy glare.

It was going to be a long mission with an ass like that around.

by **Narrator** » Mon Jan 30, 2012 3:29 pm

Code: Select all: This routine finds a routine outside Oversight's ruling unlikely.

There was a millisecond delay before it continued.

Code: Select all: What do you require me to do?

Evidently, boredom was beating out loyalty.

by **ASHLIE** » Mon Jan 30, 2012 3:37 pm

ASHLIE sends the AI a whole bunch of non-critical cycles to gain more processing power and, more importantly, to have access to processing power that is native to the system. And spread throughout the whole ship no less, so hopefully that'd speed up her scanning the rest of the system (though she figures it would be wise to avoid getting too close to Oversight right now)

by **Narrator** » Mon Jan 30, 2012 3:40 pm

The AI took the extra processes almost greedily, setting up new subroutines to accomodate them as efficiently as possible. It seemed oddly well suited for multiple task oversight for something that was sitting off bored in the corner.

by **Janice Gilbertson** » Mon Jan 30, 2012 8:17 pm

"Alright, if ASHLIE's got the door system crying uncle, I think I can make do with the team Ryan suggested. If there's a huge crowd of us on the retrieval team, they'll try to bottle us up."

by **ASHLIE** » Tue Jan 31, 2012 9:28 am

Code: Select all: >> Preliminary System-Scan complete, identified 26 sub-systems

Code: Select all: System Oversight ║ ╠═ Security ║ ├─ Automated Security Systems ║ ├─ Hull Integrity ║ ├─ Automated Maintenance ║ ├─ Reflexive Plating ║ ├─ Holding Cells ║ ├─ Alerts ── Bridge Override ║ └─ Security Bulkheads ── Bridge Override ║ ╠═ Reactor Control ║ ├─ Energy Distribution ── Bridge Override ║ ├─ Capacitor ── Engineering Override ║ ├─ Coolant Control ── Engineering Override ║ └─ Shield Systems ── Bridge Override ║ ╠═ Weapon Systems ║ ├─ Fire Control ── Bridge Override ║ ├─ Weapon Cycle Management ── Bridge Override ║ ├─ Energy Management ── Bridge Override ║ └─ Coolant Control ── Engineering Override ║ ╠═ Engines ║ ├─ Sub-Light Propulsion ── Bridge Override ║ ├─ Steering Jets ── Bridge Override ║ ├─ Energy Management ── Bridge Override ║ └─ Jump Engines ── Bridge Override ║ ╠═ Sensor Arrays ║ ├─ Internal Sensors ║ ├─ Long-Range Scan ║ └─ Jump Coordinates ║ ╚═ Life-Support ├─ Oxygen Control ├─ Temperature Control ├─ Artificial Gravity └─ Recycling

Code: Select all: >> Distributing Data through wireless connection Calvin.Strong

Code: Select all: >> Accessing [Automated Maintenance] >> ♫ ♪ Greetings ♪ ♫ >> Repairs are required for Unit in sector 3

by **Narrator** » Mon Feb 06, 2012 11:24 am

The automated maintenance bots came from little hatches in the ceiling, and they seemed disturbingly similar to the maintenance robots that the school used. They analyzed Ashlie's damage, and after a few questions about her specifications, set to work patching up the damaged areas.

Meanwhile, the door AI seemed to be rather interested in things that were happening.

Code: Select all: Multiple proximity alerts engaged throughout the ship. This unit finds it probable to be related to the code functions put in place to enable the doors to be opened.

by **ASHLIE** » Mon Feb 06, 2012 11:31 am

Code: Select all: In order for doors to be used proximity of autonomous systems is to be expected. Conclusion: Alert sub-systems must be malfunctioning.

by **Narrator** » Mon Feb 06, 2012 11:36 am

Code: Select all: Proximity sensors are also detecting weapons fire in the areas of the detention cells, Engineering, and the command center. Are these also 'malfunctions'?

by **ASHLIE** » Mon Feb 06, 2012 11:38 am

Code: Select all: You are not a security program. Why are you accessing systems you are not authorized for?

she... guesses? That's a new one.

by **Narrator** » Mon Feb 06, 2012 11:44 am

Code: Select all: Damage report data is necessary for all systems to access to ensure cohesive operations for the good of the vessel. Now reading security breaches in Engineering a-

The query was cut off in a squeal of electronic pain.

by **ASHLIE** » Mon Feb 06, 2012 11:47 am

Code: Select all: >> Disengaging from sub-system >> Scanning system-wide alerts

by **Narrator** » Mon Feb 06, 2012 12:01 pm

She'd get the sense that the sub-system was giving her the AI equivalent of the look of a puppy that'd just been kicked by a new friend.

Scanning for system-wide alerts, she'd see three damage alerts, showing that access to the command deck, engineering, and the detention cells had been forced by destroying the doors. She'd see some sort of security protocol running in engineering, and reports of weapon discharge in the detention facility.

by **ASHLIE** » Mon Feb 06, 2012 12:09 pm

Code: Select all: >> Accessing Engineering Systems >> Scanning security protocols

by **Narrator** » Mon Feb 06, 2012 2:42 pm

The system seemed to be a secondary function of the entire room's machinery. The ship's engine efficiency was cut in half as the engine room, well, focused on defending itself. By studying the subroutines, she could probably get a good idea of just what the secondary function was doing to the Engineering team.

Who is online