Бесплатный фрагмент - The Sixth Scenario

Chapter 1 — The Incident That Already Happened

Nora Keene knew what the woman on the television was going to say before she said it, because three weeks earlier, Nora had written almost the same words into an emergency simulation that was never supposed to leave her company’s secure network.

The woman stood behind a conference podium, one hand gripping a microphone while the other pressed against the polished wooden surface. Behind her, a projection screen displayed the logo of the Northwest Facilities Leadership Summit. The image was shaky, recorded on somebody’s phone, and a caption at the bottom of the television identified the location as the Harbor House Hotel in Bellport, Washington.

“Please remain in the conference hall while hotel security investigates a situation in the east service corridor,” the woman announced. “We ask everyone to stay calm and wait for further instructions.”

Nora stopped halfway between her kitchen and the living room, holding a bowl of soup she had reheated twice and still hadn’t eaten.

The words were not identical to those in her simulation. They were close enough to make her uncomfortable, though, and the reference to the east service corridor bothered her more than it should have.

She stood listening as the news anchor explained that a security incident had interrupted the afternoon conference and triggered an evacuation of approximately two hundred attendees. Police were investigating a report of a suspicious item near one of the hotel’s service entrances. No fatalities had been reported, although three people had been evaluated by emergency personnel following the evacuation.

The footage cut to a second recording, taken from farther back in the conference hall.

A man near the aisle was arguing with someone Nora couldn’t see. Several attendees were already standing, despite the instruction to remain seated. The woman at the podium spoke briefly to a member of the hotel staff, then returned to the microphone.

“Your attention, please. We’re going to ask everyone to leave through the western exits. Please follow the directions of hotel personnel and do not use the eastern hallway.”

Nora placed her soup on the nearest table.

She had written that sequence too.

Not the exact announcement, of course. Real people rarely followed scripts precisely, even when someone handed them a printed copy. But the structure was remarkably familiar: an initial instruction to remain in place while security checked an eastern service corridor, followed several minutes later by an evacuation through the opposite side of the building.

There were good reasons for the resemblance. Hotels operated according to established emergency procedures, and the scenarios Nora designed were based on plausible failures of those procedures. A security concern could lead to a shelter-in-place order, and changing circumstances could force organizers to reverse their instructions.

She had spent fourteen years studying precisely that kind of behavior.

Even so, she remained standing.

The anchor resumed speaking, explaining that conference attendees had complained of contradictory instructions and delays in leaving the building. A hotel representative had declined to comment on whether the suspicious item had posed a genuine threat.

Nora reached for the remote and increased the volume.

A reporter appeared outside the hotel, with police vehicles and a line of conference attendees visible behind her.

“Authorities say the first emergency announcement was made at approximately five seventeen this afternoon,” the reporter said. “The order to evacuate followed about six minutes later, after hotel security received additional information.”

Six minutes.

Nora remembered writing seven into the original scenario.

That difference should have reassured her. Instead, it made her want to find the document.

She looked toward the hallway, where her work bag rested against the wall beside a pair of shoes she hadn’t bothered to put away. Her laptop was still inside, along with the notebook she’d carried into four meetings that day.

The sensible response would be to finish dinner, take a shower, and forget about the television.

She was tired. Her shoulders ached from sitting too long, and the last meeting at Calder Response had ended in a disagreement over how much uncertainty a client could realistically be expected to tolerate during a training exercise. Nora had argued that removing difficult decisions from a simulation defeated its purpose. Her colleague had argued that the client was paying for something its staff could complete without feeling humiliated.

They had compromised in a way that satisfied neither of them.

Ordinarily, Nora would have continued thinking about the disagreement during her commute home, taking apart the arguments and searching for the one she should have made. Tonight, however, she had been looking forward to an evening in which nobody required her to anticipate the consequences of anything.

She had even bought soup from the little grocery store near her apartment instead of preparing dinner.

Now she found herself mentally reconstructing a simulation she had delivered three weeks ago.

On television, the reporter continued her summary. Nora barely heard her until the station replayed the footage from inside the conference hall.

The camera swung past a row of empty chairs and settled briefly on the podium.

Something bright red was leaning against the lower edge of the platform.

Nora took two steps toward the television.

The image moved away before she could make out the object properly.

She pressed the button to rewind, forgetting for an instant that she was watching a live broadcast through a streaming television app. The program paused, then allowed her to move backward through the buffered footage.

She found the relevant sequence and played it again.

A narrow red umbrella stood beside the speakers’ podium, its curved handle resting against the wooden riser. The fabric had been gathered loosely around the shaft, leaving a small triangular fold sticking out near the bottom.

Nora stared at it until the footage changed.

Then she rewound once more.

She hadn’t simply described an umbrella in her simulation. She had specified a red umbrella leaning against the speakers’ platform, an ordinary object that might distract witnesses from remembering the more consequential details of an emergency.

She remembered the paragraph because she had written it near midnight, after deciding that the exercise needed a small, irrelevant detail to make the imaginary scene feel less mechanical.

She had chosen red because it would stand out against the neutral colors of a hotel conference room.

She had placed it beside the podium because that was where a distracted event coordinator might leave something before addressing a crowd.

The object had no role in the emergency itself.

It existed because Nora had imagined it.

And now she was looking at it on the evening news.

She sank slowly onto the edge of the couch, holding the remote between both hands.

A red umbrella wasn’t rare, particularly in western Washington during October. The conference had taken place at a coastal hotel, where attendees might have brought umbrellas indoors and left them wherever they could find space.

The woman at the podium might simply have been carrying one.

The announcements followed recognizable emergency procedures.

Six minutes instead of seven could be an ordinary coincidence.

Nora could explain every detail separately.

What troubled her was that she had to explain all of them.

She left the television paused on the image of the podium, retrieved her laptop, and carried it to the dining table.

For the first time that evening, she no longer felt tired.

The simulation was filed under a project name that meant nothing to anyone outside Calder Response.

Project C-214: Conference Venue Response Assessment.

Nora remembered the number because she’d argued with the project coordinator about its classification. He wanted to place it among routine evacuation exercises, while she believed the central problem involved the management of uncertain information. Emergency planning was not simply about knowing where the exits were. It was about recognizing how quickly a reasonable decision could become dangerous when the situation changed.

The client was a regional hospitality training consortium. Calder Response had been commissioned to produce several hypothetical crisis scenarios for its professional-development program, each designed to test decision-making among hotel managers and conference organizers.

The scenarios were confidential, but not because they contained government secrets or extraordinary technical information. Calder Response maintained strict access controls because clients paid for original exercises and expected their assessment materials to remain private.

Nora entered her credentials and completed the additional verification required to access the company’s remote workspace.

The connection took longer than usual.

While she waited, she glanced at the frozen television image.

The umbrella was still there.

She disliked the way the object seemed to have become the center of the room, as though the people and the unfolding emergency had been reduced to background decoration.

The workspace opened.

She found the project and selected the final submission, which was dated September 22.

Three weeks before the incident.

She checked the date again, although she knew perfectly well when she’d completed the work. It had been a Tuesday, and she’d delivered the final materials shortly before leaving for an appointment she nearly missed.

The file’s approval history confirmed that the scenario had been submitted to the project coordinator at 4:38 that afternoon.

Nora opened the document.

The fictional hotel was called Mariner House, located in an invented coastal town. Its floor plan was intentionally generic, with conference spaces, service corridors, and exits arranged to resemble a typical midsize hotel. The purpose was to create a training environment that could be adapted to different properties.

She scrolled past the background information and found the opening sequence.

At 5:15 p.m., during the afternoon session of a professional conference, hotel security receives a report concerning an unidentified item near the eastern service entrance.

Nora stopped reading.

The news reporter had placed the real incident at approximately 5:17.

That was close, but it wasn’t the detail that mattered most. Security incidents were frequently discovered during transitions between scheduled conference sessions, when corridors became crowded and staff members moved equipment through service areas.

She continued.

The event coordinator announces that attendees should remain in the conference hall while security assesses the situation. Conflicting information reaches hotel management, creating uncertainty about whether the eastern corridor can remain in use.

Nora leaned closer.

Seven minutes after the initial announcement, the coordinator reverses the instruction and directs attendees toward the western exits. The sudden change causes confusion among staff and conference guests.

She read the paragraph again, more slowly.

The correspondence was striking, although she still lacked the kind of independent information required to establish whether the events had unfolded exactly as reported. Television coverage condensed incidents, simplified explanations, and sometimes presented preliminary statements that would later be corrected.

She opened a blank document and created two columns.

In the first, she listed details from the simulation. In the second, she recorded only what had been confirmed in the broadcast.

She had barely entered the first three observations before she noticed how carefully she was choosing her words.

Similar timing, she wrote, rather than same timing.

Apparently comparable announcements, rather than identical announcements.

Umbrella visible near podium, rather than umbrella deliberately placed in matching position.

The distinctions mattered.

Nora had built her career on persuading people not to confuse a plausible explanation with a proven one. She wasn’t going to abandon that principle simply because the evidence made her uncomfortable.

She replayed the report and checked the captions for the hotel’s name.

Harbor House Hotel, Bellport.

She had never worked with the hotel, as far as she could remember.

It wasn’t one of Calder Response’s regular clients. She searched her project directory and found no previous exercises involving the property.

That gave her a little relief.

The name of the conference, however, was more difficult to dismiss.

The Northwest Facilities Leadership Summit was exactly the kind of professional gathering the training consortium had wanted to simulate. Its organizers would have had reason to plan for security incidents and emergency evacuations.

Perhaps the hotel had used ordinary industry guidance, some of which Calder Response had incorporated into its own materials.

Perhaps the coordinator had received training from an instructor familiar with the same procedures.

Perhaps the apparent similarities reflected an established professional standard rather than any connection to Nora’s document.

She opened a browser tab and searched for publicly available information about the conference.

The event website contained a schedule, a speaker list, and photographs from previous years. The summit brought together building managers, facilities directors, security consultants, and hospitality professionals from several western states.

An afternoon session was listed for five o’clock.

Emergency Communication in High-Occupancy Buildings.

Nora stared at the title.

She had found something that initially looked meaningful, but there was an entirely innocent explanation. The conference itself focused partly on emergency management, making an incident of this kind especially likely to generate familiar language and behavior.

She added the information to her notes under a heading marked Possible explanations.

The act of writing it down helped.

This was how she worked when clients became convinced that something had gone terribly wrong. She separated observations from assumptions and built a timeline that could survive scrutiny.

She returned to the simulation.

The umbrella appeared on page eleven, in a section describing incidental environmental details.

At the beginning of the exercise, a folded red umbrella rests against the left side of the speakers’ platform. The object is unrelated to the security incident but may feature in witness recollections because of its distinctive color and placement.

She remembered adding the sentence after reviewing an earlier draft that felt too orderly. Real emergencies were full of distracting details. People remembered odd things: a dropped cup, a broken sign, somebody’s coat hanging from a chair. Those details often became disproportionately important afterward, precisely because memory was imperfect.

She had not anticipated that the umbrella itself would become the detail she couldn’t stop thinking about.

Nora switched back to the news footage and studied the image.

The umbrella stood on the left side of the platform as seen from the audience.

She checked the wording in her document.

Left side.

For a moment, she almost convinced herself that she had discovered something conclusive.

Then she remembered that the description could be interpreted from different perspectives. She hadn’t specified whether left meant the audience’s left or the speaker’s left.

It was a minor ambiguity, one she would ordinarily have corrected during review.

She sat back in her chair.

Her own imagination was making the evidence stronger than it actually was.

The red umbrella was unusual, but not impossible. A training exercise about a conference emergency resembled a real conference emergency. Nothing about that violated the laws of probability.

Nora knew this.

She also knew that if a client presented her with the same collection of observations, she would advise them to preserve the documents and examine the circumstances more carefully.

The clock on her laptop read 9:14 p.m.

She had spent almost forty minutes investigating what might be a coincidence.

Her soup was cold again.

She considered calling somebody, then dismissed the idea because she could already hear the conversation.

You’re telling me an umbrella appeared in the wrong place?

She reached for her phone anyway.

There was one person at Calder Response who would understand why the sequence bothered her, even if she thought Nora was being unnecessarily dramatic.

Elaine Mercer had supervised the simulation team for almost six years. She was practical, direct, and capable of disagreeing with Nora without turning an ordinary professional argument into a personal dispute.

She also knew the C-214 project.

Nora found Elaine’s number, hesitated, and called.

Elaine answered on the fourth ring.

“If the client has changed its mind about the assessment criteria again, I’m officially unavailable until morning.”

“It’s not the client.”

There was a pause, followed by a faint rustling sound.

“Nora? What’s wrong?”

“Have you seen the news about that conference in Bellport?”

“Which conference?”

“The facilities summit at the Harbor House Hotel. There was some kind of security incident this afternoon.”

“I caught part of it while I was making dinner. Why?”

Nora looked at the document open on her laptop.

“I think it resembles one of our exercises.”

Elaine waited.

“C-214,” Nora added. “The conference venue assessment we delivered to the hospitality consortium last month.”

“All right.”

“The announcements, the order of the evacuation, the location of the security concern. Several details are very close.”

“Close in what way?”

Nora explained, trying to keep the chronology clear. She described the initial announcement, the later reversal, and the similarities between the fictional situation and the news report.

Elaine listened without interrupting.

When Nora finished, her supervisor said, “That doesn’t sound especially surprising. We build these things around situations that could actually happen.”

“I know.”

“And hotel evacuation procedures aren’t exactly secret. There are only so many ways an incident like that can unfold.”

“There’s another detail.”

Nora hesitated because saying it aloud made her feel foolish.

“I put a red umbrella beside the podium in the exercise. It’s in the footage from the hotel.”

“A red umbrella?”

“Yes.”

“What does the umbrella have to do with the incident?”

“Nothing. That’s why I remember it.”

Elaine was quiet for a moment.

“Was it raining in Bellport?”

Nora glanced toward the television.

“I don’t know.”

“Well, it’s October on the Washington coast. I’m guessing you wouldn’t have to look far to find an umbrella.”

Despite herself, Nora smiled faintly.

“That’s what I told myself.”

“Listen, I understand why this caught your attention. You spend weeks building one of these scenarios, and then something similar happens in real life. Of course it feels strange.”

“It’s more than a general resemblance.”

“Maybe. But right now you’ve got a training document and a television report. We don’t know enough about the actual incident to make a meaningful comparison.”

Nora watched the reporter speaking outside the hotel. The footage had been replaced by a discussion between the anchor and a security consultant, who was explaining the difficulties of managing crowds when instructions changed.

Elaine was right about the limitations of the evidence. Nora resented how relieved she felt to hear somebody else say it.

“What would you do?” she asked.

“Put together a short summary. Nothing dramatic. Save it in the project workspace, and we can look at it tomorrow.”

“Should we notify the client?”

“About what? A possible coincidence?”

Nora rubbed the bridge of her nose.

“No. Not yet.”

“If there’s evidence our materials were used somewhere they shouldn’t have been, we’ll deal with it. But I’d rather have something concrete before we start asking questions.”

“Fair enough.”

Another pause followed.

“You sound exhausted,” Elaine said.

“I am.”

“Didn’t you stay late again?”

“Only until seven.”

“Nora, seven is late when you got there before eight.”

“I had work to finish.”

“You always have work to finish. That’s not the same thing as having to finish it tonight.”

Elaine’s voice softened.

“Go eat something. Get some sleep. Whatever happened in Bellport, you aren’t going to solve it from your dining table.”

Nora glanced at the abandoned soup.

“I’ll send you my notes in the morning.”

“Good. And try not to spend the entire night thinking about umbrellas.”

When the call ended, Nora placed the phone beside her computer and sat for a while without moving.

Elaine’s response had been exactly what she should have expected: sympathetic, sensible, and professionally cautious.

It was also unsatisfying.

Nora knew that feeling. She experienced it whenever a complicated situation resisted the clean explanation she wanted to give it.

Her profession had trained her to imagine consequences before they happened. Clients appreciated that talent when it helped them avoid mistakes, but they sometimes grew uncomfortable when she continued identifying weaknesses after everyone else was ready to declare a project complete.

Elaine had once told her that she treated uncertainty as a personal insult.

Nora had laughed at the time.

She hadn’t entirely disagreed.

She stood, took her soup back to the kitchen, and emptied it into the sink. The thought of eating had disappeared. Instead, she poured a glass of water and carried it to the table.

The television continued playing quietly.

Police had apparently reopened the hotel’s western entrance. The reporter now stood in front of a revolving door, explaining that investigators had not yet determined whether the suspicious item represented a deliberate threat or a misunderstanding.

Nora wanted to know who had discovered the item, what information security personnel had received, and why the evacuation instructions had changed.

She recognized the impulse. She wanted enough facts to make the uncertainty disappear.

That had always been her preferred solution.

Years earlier, when she was still learning how professional investigations worked, somebody had assured her that a discrepancy in an emergency report was insignificant. She had accepted the explanation because the person giving it possessed more experience and authority than she did.

The memory arrived unexpectedly, bringing with it the familiar discomfort of a question she had never entirely resolved.

She pushed it aside.

The situation in Bellport was not the same. She had no reason to believe anyone had falsified a report, concealed information, or done anything improper.

A coincidence did not become evidence of wrongdoing merely because it reminded her of an old mistake.

She closed the news application and returned to the project workspace.

Elaine had asked for a summary. Nora could prepare one now, without drawing conclusions, and send it in the morning.

She opened a new note within the C-214 project and began recording the similarities she had identified.

The process calmed her.

Writing required decisions about what belonged in the record and what did not. It forced her to confront the difference between what she remembered and what she could demonstrate.

She entered the date of the original submission, then added links to the publicly available reports she had examined.

At the bottom, she wrote:

Preliminary assessment: Several notable similarities exist between the fictional scenario and the reported incident. Current information is insufficient to establish any relationship. Further comparison would require confirmation of the actual event chronology and an understanding of whether relevant exercise materials were distributed outside authorized channels.

She read the paragraph twice.

It was accurate, measured, and professionally defensible.

She should have stopped there.

Instead, she reopened the simulation, intending to confirm that she had cited the correct final version.

The project interface displayed the document name, its submission status, and the most recent recorded activity.

Nora noticed the activity entry because the time was later than she expected.

She had always been particular about checking document versions. At Calder Response, draft materials could pass through several stages of review, and a client’s feedback sometimes returned a completed exercise to active development. The project workspace kept a limited history of ordinary actions so contributors could see when files had been uploaded, reviewed, or accessed.

Nora selected the activity panel.

The first entries were familiar.

September 22, 4:38 p.m.: Final scenario submitted.

September 23, 9:12 a.m.: Project coordinator review completed.

September 24, 2:06 p.m.: Delivery package approved.

A later entry recorded the completed project’s transfer to the restricted client-delivery area.

She scrolled down.

The next item was dated October 13.

Today.

At 5:41 p.m., the final scenario file had been accessed through the project’s internal service account.

Nora looked at the time again.

5:41.

According to the news report, the initial emergency announcement at the Harbor House Hotel had occurred at approximately 5:17. The evacuation order had followed around six minutes later.

Somebody had accessed her simulation roughly twenty-four minutes after the emergency began.

She checked the entry carefully.

It did not identify a person. The workspace used a shared service identity for certain administrative operations, including delivery verification and document indexing. Depending on the system’s configuration, an ordinary automated process could generate an activity record that looked similar to one created by a person.

The interface did not distinguish between those possibilities.

Nora had no reason to assume the access was unauthorized.

Still, the timing was peculiar.

The project had been marked complete nearly three weeks earlier. She was no longer making changes, and the client had not requested revisions. As far as she knew, the file had been sitting untouched since its delivery.

She opened the activity details.

The record contained only the time, document reference, and service-account designation.

There was no visible indication of which individual had initiated the action, whether the document had been read, or whether anything had been downloaded.

Nora checked the file’s revision history.

No new version appeared.

That was reassuring, but it answered only one question. A file could be viewed without being edited, and the activity record alone could not tell her what had actually happened.

She considered contacting the company’s technical support team.

At nearly ten thirty in the evening, a routine inquiry would probably remain unanswered until morning. An urgent request would require her to explain why she believed the access needed immediate investigation.

She wasn’t certain she could do that without sounding unreasonable.

Elaine had asked her to wait.

Nora closed the activity panel, then opened it again.

The entry remained unchanged.

She thought about the hotel conference, the woman at the microphone, and the red umbrella leaning against the platform.

What bothered her now was not simply that the incident resembled her work.

It was the possibility that somebody else had been interested in that work at almost the same time the incident occurred.

She knew enough about data systems to understand that such a connection could be entirely innocent. Internal services operated according to schedules and rules that ordinary users rarely considered. An automated review might have been triggered by a routine delivery check. Someone in administration might have been preparing a monthly compliance report.

There were several plausible explanations.

She would have been happier if she could identify even one of them as the actual explanation.

Nora made a note of the access record inside the company’s project workspace. She saved the entry’s reference number and wrote down the time, being careful not to label the activity suspicious or unauthorized.

Her next action was less professional.

She searched the internet for the name of the Harbor House Hotel and the phrase red umbrella.

The results were predictably unhelpful.

Several photographs showed the hotel entrance during rainy weather. One featured a couple sharing a red umbrella in front of the building, apparently taken years earlier. Another linked to a travel review discussing a restaurant with bright red patio umbrellas.

Nora almost laughed.

She had spent part of her evening investigating the existence of an umbrella in Washington State.

From the outside, the entire exercise would have looked absurd.

She closed the browser.

Then she opened it again and searched for photographs of the conference hall taken before the emergency.

The summit’s public social-media page contained several images posted earlier that afternoon. In one, attendees were gathering near the entrance. In another, a speaker stood at the podium while a presentation about building-maintenance budgets appeared behind her.

Nora enlarged the second photograph.

The platform was visible.

There was no umbrella beside it.

She checked the time of the post. The image had been uploaded shortly after three o’clock, more than two hours before the incident.

That established almost nothing. An umbrella could easily have been placed there later.

Nevertheless, Nora saved the link.

She found herself becoming increasingly dissatisfied with the way her mind was working.

Every ordinary detail seemed to acquire a possible hidden meaning. Every missing piece of information began to resemble a deliberate omission.

She was making the same cognitive error she warned clients against: treating an emerging hypothesis as though it had already been established.

Nora closed the laptop.

She would speak with Elaine in the morning. If necessary, they could ask the technical team whether the file access was routine. They could review the actual incident reports when those became available and determine whether the similarities justified further attention.

There was no immediate decision she needed to make.

She stood and walked to the kitchen.

The apartment was quiet except for the low mechanical sound of the refrigerator. Through the windows, she could see lights in the neighboring buildings and the occasional movement of traffic on the street below.

She lived alone in a two-bedroom apartment north of downtown Seattle. The second bedroom had gradually become an office, although she had promised herself when moving in that she would keep work out of her home as much as possible.

The arrangement had lasted three months.

Now the room held a large desk, a bookshelf crowded with professional manuals, and several storage boxes containing notebooks she had been meaning to organize.

Nora liked the apartment because it offered predictable comforts. The kitchen received morning light, the building was generally quiet, and the commute to Calder Response rarely required complicated planning.

She had chosen it after visiting eleven other apartments and constructing a comparison table that included rent, transportation costs, noise levels, and the distance to the nearest grocery store.

A friend had once asked whether she had ever made an important decision without preparing some kind of list.

Nora had said yes.

Afterward, she had tried to remember an example.

She filled the kettle, then changed her mind and emptied it.

Her body wanted sleep, but her mind remained caught between the television footage and the unexplained access record.

She returned to the living room, picked up the remote, and turned off the television.

The sudden quiet was welcome.

She stood looking at her reflection in the dark screen. At thirty-eight, she had become accustomed to finding signs of exhaustion in her face after difficult workdays, but tonight she looked more unsettled than tired.

The red umbrella had been an irrelevant detail in a fictional exercise.

Whoever had carried it into the real conference room might have forgotten it by now.

The woman who had made the emergency announcements probably hadn’t noticed it at all.

Nora wondered whether there was a sensible way to stop thinking about something once her mind had decided it required an explanation.

She had never found one.

Her phone lay on the dining table where she’d left it after speaking with Elaine.

She crossed the room and checked the time.

11:26 p.m.

There were no missed calls.

One unread message had arrived from an unfamiliar number.

Nora assumed at first that it was another automated notification. She had received several that week, mostly unwanted offers from companies apparently convinced that she needed to refinance a mortgage she didn’t have.

The message preview contained no greeting.

She opened it.

“You predicted the fifth one. Now look at the first four.”

Chapter 2 — Five Ways to Ruin a Life

For almost a minute, Nora did nothing except stare at the message, trying to decide whether the person who had sent it knew something about her work or merely wanted her to believe they did.

The number was unfamiliar, with an area code that told her nothing useful. There was no name attached to it, no identifying photograph, and no earlier conversation. The message had arrived at 11:26 p.m., less than two hours after she’d begun investigating the similarities between her confidential simulation and the emergency at the Harbor House Hotel.

You predicted the fifth one.

The wording bothered her more than the sender’s anonymity.

She had not predicted anything. She had developed a hypothetical training exercise for a legitimate client, using common emergency procedures and reasonable assumptions about human behavior. The real incident might resemble that exercise, but resemblance was not prediction, and whoever had written the message seemed determined to collapse the distinction.

Then there was the other problem.

Now look at the first four.

Four what?

Nora read the message again, searching for some indication that it had been sent to the wrong person. There was none. Its reference to the conference incident was too specific to dismiss, especially given the timing.

She considered replying, but stopped herself before opening the keyboard. An answer would confirm that the number belonged to her and that she had understood the reference. She had no reason to give an unknown person either piece of information.

Instead, she took a screenshot, recorded the number in her notes, and opened the message details. The phone provided no useful information beyond the delivery time.

She checked the obvious possibility that someone at Calder Response had decided to play an exceptionally poor joke. A colleague might have seen the Bellport news coverage, recognized the similarities, and sent an anonymous message to provoke her curiosity.

But there were problems with that explanation.

Only a handful of employees had been involved in developing C-214, and Nora had discussed the incident with Elaine Mercer less than two hours earlier. She couldn’t imagine Elaine sending a message like this. Nor could she think of anyone else who would know that she was investigating the conference emergency tonight.

The more she considered it, the less comfortable she became.

She returned to the dining table and opened her laptop.

The project workspace was still active, displaying the summary she’d prepared for Elaine. Nora created a separate private working note outside the company’s system and typed the message exactly as it appeared.

Below it, she added a question.

Does “fifth” refer to the sequence of actual incidents or the order of the simulations?

She looked at the sentence for a moment, then began searching her project history.

Over the previous nine months, she had completed more than a dozen training assignments. Most were ordinary exercises involving workplace emergencies, communication failures, or complicated decisions that organizations preferred to practice before encountering them in reality.

Five projects stood out because they dealt with situations in which an institution’s first public response could have serious consequences for a particular individual.

It was a broad category. Nora knew that from the beginning. Almost any crisis involving an organization could damage somebody’s reputation, livelihood, or physical safety.

Still, the anonymous message had given her a number.

Five.

She began with the oldest project she could remember.

The first simulation had been submitted on February 4.

Its internal reference was CR-041, and Nora had titled it Hearing Room.

The assignment concerned a public meeting at which officials were scheduled to hear testimony about municipal recordkeeping practices. During the meeting, an unexpected building alert created confusion among attendees. Security personnel attempted to restore order, but conflicting instructions interrupted the proceedings and prevented several speakers from delivering their prepared statements.

The client’s objective was straightforward: assess how public officials communicated when a routine procedural meeting was unexpectedly disrupted.

Nora remembered writing the exercise because she’d been dissatisfied with the client’s initial request.

They wanted an emergency that was dramatic enough to challenge participants but uncomplicated enough for everyone to agree on the correct response.

She had argued that the more interesting problem involved competing responsibilities. Officials had to protect the people in the building, but they also had an obligation to preserve public participation. An evacuation might be justified, yet the way the meeting was subsequently handled could create an entirely different kind of harm.

She opened the archived document and skimmed the first pages.

Nothing immediately suggested a connection to Bellport.

The exercise involved a municipal hearing rather than a professional conference. The building was a county administrative center, not a hotel, and the disruption arose from an unexpected alarm rather than a suspicious item.

Then Nora searched the news archives.

She began with general terms related to interrupted public meetings in Washington State during the spring. The first results were irrelevant: a school board meeting postponed because of a power outage, a city council session interrupted by a medical emergency, and several articles about public protests.

She narrowed the search to March.

An article from a regional newspaper caught her attention.

COUNTY HEARING ENDS ABRUPTLY AFTER BUILDING ALERT

The report was dated March 12.

According to the article, a public hearing at the Greyhaven County Administrative Annex had been suspended after an unexpected evacuation alert interrupted testimony concerning municipal records retention.

Several attendees had complained that officials failed to explain whether the meeting would resume.

One man, Thomas Bell, had been waiting to present documents when security personnel directed everyone outside.

Nora read the article twice.

The general resemblance was obvious, although it was hardly extraordinary. Public meetings were sometimes interrupted by alarms, and disputes over whether proceedings should continue were predictable.

What caught her attention was a passage near the end.

Bell had reportedly requested that the county preserve the speaking order and allow him to submit his prepared materials when the hearing reconvened. His request had not been addressed before officials closed the session.

In Nora’s simulation, a fictional participant encountered almost exactly that problem.

She opened the relevant section.

Participant requests confirmation that documentary material intended for public testimony will be accepted following the interruption. The meeting chair declines to address the request until building operations have returned to normal.

The similarity gave her pause, but she knew how easily a reader could exaggerate the importance of familiar language.

Public officials often deferred procedural questions during emergencies. A speaker asking to preserve testimony was not inherently unusual.

There was also a significant difference.

Her exercise required the meeting to reconvene later that same day.

According to the article, the real Greyhaven hearing had been postponed for nearly two weeks.

Nora wrote both observations into her notes.

She then looked for additional reporting about Thomas Bell.

He was a former municipal records technician who had become involved in a local campaign advocating greater public access to government documents. The hearing interruption had apparently damaged his efforts to challenge the county’s recordkeeping policies. By the time the postponed meeting occurred, the agenda had changed, and his prepared testimony had received little public attention.

The articles did not establish that anyone had deliberately prevented Bell from speaking.

They established only that an unexpected interruption had consequences for him.

Nora added his name to her notes.

Thomas Bell — public hearing — March 12 — Greyhaven.

It was the first entry in a list she had not intended to make.

At 12:38 a.m., Nora was examining the second project.

CR-088 had been submitted on April 9 under the title Public Confidence.

The client was a professional association that trained municipal administrators. The scenario involved accusations of misconduct against a senior city official, followed by the circulation of documents whose authenticity could not immediately be established.

The challenge for participants was to respond without prejudging the allegations, improperly disclosing confidential information, or undermining an ongoing review.

Nora remembered spending considerable time on the exercise because she disliked scenarios that assumed an accused person was guilty merely to simplify the training.

Real institutions often faced situations in which the truth was not immediately knowable. Acting too quickly could harm innocent people, while refusing to act could create the impression of a cover-up.

Her final version deliberately avoided resolving the accusations during the exercise itself.

She searched for municipal officials in Washington who had faced allegations involving procurement documents during the spring.

The first several results were unrelated.

Then she found an article published on May 19.

DEPUTY FINANCE DIRECTOR PLACED ON LEAVE AMID CONTRACTING QUESTIONS

The official was Marisol Vega, deputy finance director for Port Alder, a small city north of Seattle.

An anonymous source had circulated documents suggesting that Vega improperly influenced a municipal contracting decision. The allegations emerged shortly before a scheduled council review, and copies of the documents reached several local news organizations.

Vega denied wrongdoing.

The city placed her on administrative leave pending an investigation.

Nora opened a second article.

A photograph showed Vega leaving the municipal building, her expression strained as reporters called questions from behind a temporary barrier.

The caption described her as a longtime public servant who had previously worked in Greyhaven.

Nora stopped scrolling.

Greyhaven again.

She opened a map, confirming that the two municipalities were separate communities. A former official moving between nearby cities was entirely ordinary, but the repeated name was enough to make her return to her notes.

She entered Marisol Vega beneath Thomas Bell.

Then she examined the details of the allegations.

The documents had apparently been delivered to journalists in a collection of scanned pages, accompanied by a short statement accusing Vega of manipulating a bidding process. The news articles did not establish who had assembled the material.

In her simulation, Nora had described an anonymous packet containing selected extracts from internal records.

The fictional accusation was different, and the timing did not match perfectly.

However, one detail was oddly familiar.

The real documents were distributed shortly before a public meeting, leaving officials little time to examine them before reporters began asking questions.

Nora’s exercise had been built around that exact difficulty.

She compared the materials for several minutes, then found another distinction that mattered.

Her original working notes emphasized the danger of misinformation spreading before documents could be authenticated. The approved project file seemed to go further.

It contained a paragraph describing how an accusation might become permanently associated with an official even if a later investigation found insufficient evidence.

Nora remembered discussing that possibility with Elaine, but she did not remember including it in such explicit language.

She opened her notebook from April.

The notebook was not a formal company record. Nora kept handwritten notes during brainstorming sessions because she found it easier to identify connections when she wasn’t staring at a screen. She generally transferred important ideas into the official project documents afterward.

On April 6, she had written:

Focus on uncertainty, delayed verification, communication failures. Avoid assuming guilt or innocence.

There was nothing about a lasting reputational consequence being the primary objective of the exercise.

That did not establish a discrepancy. She could have developed the idea afterward, during revision.

Nevertheless, the wording in the approved file seemed unfamiliar.

She marked the paragraph for later comparison.

At 1:17 a.m., she found a follow-up article reporting that Vega had resigned from her position despite the investigation remaining unresolved.

There was a photograph of the official standing outside her home, refusing to comment.

Nora studied the image longer than she intended.

The woman looked exhausted.

She wondered what it was like to have strangers examine your professional life through a collection of documents you hadn’t been allowed to explain.

Then she remembered that she was doing something uncomfortably similar.

She closed the photograph.

Her job had taught her to consider the consequences of institutional decisions, but until tonight, those consequences had usually existed as hypothetical entries in a training exercise.

Thomas Bell had lost an opportunity to speak publicly.

Marisol Vega had lost her position.

Both had experienced events that resembled situations Nora had imagined beforehand.

That was unsettling.

It still wasn’t proof of anything.

The third project was easier to remember because Nora had nearly withdrawn it before submission.

CR-123, Worksite Response, had been completed on June 11 for a private industrial-safety training organization.

The simulated emergency involved an accident at a commercial worksite, followed by confusion over the severity of an employee’s injuries and the responsibilities of several organizations involved in the response.

Nora had designed the exercise around the consequences of incomplete information.

A supervisor initially believed that all personnel had been accounted for. Later, conflicting reports revealed that one worker had been injured and that the company’s first public statement had been inaccurate.

The client’s training coordinator had objected to the scenario because it portrayed management as poorly informed.

Nora had argued that the purpose of the exercise was to prepare people for situations in which their information was imperfect, not to reassure them that their organization would behave flawlessly.

The final version remained close to her original draft.

She searched for workplace incidents in Washington during July.

This time, a relevant result appeared almost immediately.

On July 23, an industrial accident at a commercial facility near the Greyhaven waterfront had injured an electrical contractor named Nolan Price.

Initial statements from the operating company suggested that the incident had caused a temporary work stoppage but no serious injuries. Later reports confirmed that Price had been transported to a hospital.

The revised statement attracted criticism from local safety advocates, who accused the company of releasing information before it had adequately established the facts.

Nora read the article, then checked two additional sources.

The broad sequence resembled her exercise closely, but she remained cautious. The actual accident involved equipment that had not appeared in her simulation, and the employer’s initial statement had been issued through a different communication channel.

She added the incident to her list.

July 23 — Nolan Price — Greyhaven waterfront.

Then she opened the official version of CR-123 again.

Something in the later pages troubled her.

The scenario contained an optional discussion point asking participants how they would respond if the injured employee had previously raised concerns about the organization’s safety record.

Nora did not remember writing that question.

She found the paper notebook she’d used during the June project and searched through several pages of diagrams and crossed-out observations.

Her original outline mentioned an employee injured during a routine operation, but there was no reference to previous complaints.

She checked the official project’s approval history.

The file had passed through a coordinator’s review before final delivery, as was normal. The workspace showed the approved version but did not provide a complete history of every change made during internal review.

Nora looked again at the unfamiliar discussion point.

Had she written it during revision and simply forgotten?

That was possible.

Had a coordinator added it to make the exercise more demanding?

Also possible.

Neither explanation required misconduct.

Yet the question seemed carefully chosen to introduce a motive for discrediting the injured worker.

Nora opened another news article about Nolan Price.

The report quoted a colleague who said Price had repeatedly complained about inadequate safety documentation before the accident.

She sat still, reading the sentence a second time.

Her official exercise contained a hypothetical employee with a history of safety complaints.

The real incident involved an injured contractor whose colleagues described similar concerns.

The correspondence was meaningful enough to investigate, but the article had been published after the accident. If the detail had circulated earlier through professional networks, somebody involved in reviewing the simulation might have encountered it indirectly.

She checked the dates again.

June 11: her simulation submitted.

July 23: accident.

The article appeared on July 26.

That sequence ruled out the article as the source of an earlier revision, but not every possible source of information.

Nora wrote a note beside the project reference.

Optional discussion point absent from handwritten planning notes. Authorship uncertain. Verify review history.

She resisted the temptation to write anything stronger.

The habit of cautious language felt almost absurd at two o’clock in the morning, with an anonymous message sitting on her phone and three real incidents appearing to correspond to three confidential exercises.

But she knew what happened when investigators began treating a pattern as a conclusion.

They stopped noticing facts that complicated the story they wanted to tell.

She refused to do that.

By 2:31 a.m., the apartment had become painfully quiet.

Nora had turned off the kitchen lights to reduce the glare on her laptop screen, leaving only the lamp above the dining table. Beyond the windows, the neighboring buildings were mostly dark.

Her glass of water stood untouched beside her notebook.

She had considered making coffee, but the idea of deliberately extending the night made her uneasy. She was tired enough to begin making careless decisions, and the material in front of her required precision.

She looked at her notes.

Three projects.

Three real incidents.

Three individuals whose professional lives or physical safety had been affected.

Two connections to Greyhaven, and one incident that had occurred there.

She could have stopped.

She had enough information to approach Elaine in the morning with a reasonable request for a formal review. Continuing alone would not make the company more likely to cooperate.

But there were still two projects to examine.

The fourth had been submitted on August 20.

CR-170, Archive Integrity.

Nora remembered that assignment particularly well.

It involved a public institution discovering apparent inconsistencies in its historical records after documents became available through an online portal. The scenario required participants to distinguish between genuine errors, misleading records, unauthorized alterations, and deliberate accusations intended to damage confidence in the institution.

She had written the exercise after a discussion with a client who believed that digitizing records automatically made them more reliable.

Nora disagreed.

Digital records could be copied, transferred, mislabeled, and presented outside their original context. A file’s presence in an official database did not necessarily establish that every statement inside it was accurate.

She found the final document and skimmed the background section.

The simulated controversy centered on a records manager whose professional reputation was damaged when apparently falsified inspection reports appeared in a public archive.

Nora remembered writing the fictional records manager as a sympathetic character. She wanted trainees to consider the possibility that the person responsible for maintaining a record might not be responsible for its contents.

She searched for public controversies involving altered inspection records.

The results included several unrelated investigations and one article dated September 9.

CITY RECORDS MANAGER SUSPENDED AFTER DOCUMENT DISCREPANCIES EMERGE

The official was Helen Dorr, a senior records manager working for a municipal agency in Tacoma.

According to the report, inspection documents released through a public records portal contained inconsistencies that raised questions about whether information had been altered before publication.

Dorr had been suspended while the agency conducted an internal review.

The article included a statement from her attorney denying that she had falsified any records.

Nora read the story carefully.

The similarities to her simulation were substantial, although the underlying documents concerned different municipal functions. She found no indication that the real agency had followed the same procedures described in the exercise.

Then she noticed a reference to Dorr’s earlier career.

Before moving to Tacoma, Helen Dorr had served as a municipal records coordinator in Greyhaven.

Nora leaned back.

The same town again.

She opened another search result and confirmed the biographical information.

Thomas Bell had worked in Greyhaven.

Marisol Vega had previously held a municipal position there.

Nolan Price had been injured at a commercial facility near its waterfront.

Helen Dorr had spent years maintaining records for the town’s administration.

The connection was no longer something she could comfortably ignore, even though it remained difficult to interpret.

Greyhaven was not an isolated village where every former resident would necessarily know everyone else. It was a small coastal municipality with enough commercial and government activity to produce many professionals who later moved elsewhere.

A group of unrelated people might share that geographic history without being connected in any meaningful way.

Still, the repetition was striking.

Nora opened a new page in her notebook and wrote a single heading.

Greyhaven.

Underneath, she listed the four names.

She considered searching each person’s employment history more thoroughly, but stopped when she realized how quickly that investigation could expand beyond the original question.

She was supposed to be determining whether five real incidents resembled five confidential simulations.

Instead, she was approaching the edge of a much larger inquiry into the professional histories of people she’d never met.

The anonymous message had led her here.

She reminded herself that this was exactly what an anonymous sender might have intended.

Whoever sent it could have selected incidents with superficial similarities and arranged them into an apparent pattern. A sufficiently determined person could find connections among almost any group of professionals, particularly in a region where people frequently moved between local governments, consulting firms, and private organizations.

She had to consider that possibility.

But the sender hadn’t provided her with the incidents.

They had provided only a number.

Nora had found the cases herself by comparing her own work with publicly available records.

That distinction mattered.

She glanced at the clock.

3:06 a.m.

The final project was still waiting.

C-214.

The conference emergency.

Nora already knew more about the fifth incident than the others, but reviewing it alongside the earlier cases changed how she interpreted the evidence.

Until tonight, she had considered Bellport as an isolated coincidence.

Now it appeared to belong to a possible sequence.

The five simulations had been created for different clients over approximately eight months. They involved different organizations, distinct professional environments, and different kinds of crises.

Yet each one centered on an individual who could be harmed by the response to an emergency or accusation.

And each corresponding real incident appeared to have damaged someone.

She reopened the website for the Northwest Facilities Leadership Summit.

The program contained photographs and brief biographies of the scheduled speakers.

Nora recognized several names from professional conferences she’d attended, although she knew none of them personally.

She moved down the list until she found the afternoon session that had been interrupted.

Three speakers were scheduled to discuss emergency communication in buildings with large numbers of occupants.

One was a hotel security consultant.

Another worked for a facilities-management association.

The third was Leah Sutton, an independent risk-management adviser.

Her biography stated that she had previously worked with emergency-planning organizations throughout western Washington, including several years in Greyhaven.

Nora felt a slow tightening in her chest.

She read the biography again.

Leah Sutton was not listed as a current Greyhaven employee. Her connection to the town appeared to be historical.

The biography didn’t explain what projects she had worked on there.

Nora searched her name alongside the hotel incident.

Most results repeated the original breaking news report. One more recent article included a statement from the conference organizers.

Several attendees had received assistance following the evacuation. Sutton, who had been scheduled to participate in the interrupted afternoon session, had been transported to a nearby hospital for observation after suffering an injury during the confusion.

Her condition was described as stable.

Nora placed both hands flat on the table.

Five incidents.

Five people.

All connected, in different ways, to Greyhaven.

She looked at the names.

Thomas Bell had lost an opportunity to present documents at a public hearing.

Marisol Vega had faced damaging allegations and resigned from her position.

Nolan Price had been seriously injured at work.

Helen Dorr had been suspended amid accusations involving falsified records.

Leah Sutton had been injured during a conference emergency.

The outcomes were not identical. The evidence linking each event to Nora’s corresponding simulation varied considerably, and some similarities remained explainable as coincidence.

Yet the geographic pattern demanded attention.

She began a new search using the five names together.

Nothing useful appeared.

She tried combinations of two and three names, adding Greyhaven and terms related to municipal government.

The results were scattered.

A county meeting record included Thomas Bell’s name. An old procurement notice mentioned Marisol Vega. A local business directory listed a company associated with Nolan Price.

There was no obvious document connecting all five.

Nora searched for Greyhaven itself.

The town’s website appeared first, followed by tourism listings, local news articles, and a collection of public notices.

She scrolled through several pages, looking for anything that might explain why so many people associated with the town had become involved in unrelated controversies.

Nothing immediately stood out.

The town had experienced ordinary political disputes, commercial development, and periodic disagreements over municipal contracts.

A coastal storm several years earlier appeared in the search results, but Nora didn’t open the article. She was looking for recent connections among the five people, not a general history of the municipality.

She returned to her notes.

The problem was no longer whether one simulation resembled one incident.

It was whether the similarities across all five projects could be explained by ordinary professional circumstances.

She knew that improbable combinations occurred more frequently than people expected. Given enough events and enough possible similarities, patterns would inevitably emerge.

But there was a difference between noticing a pattern after the fact and finding evidence that somebody had deliberately created it.

The anonymous message suggested the latter.

Nora had not yet established it.

She looked again at her working notes for the earlier simulations.

Then she remembered the unfamiliar passages in the approved project files.

At 3:42 a.m., Nora began comparing her handwritten notes with the official versions of the five scenarios.

She had accumulated several notebooks over the previous year, each filled with meeting observations, rough diagrams, draft dialogue, and reminders written in the hurried shorthand she used during project development.

Her handwriting was not especially neat, but she could usually reconstruct what she’d meant.

For every major assignment, she began by writing a simplified version of the intended problem before drafting the formal exercise.

Those early notes often contained the central idea in its clearest form.

She found the February notebook first.

The original Hearing Room concept included a public meeting disrupted by an unexpected alert. The main training objective was to preserve orderly communication while maintaining participants’ rights.

The official file contained that material.

But it also contained a detail Nora didn’t remember adding.

The central witness is prevented from submitting supporting documents before the hearing is terminated.

She read the sentence several times.

In her notebook, the fictional participant was described simply as someone waiting to speak. The emphasis was on fair procedure, not on preventing a particular person from providing evidence.

The difference could have resulted from an ordinary revision.

Nevertheless, it was significant enough to note.

She opened the April project.

The approved Public Confidence scenario placed greater emphasis on discrediting an individual through allegations that couldn’t immediately be verified than her working notes appeared to support.

Again, she could not establish that someone else had made the change.

She might have expanded the concept during drafting.

But it was unusual for her to forget the central purpose of an exercise she’d designed.

The June project contained the additional discussion point about an injured employee who had previously reported concerns.

The August project included another unfamiliar passage.

Participants should consider how public uncertainty about document authenticity may affect the credibility of the records manager responsible for the archive.

Nora searched her August notebook.

Her original idea focused on protecting the reliability of institutional records while an investigation proceeded.

The approved file seemed more concerned with the personal consequences for the records manager.

She opened the submission history.

The approved document was dated August 20, as expected. The workspace showed that the project had passed through internal review, but its limited activity display did not establish who had written every passage.

That meant she couldn’t prove anything had been altered after her submission.

She couldn’t even rule out the possibility that the unfamiliar material reflected changes she had made herself and subsequently forgotten.

The uncertainty irritated her.

At work, she routinely told colleagues that missing information was not evidence of misconduct. Now, sitting alone in her apartment, she found herself wanting to disregard that principle.

She forced herself to return to the facts.

Four projects contained passages whose emphasis differed from her original handwritten plans.

Those passages appeared in official company files.

Several corresponded to unusually specific aspects of real incidents that occurred after the exercises had been developed.

The project histories visible to her were insufficient to establish who had added the passages or when.

She wrote the findings down exactly that way.

Then she added a question.

Were the approved versions the same documents I originally submitted?

For the first time that evening, the question seemed more important than the anonymous message.

If the files had been changed during legitimate editorial review, there might be a perfectly ordinary explanation for the discrepancies.

If they had been changed without authorization, the implications were considerably more serious.

And if the changes had been made after the real incidents occurred, someone might be attempting to create the appearance that Nora had anticipated details she had never actually written.

She looked at the final paragraph in her notes.

That possibility frightened her because it transformed the situation.

Until now, she had been investigating why fictional scenarios resembled real events.

The new question was whether somebody was manipulating the documentary record of her work.

She couldn’t answer it without access to original submissions, complete revision histories, and an independent review of the company systems.

Those were not things she could obtain simply by searching through her own project dashboard.

She would need help.

Nora reached for her phone and opened Elaine’s contact.

Her thumb rested above the call button.

It was 4:19 a.m.

She imagined waking her supervisor to explain that she’d spent the night comparing confidential simulations with newspaper reports, searching the employment histories of strangers, and examining handwritten notes because an anonymous message had instructed her to do so.

Elaine would listen.

She might even agree that the file discrepancies deserved investigation.

But Nora wanted to present something more convincing than a collection of observations whose significance she still couldn’t establish.

She closed the contact without calling.

Then she opened a new email draft.

Elaine,

I continued reviewing the project materials after our conversation. I’ve identified several matters concerning previous simulations that may justify a formal comparison of original submissions and approved versions.

She stopped.

The message was accurate, but hopelessly incomplete.

It didn’t explain the five incidents, the Greyhaven connection, or the possibility that unauthorized changes had been made to the company’s files.

Nor did it mention the anonymous message.

Nora read the draft again and deleted it.

She could write a proper report in the morning.

For now, she needed sleep.

At 5:03 a.m., Nora finally closed the project workspace.

Her notes filled seven pages.

She had organized the five incidents into a timeline, marked which similarities were verified, and listed the questions that required further investigation.

The red umbrella appeared near the bottom of the fifth entry.

It was still the detail that disturbed her most.

The anonymous sender might have known something about the other incidents, but Nora couldn’t explain how a seemingly irrelevant object from her private imagination had appeared in a real conference room.

She knew she was assigning too much significance to the object.

She also knew she couldn’t stop thinking about it.

Nora left the dining table and walked to the bedroom.

She changed into an old T-shirt, set her alarm for eight, and lay down.

Sleep did not come.

Every time she closed her eyes, the five names returned in the order she’d written them.

Thomas Bell.

Marisol Vega.

Nolan Price.

Helen Dorr.

Leah Sutton.

Five people whose lives had been disrupted in different ways.

Five incidents resembling exercises she had helped create.

One coastal town linking them.

She wondered whether the anonymous sender had selected the incidents precisely because they would make her investigate.

Perhaps the message came from a disgruntled employee, someone with access to Calder Response’s project archive and a personal grievance against the company.

Perhaps the sender believed a conspiracy existed and wanted Nora to confirm it.

Or perhaps someone was deliberately trying to frighten her.

There was no reliable way to choose among those explanations.

She turned onto her side.

The room was beginning to brighten.

Outside, a vehicle passed along the street, its tires making a soft sound against the pavement.

Nora tried a technique she sometimes recommended to clients preparing for difficult decisions: list what was known, what remained uncertain, and what action could reasonably be taken next.

She knew that five real incidents bore varying degrees of resemblance to five training exercises.

She knew that the affected people shared connections to Greyhaven.

She knew that some passages in the official company files were absent from her original notes.

She did not know who had written those passages.

She did not know why the incidents had occurred.

She did not know who had sent the message.

And she had no evidence that anyone at Calder Response had committed wrongdoing.

The next reasonable action was to bring the findings to Elaine and request a proper review.

She repeated that conclusion until it began to feel reassuring.

At some point, she fell asleep.

The alarm woke her at eight.

For several seconds, she didn’t remember why she felt so exhausted.

Then she saw the open notebook beside her bed.

The five names were written across the top of the page.

Nora sat up.

The events of the night returned with uncomfortable clarity.

She checked her phone.

No new messages had arrived from the anonymous number.

There was, however, an ordinary company notification.

A new assignment had been added to her project queue.

Nora frowned.

Calder Response’s project coordinators occasionally distributed assignments early in the morning, particularly when clients were working across different time zones. Nothing about the notification was inherently unusual.

She opened it.

The assignment had been created under a restricted client category, with preliminary materials awaiting her review.

The project description was brief.

CONFIDENTIAL COMMISSION — SCENARIO SIX

Nora stared at the title.

The wording could have been a coincidence. Calder Response regularly numbered exercises according to a client’s preferred sequence, and the company handled enough projects that seeing a sixth scenario would ordinarily have meant nothing.

But after the anonymous message, she couldn’t treat it as an ordinary assignment.

She opened the accompanying document.

The first page contained standard administrative information: project classification, confidentiality requirements, and a short description of the intended assessment.

The exercise was supposed to examine how an experienced crisis professional responded when confronted with uncertain evidence, conflicting institutional obligations, and threats to personal credibility.

Nora’s pulse quickened.

She scrolled down.

The next section introduced the fictional subject.

Female crisis analyst, late thirties. Senior position within a private emergency-planning consultancy. Based in Seattle. Demonstrates exceptional analytical discipline, strong professional independence, and persistent difficulty delegating decisions involving reputational or personal risk.

Nora stopped reading.

There were thousands of professional women who might fit such a description, although the combination of age, occupation, and location narrowed the possibilities considerably.

She continued.

Subject maintains handwritten planning notebooks independently of formal project documentation. She habitually compares alternative outcomes before making decisions and shows a marked preference for resolving uncertainty through personal investigation rather than seeking immediate assistance.

Her mouth had gone dry.

The description matched her working habits with uncomfortable precision.

She looked at the notebooks beside her bed.

Then she returned to the document.

The next paragraph described the subject’s response to evidence suggesting that her professional work had become connected to a real-world incident.

Initial behavior is expected to involve independent verification of the apparent correspondence, followed by consultation with a trusted direct supervisor. The subject is likely to delay external reporting until she believes her findings can withstand professional scrutiny.

Nora read the paragraph again.

It described what she had done the previous evening.

She had investigated the conference incident alone.

She had contacted Elaine.

And when the discrepancies in the earlier simulations became more troubling, she had postponed reporting them until she could prepare a convincing account.

Her eyes moved to the next sentence.

Subject’s central vulnerability is an unresolved professional failure in her earlier career. This experience has reinforced a need to anticipate consequences and has made the subject particularly susceptible to situations in which she believes she can prevent a repetition of her previous mistake.

Nora felt a cold, immediate recognition.

The document did not name her.

It didn’t have to.

Someone had written a fictional crisis analyst whose profession, habits, age, location, private methods of working, and deepest professional regret corresponded to Nora’s own life.

She looked at the heading again.

SCENARIO SIX

For the first time since the conference footage appeared on television, Nora understood that the question might not be how somebody had obtained access to her imagination.

It might be how much somebody knew about her.

And why they had decided to turn that knowledge into an exercise.

Chapter 3 — The Woman in the File

The next page of Scenario Six described what the fictional crisis analyst would do when she began to suspect that her employer was concealing information, and Nora Keene found herself reading the paragraph with the peculiar sensation that someone had been standing behind her during the previous night.

The subject will initially avoid formal external reporting because she believes an unsupported allegation could damage her professional credibility. She is likely to seek confirmation from a trusted superior while continuing an independent review of available materials. If the superior offers a reassuring explanation, the subject may temporarily accept it, although unresolved inconsistencies will encourage further private investigation.

Nora moved the cursor away from the text, as though doing so might make the words less personal.

She had called Elaine Mercer shortly after discovering the similarities between her conference simulation and the emergency at the Harbor House Hotel. Elaine had listened, offered reasonable explanations, and suggested that they review the matter together in the morning. Nora had accepted that advice, then spent the night investigating five other incidents without telling anyone what she was doing.

The description was accurate, but accuracy alone did not make it extraordinary. A competent behavioral analyst could reach similar conclusions about many cautious professionals.

What disturbed Nora was the combination of specific details.

The fictional subject was a woman in her late thirties, a senior crisis analyst in Seattle who kept handwritten notebooks, disliked delegating important decisions, and had developed an unusually strong need for control after an unresolved professional failure.

Nora looked toward the open notebook on her bedside table.

Most people at Calder Response knew she preferred handwriting during the early stages of a project. Elaine had occasionally teased her about the habit, pointing out that the company employed people specifically to maintain digital records. There was nothing confidential about it.

Her earlier professional mistake was different.

She had never discussed it openly with Elaine.

Eight years ago, during an emergency-response review, Nora had noticed that two official records described the same event using different times. She’d raised the discrepancy with someone more senior, accepted an explanation that now seemed inadequate, and allowed the review to proceed.

No one had accused her of misconduct. The final report had been approved, the assignment closed, and the incident gradually disappeared from ordinary professional conversation.

But Nora remembered.

She remembered the conference room where she’d asked her question and the embarrassment she’d felt when the discrepancy was dismissed as something an experienced analyst should have understood. More than anything, she remembered how relieved she’d been to accept the explanation.

She had spent years trying not to repeat that particular weakness.

Now someone had placed a description of it inside a training exercise.

She scrolled to the document’s administrative section.

The assignment had appeared in her queue shortly before eight that morning, while she’d been asleep. Its title was Confidential Commission — Scenario Six. The client was identified only by a restricted account number, and the project coordinator’s field contained a general departmental designation rather than a person’s name.

That was unusual but not unprecedented. Calder Response sometimes handled sensitive assignments for organizations that wanted preliminary work completed before distributing their names to a larger project team.

Nora checked the file properties available to her.

The document appeared to have been prepared within the company’s restricted project environment and released to her account that morning. The interface displayed neither a complete drafting history nor the identity of the person who had written the behavioral profile.

She could not tell when the descriptions had originally been composed.

That distinction mattered.

If the document had been written before the previous evening, its accuracy raised one set of questions. If it had been assembled afterward, someone might simply have been recording her actions and presenting the result as a prediction.

Neither possibility was reassuring.

She reached the section titled Decision-Making Vulnerabilities.

The subject’s desire to establish certainty may become a liability when she encounters apparently contradictory evidence. She will favor independent verification even when professional assistance is available, particularly if she believes that disclosure could expose an earlier failure of judgment.

Nora felt an unexpected flicker of anger.

The description was plausible. It was also reductive, transforming a complicated human being into a collection of tendencies that could be manipulated.

She had written similar profiles herself.

In training exercises, behavioral models helped participants understand why people under pressure might make choices that seemed unreasonable afterward. Nora had always insisted that those models remain provisional. Individuals were not mechanical systems, and even well-supported predictions could fail when circumstances changed.

The author of Scenario Six did not seem interested in such qualifications.

The next paragraph identified the subject’s probable response to a perceived institutional threat.

The subject is expected to preserve her professional standing while seeking evidence that may compromise the organization employing her. This conflict can be intensified by limiting her confidence in internal reporting channels.

Nora read the sentence again.

It was no longer describing how the fictional analyst might behave.

It was describing how someone could influence her.

She closed the document without finishing it.

For a moment, she remained sitting on the edge of the bed, conscious of the pale morning light entering through the curtains and the dull pressure behind her eyes. She had slept for less than three hours. Her thoughts were sharp in some directions and strangely slow in others.

She needed another person to look at the material.

The realization irritated her because she had already reached the same conclusion during the night and then found reasons to postpone acting on it.

She picked up her phone and called Elaine.

Her supervisor answered almost immediately.

“Good morning. I was about to call you. Did you get any sleep?”

“Not much. Have you heard of a project called Scenario Six?”

Elaine hesitated. “I don’t think so. Why?”

“It appeared in my queue this morning. Restricted commission, no named client, and a behavioral profile that’s uncomfortably close to me.”

“Close in what sense?”

“Age, profession, work habits. Things I’d usually dismiss as generic, except some of the details are personal.”

There was a brief silence.

“Is it assigned to our team?”

“Apparently. I can’t see who prepared it.”

“That sounds like an administrative mistake. Send me the project number, and I’ll look into it.”

Nora glanced at the screen.

“I also found some problems with the older simulations.”

“The Bellport exercise?”

“Five exercises altogether. Four earlier ones.”

Elaine exhaled softly.

“Nora, how long were you working last night?”

“Most of it.”

“All right. Look, come into the office and we’ll go through what you’ve found. I’d rather not do this over the phone.”

“Can we include the original submission records?”

“If there’s a reason to review them, yes. But let me understand the problem first.”

Nora considered explaining the anonymous message. She had omitted it from her previous conversation, and doing so again would mean withholding the very thing that had prompted her investigation.

“Someone sent me a text last night,” she said. “An unknown number. They referred to the conference incident as the fifth one and told me to look at the first four.”

Elaine didn’t answer immediately.

“Did you recognize the number?”

“No.”

“Was it threatening?”

“Not directly.”

“Have you shown anyone?”

“Not yet.”

“Then bring it with you. And Nora, please don’t forward those restricted documents around while we’re trying to understand what’s happened.”

“I wasn’t planning to.”

“I know. I’ll see you when you get here.”

The call ended.

Nora looked at Scenario Six, still visible in the list of recent assignments.

She had asked Elaine about the project and received no explanation. Her supervisor sounded concerned, but there had been nothing in her response to suggest that she knew what the document contained.

Under ordinary circumstances, Nora would have felt relieved.

Instead, she found herself wondering how much any explanation from Calder Response could be trusted.

The thought embarrassed her.

She had worked with many of these people for years. Elaine had supported her through difficult assignments, defended her work when clients complained, and occasionally told her things she needed to hear but didn’t particularly welcome.

A mysterious document and an anonymous message did not justify suspecting everyone around her.

Yet neither did long acquaintance establish that an organization was incapable of concealing something important.

Nora put the laptop in her bag, gathered the handwritten notes from the previous night, and prepared to leave.

Before closing the apartment door, she returned to the dining table and picked up the notebook containing her comparison of the five incidents.

She had almost left it behind.

The omission bothered her because it was so unlike her.

Then she remembered that she had been awake for most of the night and allowed herself the possibility of ordinary human fatigue.

Calder Response occupied three floors of a renovated office building near Seattle’s business district. The reception area was deliberately understated, with pale walls, comfortable chairs, and a display showing photographs of emergency-planning exercises at airports, hospitals, and commercial facilities.

The company wanted visitors to feel that complicated situations could be made manageable through preparation.

Nora usually appreciated the message.

That morning, it seemed faintly ironic.

She arrived shortly after ten, having stopped for breakfast at a café where she managed to eat half a sandwich despite having little appetite.

The office was busy in the familiar way of a consulting firm approaching several deadlines at once. Conversations drifted from meeting rooms, someone was arguing about a presentation schedule, and a junior analyst hurried past carrying a stack of printed documents.

Nothing appeared different.

Nora had expected that normality would comfort her. Instead, she felt a peculiar distance from her colleagues, as though she’d spent the night examining a version of the company that nobody else knew existed.

Elaine’s office was empty.

Her calendar showed that she had been called into a management meeting.

Nora stood beside the glass partition, considering whether to wait, when the executive assistant from the top floor approached.

“Julian would like to see you,” the woman said.

Nora looked up.

“Now?”

“If you’re available. He said it shouldn’t take long.”

Julian Calder rarely summoned employees without arranging an appointment, particularly when they were not working directly on one of his executive projects.

“Did he say what it was about?”

“No, but he knows you’ve just arrived.”

The answer was ordinary enough.

Nora followed the assistant toward the elevators.

Julian Calder had founded the company more than two decades earlier and remained deeply involved in its most important client relationships. At sixty-one, he had the polished confidence of someone accustomed to being listened to, although Nora had always thought his greatest professional skill was making other people feel that he was listening to them.

He had been one of her earliest mentors.

When she joined Calder Response, she was technically capable but uncertain about the political complications of consulting work. Julian taught her that a good analysis was only useful if the people receiving it could understand the consequences.

He had also taught her that organizations rarely welcomed information that made them uncomfortable.

“Your job,” he once told her, “is to make it easier for them to hear the truth than to ignore it.”

She had carried that sentence through much of her career.

The elevator opened onto the executive floor.

Julian’s office overlooked the city, with broad windows and a large conference table that was rarely used for actual conferences. He preferred meeting people in the sitting area near the windows, where conversations felt less formal.

He rose when Nora entered.

“There you are. I heard you had a difficult evening.”

The remark unsettled her, although Elaine had presumably told him about their conversation.

“That’s one way to describe it.”

“Sit down. Can I get you coffee?”

“No, thank you.”

He studied her for a moment.

“You look tired.”

“I didn’t sleep much.”

“I gathered that.”

Julian indicated the chair opposite him and waited until she sat.

Nora placed her bag beside her feet.

“I assume Elaine told you about Bellport.”

“She mentioned your concerns. Apparently one of our training exercises resembles the incident at that hotel.”

“It’s more complicated than that.”

“Then tell me.”

The invitation was so familiar that Nora almost relaxed. Julian had always preferred allowing people to finish explaining a problem before offering an opinion.

She described the conference emergency, the distinctive umbrella, and the sequence of announcements. She then explained that an anonymous message had prompted her to examine earlier projects.

She gave him the five project references and summarized the corresponding real incidents.

When she mentioned Greyhaven, Julian’s expression remained attentive but unreadable.

“All five people have connections to that town,” she said. “The connections vary, and I haven’t established that they’re meaningful, but the pattern deserves examination.”

Julian folded his hands.

“And you’ve done all this since last night?”

“Yes.”

“After speaking to Elaine?”

“I couldn’t sleep.”

He considered that.

“Nora, before we go further, has anyone else seen these notes?”

“Not yet.”

“Have you contacted any of the people involved?”

“No.”

“Good. I’m glad you came to us first.”

Something about the relief in his voice made her uneasy.

She reminded herself that any responsible executive would prefer an employee to report concerns internally before contacting strangers connected to potentially sensitive incidents.

“There are also discrepancies in the approved project files,” she said. “Some passages don’t appear in my original planning notes.”

“That’s not unusual. Our review process often adds material.”

“I know. But these passages seem to correspond to details in the real incidents.”

“Seem to?”

“I haven’t established who wrote them or when. That’s why I want the original submission packages and complete revision histories preserved.”

Julian nodded slowly.

“A sensible request, provided we handle it properly.”

Nora opened her bag and took out a single page containing the project references.

“I’ve listed what I think needs reviewing.”

He accepted the paper but did not immediately look at it.

“And Scenario Six?”

The direct question surprised her.

“Elaine mentioned it?”

“She did. Something about a behavioral profile.”

Nora watched him closely.

“Do you know who commissioned it?”

“Not offhand. We have several restricted projects underway.”

“It describes me.”

“Specifically?”

“Enough that I don’t believe it’s accidental.”

Julian looked down at the page in his hand.

“Have you considered the possibility that the assignment was generated from an internal training profile? We sometimes use composite subjects based on professional roles.”

“Who would have access to the details about my earlier career?”

He raised his eyes.

“What details?”

Nora hesitated.

The document had referred to an unresolved professional failure, but it had not specified the incident. She was suddenly reluctant to tell Julian exactly which memory it had awakened.

“Things I don’t generally discuss,” she said.

His expression softened.

“I understand why that would be disturbing.”

“Then I want to know who wrote it.”

“And you should. I’ll ask our compliance people to establish the source of the assignment.”

“Will they preserve the original record?”

“Of course.”

Nora had expected him to resist more strongly. The ease of his response should have reassured her, but she kept thinking about the difference between promising a review and establishing that the underlying evidence could not be changed.

“I’d also like an independent record of the request,” she said.

Julian’s expression changed slightly.

“Independent in what sense?”

“Something that confirms the preservation request was made before anyone began examining or modifying the files.”

“We have procedures for that.”

“I know.”

He leaned back.

“Then perhaps you should let those procedures work.”

There was no irritation in his voice, but Nora recognized the boundary he was drawing.

She had encountered it with clients who welcomed difficult questions until those questions began challenging the systems they trusted.

“Julian, somebody sent me a message about these incidents before I’d identified the earlier four. Then Scenario Six appeared in my queue, containing details about my behavior. I don’t know whether the two things are connected, but I can’t dismiss them as administrative coincidences without checking.”

“I’m not asking you to dismiss anything.”

“What are you asking?”

“I’m asking you to recognize that you’ve had a frightening experience, you’ve barely slept, and you’re attempting to investigate several complicated matters at once. That’s a difficult position for anyone.”

Nora looked toward the windows.

Beyond the glass, traffic moved steadily through the streets below.

“I understand that.”

“Do you?”

His tone was gentle.

“You’ve spent years teaching organizations that people make poor decisions when they’re exhausted and under pressure. You deserve the same consideration you give your clients.”

She had no immediate answer.

Julian rose and moved to the window, then turned back toward her.

“I’d like you to take a few days away from work. Paid leave, nothing disciplinary. Elaine can arrange it. Meanwhile, I’ll have compliance conduct a quiet review of the projects you’ve identified.”

Nora felt an uncomfortable mixture of gratitude and suspicion.

She wanted to believe him.

She also wanted to know why taking leave was necessary before the records could be examined.

“Will I receive the findings?”

“Anything relevant to your concerns, certainly.”

“And the underlying records?”

“We’ll determine what can properly be shared.”

“Some of those records relate to my own work.”

“They also belong to clients, Nora. We have obligations beyond any one employee.”

She couldn’t dispute that.

Julian returned to his chair.

“There’s another consideration. If you begin contacting outside organizations or discussing restricted assignments with people who aren’t authorized to see them, you could create problems for yourself and for the company.”

“Are you telling me not to report this?”

“No. I’m telling you to be careful about confidential information. If there is evidence of a crime, we’ll cooperate with the appropriate authorities. But speculation circulated without context can do considerable damage.”

He paused.

“I’ve seen how seriously you take your professional reputation. I’d hate for an exhausted evening to become something you regret.”

Nora studied him.

Julian appeared genuinely concerned. He had not raised his voice or accused her of misconduct. Most of what he said was reasonable.

Yet she couldn’t ignore the way the conversation had shifted.

She had entered his office asking for the preservation of records and an explanation of a disturbing assignment.

She was now being encouraged to take leave while the company reviewed the matter privately.

Perhaps that was the correct response.

Perhaps it was simply the response most convenient to the organization.

“I appreciate the offer,” she said, “but I don’t want to agree to leave before I’ve spoken with someone independent.”

Julian’s expression remained composed.

“A professional adviser?”

“Yes.”

“That’s your decision.”

He handed back her list of projects.

“Take the rest of the day, at least. We’ll make sure the appropriate people are informed.”

Nora stood.

“Please confirm the preservation request in writing.”

“I’ll have someone contact you.”

She picked up her bag.

At the door, Julian spoke again.

“Nora?”

She turned.

“You’ve always been unusually hard on yourself. Whatever this turns out to be, don’t assume you’re responsible simply because your name appears somewhere in the paperwork.”

For a moment, she felt the old gratitude that had once made his approval so important.

Then she remembered the behavioral profile.

Its author knew precisely how much she feared repeating a past mistake.

She thanked Julian and left.

Elaine was waiting near the elevators.

“How did it go?”

Nora glanced toward the executive offices.

“Julian offered me leave while compliance reviews the files.”

“That sounds reasonable.”

“Maybe.”

Elaine studied her face.

“You’re not convinced.”

“I want someone outside the company to look at the problem.”

“Because you think we’re hiding something?”

Nora heard the hurt beneath the question.

“No. Because if the records have been altered, I don’t know who did it. An independent review protects everyone, including the people who haven’t done anything wrong.”

Elaine considered that.

“I suppose it does.”

They stood together for a moment while employees moved through the corridor.

“I should have asked you more questions last night,” Elaine said.

“You had no reason to think there was more to it.”

“Neither did you, at first.”

Nora looked down at the notebook in her hand.

“I found more than I expected.”

“Then get some advice. And please, for once, don’t try to solve every part of this yourself.”

Elaine’s concern was unmistakable.

Nora wanted to tell her everything, including the private memory that had appeared in Scenario Six, but the hallway was not the place for that conversation.

“I’ll call you,” she said.

“Good. And eat something before you start another investigation.”

Nora managed a small smile.

Elaine had said almost the same thing the night before.

This time, Nora intended to listen to at least part of the advice.

Outside, the morning had become a bright, cool autumn day. People moved along the sidewalks carrying coffee and talking into phones, apparently unaware that anything unusual had happened.

Nora stood near the building entrance and searched for an attorney.

She had worked with corporate counsel on client contracts, but those lawyers represented Calder Response or its customers. She needed someone whose professional responsibility would be to her alone.

The distinction was suddenly important.

She found the Washington State Bar Association’s lawyer-referral information and began identifying attorneys experienced in employment matters, internal investigations, and allegations involving confidential records.

The first office couldn’t offer an appointment until the following week.

The second referred her to a specialist whose schedule was full.

At the third, a receptionist listened to her brief explanation and said that an attorney named Claire Bennett had an opening that afternoon because another client had canceled.

Nora accepted immediately.

The receptionist asked whether the matter involved a dispute with her employer.

“Possibly,” Nora replied. “I don’t know yet.”

“That’s all right. Ms. Bennett can help determine what kind of matter it is.”

For the first time that morning, Nora felt a small measure of relief.

Someone was willing to examine the problem without requiring her to define it first.

Claire Bennett’s office was on the seventh floor of a modest building several blocks from the courthouse.

There were no dramatic views or expensive furnishings. The reception area contained a small table with legal publications, a framed photograph of the Washington coast, and a coffee machine that appeared to have survived several renovations.

Nora arrived fifteen minutes early.

She had spent much of the intervening time organizing her notes into a chronology, although she had resisted the temptation to rewrite every observation into a formal report.

The attorney greeted her at precisely two thirty.

Claire was a woman in her forties with dark hair pulled loosely away from her face and an expression that suggested she was accustomed to hearing complicated explanations without being impressed by their complexity.

She offered Nora a seat across from a desk covered with neatly arranged folders.

“Before we begin, I want to be clear about something,” Claire said. “I’m here to understand what happened and what legal risks you may be facing. That doesn’t mean I’ll agree with every conclusion you’ve reached.”

“That’s what I need.”

“Good. Start wherever you think the problem began.”

Nora took a breath.

“Yesterday evening, I saw a news report about an emergency that resembled a confidential simulation I’d written three weeks earlier.”

She explained the conference incident, the red umbrella, and the suspicious access record.

Claire listened without interrupting.

When Nora described the anonymous message, the attorney asked to see it.

Nora showed her the screenshot and the original conversation on her phone.

“Have you replied?”

“No.”

“Good. Don’t delete anything, and don’t try to identify the sender through questionable means. If the message becomes relevant to an investigation, we’ll want the original record preserved.”

Nora nodded.

She continued with the five simulations and the real incidents she had identified.

Claire asked questions about dates, document ownership, and how Nora had obtained the information.

When Nora mentioned her handwritten notebooks, the attorney leaned forward.

“Are those your original working notes?”

“Yes. I keep them while developing the exercises.”

“Do they contain confidential client information?”

“Some project details, although the notes are primarily my own planning material.”

“Then we need to be careful about how they’re handled. Don’t distribute copies until we’ve reviewed the confidentiality obligations that apply.”

Nora agreed.

She had expected the attorney to focus immediately on the apparent conspiracy.

Instead, Claire seemed most interested in separating ordinary records from evidence that might have legal significance.

It was exactly the kind of discipline Nora usually appreciated in her own work.

After nearly forty minutes, Claire closed her notebook.

“Let me make sure I understand. You have five training exercises completed before five real incidents. Some of the incidents share unusual similarities with those exercises, and all five affected individuals have connections to Greyhaven.”

“Correct.”

“You also believe certain passages in the company’s approved files differ from your original work.”

“I know they differ from my handwritten notes. I can’t establish who wrote the approved passages or when they were added.”

“That’s an important distinction.”

“I know.”

“And this morning, you received a new assignment containing a behavioral profile that appears to describe you.”

“Yes.”

“Have you shown that document to anyone outside Calder Response?”

“No. I haven’t copied or distributed it.”

Claire nodded.

“That was prudent. We can address lawful preservation and disclosure without creating unnecessary complications.”

Nora looked at the attorney.

“Do you think I’m imagining a connection that isn’t there?”

“I think you’ve identified circumstances worth examining. I don’t yet know whether they establish misconduct.”

The answer was neither reassuring nor dismissive.

Nora found that she trusted it.

Claire rested her hands on the desk.

“My immediate concern is preserving the records and protecting your position while the facts are established. If documents have been altered, we don’t want original versions lost through routine retention processes or deliberate interference. We also don’t want you accused of improperly accessing or distributing confidential materials while attempting to investigate.”

“What should I do?”

“First, stop conducting your own inquiry through the company’s systems unless it’s part of your ordinary authorized work. Don’t change anything, and don’t attempt to recover files or access histories beyond your permissions.”

Nora nodded.

“Second, I’ll send a formal preservation notice to Calder Response’s legal department. It will identify the relevant projects, document versions, access records, assignment history, and communications. We’ll ask the company to suspend ordinary deletion or overwriting of potentially relevant material.”

“Will they have to comply?”

“A preservation notice isn’t a court order, and sending one doesn’t guarantee that every record will be retained. But it establishes that the company has been informed of a foreseeable dispute and provides a documented basis for further legal steps if necessary.”

“And Scenario Six?”

“We’ll include it. I’ll also ask for preservation of the original assignment metadata and any records showing how the behavioral profile was created.”

Nora exhaled.

She hadn’t realized how much she needed someone else to make a practical decision.

“What about the five incidents?”

Claire considered the question.

“Some involve possible criminal conduct, but we don’t have enough information to say what happened. We can make a report describing your observations and the potential concerns about document integrity. Investigators can determine whether there is an appropriate basis for further inquiry.”

“Will they believe me?”

“They may not accept your interpretation. That’s different from refusing to examine the information.”

Nora looked at her notes.

“I’ve spent my career telling people to separate facts from assumptions.”

“Then you’re familiar with the process.”

“I thought I was.”

Claire’s expression softened slightly.

“Being personally involved changes things.”

Nora gave a tired laugh.

“Apparently.”

The attorney opened a new page in her notebook.

“Tell me about the earlier professional mistake mentioned in Scenario Six.”

Nora’s smile disappeared.

For several seconds, she considered offering the same vague description she’d given Julian.

Then she remembered why she had come.

Eight years earlier, during an emergency-response review, she’d found conflicting timestamps in records that were supposed to describe a single sequence of events. She’d raised the issue, accepted an explanation from a senior colleague, and allowed the review to proceed.

She had never established whether the explanation was correct.

“Why does that still trouble you?” Claire asked.

“Because I accepted it too easily.”

“Did you believe the explanation at the time?”

“I wanted to.”

“That isn’t quite the same answer.”

Nora looked away.

“I was younger. I was working with people I respected, and I didn’t want to become the person who delayed an important report over something everyone else considered insignificant.”

“Did you knowingly approve false information?”

“No.”

“Do you have evidence that the report was false?”

“Not enough to say that.”

“Then we need to distinguish your regret from any actual wrongdoing.”

Nora was quiet.

For years, she had treated the incident as a personal failure because doing so gave the uncertainty a shape she could understand.

Claire’s questions did not erase that regret, but they forced her to recognize how much of it rested on assumptions she had never verified.

“Does Julian Calder know about this?” the attorney asked.

“He knew about the review. He was involved in the project.”

“Did he know you were troubled by the discrepancy afterward?”

“I don’t know.”

Claire made a note.

“That’s something we may need to establish later. For now, we won’t assume the behavioral profile came from him or anyone else.”

Nora nodded.

The attorney turned to her computer.

“I’m going to prepare the preservation notice. Then I suggest we contact the appropriate law-enforcement agency and explain that you have information concerning possible alterations to corporate records and incidents in several jurisdictions.”

Nora watched Claire begin drafting.

It was a surprisingly ordinary process.

There were no dramatic revelations, no sudden certainty, and no promise that the problem would be resolved quickly.

There was simply another professional taking responsibility for a part of the situation Nora could no longer manage alone.

For the first time since the previous evening, she felt less isolated.

At 4:06 p.m., Claire sent the preservation notice to Calder Response’s legal department.

The letter identified the five project files by their internal reference numbers, requested retention of the original submission packages and subsequent versions, and asked the company to preserve relevant access histories, administrative logs, approval records, client communications, and assignment metadata.

It also specifically identified Scenario Six.

Claire retained a copy of the sent notice and the delivery confirmation.

“That doesn’t mean we’ve secured the evidence,” she explained, “but we’ve taken an important first step.”

Nora looked at the message on the screen.

“So now we wait?”

“Not entirely. I’ve also contacted the police department’s investigations office. They want some preliminary information before deciding how to handle the report.”

“Today?”

“They’re reviewing the details we gave them. There’s a possibility they may already be aware of something connected to these matters.”

Nora frowned.

“Why would they be?”

“I don’t know. The person I spoke with didn’t provide specifics.”

Claire closed the file.

“Let’s not speculate.”

Nora almost smiled.

She was beginning to recognize that the attorney had no intention of allowing her to turn uncertainty into certainty merely because certainty would be more comfortable.

They went through the notes one final time.

Claire asked Nora to distinguish between what she’d personally observed, what she’d found in public reporting, and what she’d inferred from similarities.

The exercise was demanding, especially after so little sleep.

Several times, Nora corrected her own wording.

She replaced the files were altered with some passages differ from my original planning notes.

She changed the incidents were coordinated to the incidents share similarities and geographic connections.

The more carefully she described the evidence, the less dramatic her account sounded.

But it also became more defensible.

At 4:32, Claire’s phone rang.

She answered, listened for several seconds, and then looked toward Nora.

“Yes, she’s here with me. She’s willing to speak with investigators, but I’d like to be present.”

Another pause followed.

“I understand. Can you tell me whether the material has been authenticated?”

Claire listened again.

“All right. We’ll discuss that when we meet.”

She ended the call.

Nora felt her shoulders tighten.

“What was that?”

“A detective from Seattle Police. They’d like to speak with you this afternoon.”

“About my report?”

“Partly.”

Nora waited.

Claire’s expression had become more serious.

“Apparently, investigators received information involving Calder Response before we contacted them.”

“What kind of information?”

“They wouldn’t discuss everything over the phone.”

Nora looked toward the window.

The afternoon light had begun to fade, leaving the buildings across the street in shadow.

“Someone else reported the incidents?”

“Possibly. What they told me is that an anonymous submission connects your name to several of the matters we’ve been discussing.”

For a moment, Nora couldn’t find an answer.

“My name?”

“Yes.”

“In what way?”

“I don’t know yet.”

Claire watched her carefully.

“Nora, listen to me. We are not going to assume that the material is accurate. We don’t know where it came from or whether any of it has been authenticated.”

Nora remembered the unfamiliar passages in her project files.

She remembered the anonymous message.

Then she thought of Scenario Six and its prediction that she would attempt to protect her professional credibility while investigating possible institutional wrongdoing.

Someone had already placed her at the center of the story.

She had been so concerned about understanding the incidents that she had barely considered what might happen if other people began investigating her.

Claire gathered her documents.

“We’ll go together.”

Nora stood.

Her legs felt unsteady, an unfamiliar physical response that embarrassed her even though no one appeared to notice.

She had wanted an independent investigation.

Now she was about to discover what investigators already believed.

The detective introduced herself as Morgan Shaw.

She was in her mid-forties, with closely cropped dark hair and a measured manner that made it difficult to tell whether she was skeptical, concerned, or simply concentrating.

The meeting took place in a small interview room at a Seattle Police Department facility. Claire sat beside Nora, a legal pad open in front of her.

Shaw began by explaining that the conversation was voluntary and that Nora could decline to answer questions or end the interview.

Nora glanced at Claire, who gave a small nod.

They had discussed the arrangement beforehand. Nora was willing to explain what she’d discovered, but she would not attempt to interpret documents she had not seen.

Shaw opened a folder.

“Ms. Keene, I understand you’ve reported concerns about several training exercises prepared by your employer.”

“Yes.”

“How long have you worked for Calder Response?”

“More than a decade.”

“And your current position?”