After the Apocalypse

“How about a cricket? How about a jellyfish? A sponge?”

“If we don’t know if DMS is conscious or not, then we pretty much have to assume it is,” Sydney said. “And if we back it up, we might kill it.”

Damien shook his head. “How can we kill it?”

Sydney said, “Because we will stop it and reinstall it.”

“So you think that the interruption of consciousness might be enough to kill it? You think it has a soul? Its consciousness is in the code. Its code and body are unchanged. If someone has a heart attack and you shock them back, they come back as themselves. Your body is you. DMS’s software and hardware is DMS.” Damien was very pleased with himself.

Sydney was pretty sure it wasn’t so simple. It wasn’t until the next day that she thought of a cogent argument, which was that organic systems are a lot less fragile than computer systems. Organic systems decay gracefully. Computer systems break easily. DMS was much more fragile than an animal. But that night she couldn’t think of anything.

The problem with poking the system to see if it was aware was to figure out what it could sense. DMS didn’t see or hear, didn’t eat or breathe. Its “senses” were all involved in interpreting data. So the “poke” needed to be something that it would recognize, that it would sense. And the poke needed to be something that it would sense as meaningful. The idea that Damien came up with was to feed it information in a way that it could recognize was a pattern but that wasn’t a pattern it expected.

DMS had several systems which regulated input and scanned for patterns. Epidemiological information was generated from ER, patient intake, and pharmaceutical information. Maintenance issues were anticipated from electrical usage. They picked the maintenance system, since DMS had been screwing with the electrical system, and input a thousand-character string of ones and zeroes. It was, Damien said, boring but clearly a pattern.

Sydney wasn’t sure it was the right kind of pattern. “Basically,” she said, “It’s like I flipped a coin and it came up heads a thousand times.”

“Yeah,” Damien said.

“If I did that, I might assume there was something wrong with the coin. But I wouldn’t assume aliens were trying to communicate with me through my coin toss.”

“DMS doesn’t have to recognize that we’re trying to communicate with it,” Damien explained. “It just has to notice that the information is not junk.”

DMS kicked the entry into the garbage column on its maintenance report.

They had written a program to do the entry, so they ran the program a thousand times.

If DMS noticed, it didn’t think anything of it. One thousand times it kicked the entry into the junk portion of the report.

“I don’t think it knows what we’re doing,” Sydney said. “You know, analyzing reports may be unconscious.”

“I don’t think consciousness is an issue here,” Damien said. “Remember the shark.”

“Okay. Maybe it’s involuntary. The shark has control over what fish it goes after, but it doesn’t have control over its kidney function. It doesn’t choose anything about kidney function. Maybe maintenance is involuntary.”

Damien looked at her. She thought he was going to say something dismissive, but after a moment he said, “Well, then, what parts of it would be voluntary?”

Sydney shrugged. “I don’t know. Epidemiologist, maybe. But we can’t screw too much with that.”

Screwing with maintenance was bad enough. But data from LEGBA went directly to the CDC and National Institute of Health through a weird subroutine called DAMBALLAH which did complicated pattern recognition and statistical stuff. Sydney worried about a couple of things. One was causing a system crash that meant someone ended up dying. The other was getting them in trouble with the CDC or the government. Of the two, she would have to choose getting in trouble, except she could imagine bad data to the CDC might mean someone ended up dying anyway. In her mind it unfolded: bad information seems to indicate a critical alert, Marburg virus reports in New York City seem to show that someone got off a plane and infected people with a hemorrhagic fever. The false epidemic pulls resources from a real outbreak of Legionnaires’ disease, and people who would have lived now die because she and Damien were poking DMS.

She thought Damien would say to poke DAMBALLAH. Damien seemed a lot less concerned about getting in trouble than she did. She had a theory that the fear of getting in trouble was what made her not as good a programmer and that, in fact, it was all linked to testosterone, and that was why there were more guy programmers than women. It was a very hazy theory, and she didn’t like it, but she had pretty much convinced herself it was true, although she couldn’t bear to think of sharing it with anybody, because it was a lot better to think that there were social reasons why girls didn’t usually become code monkeys than to think there were biological reasons. But right now she was pretty sure that she would say stop and Damien would say go.

He surprised her. “Not DAMBALLAH. You think that DMS might be fucking with the outputs on DAMBALLAH?”

She shrugged. “I don’t know.”

“Maybe tomorrow we can try to check that.”

Tomorrow was tough, because when Sydney got home she was too keyed up to sleep, and she was up until almost four reading a book called Dead Until Dark. The book had been recommended to her by Addy, her college roommate from junior and senior years. It was the first in a series about a paranormal detective and had been just about the most perfect thing to read after coming home from a failed attempt to prove that a computer system was aware.

She was still worried about DAMBALLAH and whether DMS was doing weird things with the epidemiological reports. DAMBALLAH was a complicated system. It made decisions about reporting data. She couldn’t easily check its decisions—that was the point. Every two weeks they got a report from the NIH and the CDC about epidemiological trends, and if there was something new that the CDC was looking for, say an outbreak of shigella in preschools in the South, there was an elaborate way they entered additional parameters to DAMBALLAH’s tracking system. The CDC and the NIH also sent them error reports and WRs. WRs were to correct when DMS was reporting something that wasn’t important or was overreporting. The result was the DMS “learned” epidemiology.

This made it difficult to know if DMS was screwing with the numbers. If DMS did report something, like an epidemic of onchocerciasis (parasitical river blindness) in Seattle, that would get caught fast. But if DMS were just, say, overreporting the incidence of TB in Seattle, that might not. Sydney ran an ep report and started working on a program that would check the DAMBALLAH database for raw numbers of cases of illnesses that DMS was tracking for the CDC, to see if she could spot anything that looked weird.

Damien had been cranky and quiet all day. Then at 3:17, the lights at Meridian Health in Macon, Georgia, did the wave. The same thing that had happened the day before happened again, except this time in reverse order, ending with DM Kensington Medical. They found out it was happening again when the power outage rolled through headquarters early in the sequence. Within minutes Tony, their boss, was screaming at people to stop it, but they decided that stopping it would be more complicated than letting it run its course, so they called the last three hospitals and gave them a heads-up.

Damien was set to write code that would catch the beginning of the sequence and stop it from happening. Together, he and Sydney pored over the tangle of spaghetti that was SAMEDI code. The next day, at 3:17 they could at least switch the electrical systems to maintenance mode for the time it took for DMS to run through its sequence. (According to the log, it would have started with DM Kensington again.) Hospitals bitched about slowdowns in the DMS while SAMEDI was not running. It shouldn’t have affected everything else, but DMS was so weirdly interconnected that SAMEDI had evidently been doing something that optimized read/write functions. Which SAMEDI wasn’t supposed to do at all.

“Why 3:17?” Sydney asked. “Why the electrical system?”

Damien shrugged. They were poring over printouts, looking for ways to, in Damien’s words, “build a box around the bug.” Tony was alternating between asking them if they’d found it yet and telling the head of operations that the admin IT team was doing a great job and to get out of their faces and let them work. Tony was a screamer, but as far as he was concerned, the only one allowed to scream at his people was him.

Mostly Sydney noticed that Damien did not seem to be “in the zone.” He had talked a lot about being “in the