Part VI: Arteries Beneath the Glass

Aisha asked Claire to step into the hallway again, away from screens.

“I found something,” Aisha said quietly. “In the assistant training quarantine.”

Claire asked, “We disabled ingestion. What?”

Aisha replied, “I analyzed which resolved tickets contributed most to the assistant’s drift toward euphemisms. A small set of tickets from one period. They all involve the same support operations analyst. The analyst did not do anything malicious. But their templates were used. And those templates were requested by Connor’s partner team.”

Claire nodded. “Cultural root.”

Aisha said, “Yes. But there is more. The analyst’s account shows sign in anomalies.

Six weeks ago. Same day as runner manager fingerprint origin.”

Claire’s mind sharpened. “So their account was compromised.”

Aisha nodded. “Maybe. Or their session token was used. It would explain why the templates appeared so quickly. The attacker could have inserted them.”

Claire felt a cold line of anger. The attacker had not only used cultural habits. They may have actively seeded templates into the system to train the assistant. That would be more deliberate than she had assumed.

Claire asked, “Do we have evidence of template modifications?”

Aisha replied, “Version history shows edits by the analyst at times they claim they were offline. But we need to verify. The logs show sign-in from an unusual location.”

Oliver would want to treat this carefully. Accusing an employee is dangerous. But ignoring evidence is worse.

Claire wrote a note: investigate analyst account compromise without blame.

She returned to the war room and told Oliver and Rita privately.

Oliver listened, expression flat.

“We do not accuse,” he said. “We treat the account as compromised until proven clean. We interview the analyst with respect. We pull device logs. We check tokens.”

Rita nodded. “Agreed.”

Marianne, hearing only the end of the conversation, asked, “Are we suspecting internal?”

Claire replied, “We are suspecting compromised accounts. That is different.”

Marianne nodded reluctantly.

Claire watched her. Marianne was learning too, slowly. In her world, suspicion often implies blame. In security, suspicion is often just risk management. They were different languages.

The attacker lived in the gap between them.

***

They had forced the incident to reveal its structure.

Partner compromise: the diagnostic relay virtual machine, built from a marketplace image, was sending traffic to an external host.

Internal compromise: the runner manager’s identity was used to update the build runner image. Inside that environment, a planted executable program was modifying configuration live, from inside memory, in a way that could survive ordinary remediation steps.

Governance compromise attempt: a workflow automation tool was used to submit an executive role membership request under Marianne’s name.

Support tooling misuse: service account flipping identity provider toggles during noise event.

Gatekeeper: rules repository influence, attempted diagnostic windows.

Impersonation: voice and text used to push for unsafe actions.

The arteries were mapped.

Now the counterplay had to pay off in a way that changed the story, not just described it.

Oliver wanted attribution. He wanted a target. Not for revenge. For closure.

For prevention. For the ability to say - this is the campaign and this is how it operates.

But Claire cared about something else.

She cared about the high stakes choice at the end of wave three.

Because every incident ends with a choice: disclose or conceal, cut the partner or maintain, blame individuals or fix systems, restore speed or keep boundaries.

Attackers want you to choose the thing that makes them invisible.

Claire wanted the opposite.

***

The major reveal arrived when Edward compared two things that were not supposed to be related.

He compared the modified build runner image binary to the code snippet the attacker had embedded in the decoy request.

They had a matching logic structure. Not identical code. The same style of thinking.

The same error handling approach. The same habit of naming variables in a certain way.

Edward called it a signature.

He posted in the bridge, “The attacker’s code style is consistent across decoy pivot attempt and build runner binary. That suggests the same operator authored both. Not a commodity malware kit. A focused actor.”

Claire felt the room tighten.

A focused actor is more dangerous because they adapt. They learn your rituals. They pick new arteries.

Oliver asked, “Any clues about who?”

Edward replied, “Not identity. But we have infrastructure. We have the external host from the partner logs. Through our threat intelligence partners, we can review the domain’s historical routing records and the digital certificates tied to it. That may tell us what else it has been linked to, and whether it has appeared in other campaigns. We can also check whether the domain has been used before.”

Connor said, “We can ask Evelyn if they have law enforcement contact.”

Marianne said, “Be careful. Coordination with law enforcement affects disclosure obligations.”

Rita replied, “We will coordinate through legal.”

Oliver looked at Claire. “This is where your team matters. Threat intelligence. We need to know whether this actor is known.”

Claire nodded. “We can do that. But we do not need a name to act. We need to know their tactics and their likely next move.”

Aisha said, “Their next move is to force us to reopen a lever.”

Claire replied, “Or to extort.”

Julian’s eyes widened. “Extort.”

Claire said, “If they have this level of access, they can threaten release integrity. They can threaten to leak. They can threaten to keep impersonating. Attackers often turn operational compromise into leverage.”

Oliver nodded. “So, we prepare for extortion attempt.”

Rita wrote, “Any extortion attempt is handled through a single channel. No negotiation by individuals. Report and document.”

Marianne wrote, “If extortion happens, we need executive alignment immediately.”

Claire said, “Alignment requires truth. Not panic.”

Marianne did not respond.

Claire could see the high stakes choice approaching.

It would be about partnership and disclosure, about whether to keep quiet to preserve perception or to speak to protect others. Because the partner compromise suggested a broader campaign. If the external host domain was used elsewhere, other companies might be infected too.

Claire felt a familiar ethical weight.

She had seen organizations hide incidents to preserve reputation. She had seen that choice cause harm to others. She had seen the cost of silence.

But she also understood legal reality. Disclosing too early without facts can cause chaos and lawsuits.

The choice would be razor thin.

And the attacker would press on that narrow edge, because silence was not absence. Silence was cover. It was delay. It was the space in which an intruder could keep breathing.

***

The extortion attempt arrived on a Sunday morning, precisely when it would cause maximum confusion.

Claire was at home, wearing a t-shirt, hair tied back, coffee cooling on the counter.

She had not truly rested, but she had tried. Her phone buzzed with a notification from the incident bridge.

A new message in an external email inbox used for security communications.

Subject: We can help you restore normal.

Claire’s stomach turned at the word normal.

She opened the message.

It was short. Polite. Almost professional.

It said they had access. It said they could prove it. It said they would stop disruption if the company restored the diagnostic window and re-enabled the partner premium endpoint. It said they wanted a payment. It did not name an amount. It said they would name it after proof.

It ended with a sentence that made Claire’s skin go cold.

“We are not your enemy. We are your system’s teacher.”

Claire felt anger rise, sharp and clean. Attackers love to claim moral authority. They love to frame themselves as educators.

She forwarded the message to Oliver, Rita, Aisha, Edward, Julian, Connor, and Marianne with one line.

“Extortion attempt. Do not respond.”

Oliver replied within minutes.

“No response. Gather proof.”

Rita wrote, “All communications go through legal and governance. No one engages.”

Marianne wrote, “We need to convene now.”

Claire wrote, “In person if possible. No devices for the decision.”

They convened in the war room within an hour. Sunday incident rooms have a different feeling. The building is quieter, and that makes everything sound louder.

Oliver placed the printed extortion email on the table.

“Proof request,” Oliver said. “We need to see what they claim.”

Rita said, “We do not invite them to perform inside our systems.”

Aisha said, “But we can ask for proof that does not require action. Like a hash of an internal file, or a specific log line, or a screenshot.”

Edward nodded. “Or a list of systems they touched. But they can lie.”

Claire said, “We ask for proof, but we do it through legal channel, and we keep it minimal. We do not open new doors.”

Marianne asked, “If they prove, what then?”

Claire looked at her. “Then we keep doing what we are doing. We do not pay.

We continue eradication. We prepare for disclosure.”

Marianne’s eyes flashed. “Disclosure will destroy confidence.”

Rita replied, “Silence will destroy safety.”

Connor said, quietly, “And the partner may already be dealing with it.”

Julian added, “And my analysts are scared. They deserve truth.”

Marianne looked at Julian. “Truth is not always kind.”

Julian replied, “Neither is being used.”

Claire felt something shift. Julian, the support manager, was now arguing ethics with an executive. That was growth born of pain.

Oliver said, “The attacker wants us to reopen the lever. That is their ask. We will not reopen. That is the line.”

Rita nodded. “Agreed.”

Marianne noted, “If we do not reopen, they may retaliate.”

Edward said, “They already tried. Their arteries are being cut. Their options are shrinking. Retaliation is likely noise or data leak.”

Aisha added, “Or more impersonation.”

Claire said, “Then we maintain ritual. And we consider proactive communication to our internal teams so they are not blindsided by impersonation.”

Marianne’s face tightened. “Internal communication will leak.”

Rita replied, “Everything leaks. We choose controlled truth over uncontrolled chaos.”

Marianne looked at Oliver. “Is that your position?”

Oliver said, “Yes.”

Marianne’s shoulders dropped slightly. She looked like a person realizing she was outnumbered not by politics, but by a shared reality.

“Okay,” she said. “Draft internal communication. But it must be precise.”

Claire nodded. “It will be factual.”

The high stakes choice was approaching, and the building was leaning toward truth.

That was good.

But the third wave needed a reveal and a choice that would sting.

The reveal had already begun.

The attacker used the word normal.

They were watching the company’s psychology. They knew the most tempting lie was the promise of ordinary life.

Claire looked at the extortion email again.

Teacher.

They framed themselves as the one who knew better. That meant they wanted to be believed. That meant they wanted to shape narrative.

Claire refused to let them.

***

The proof arrived two hours later through the same inbox.

A list of six internal artifacts the attacker claimed to have modified, with timestamps, and a hash for each. The list included the build runner image tag, the rules repository commit, the support ops template, the workflow automation configuration, and two items that made Claire’s stomach knot.

A private directory document containing the printed callback numbers Rita had just created.

And an internal incident draft that Oliver had written but not published.

Claire stared at the list.

“How?” she whispered.

Edward read the hashes and confirmed two were accurate. The attacker had seen internal documents that should not have been visible. They had eyes.

Aisha said, “They are reading the chat or the document store.”

Rita said, “We have to assume our communications are compromised. Clean room only for strategy.”

Oliver’s face darkened. “They got our printed list.”

Rita’s mouth tightened. “Then we rotate again. And we stop writing lists digitally at all.”

Claire asked, “How did they access the directory document? It was created yesterday.”

Edward replied, “It was created in a shared drive. It may have been synced.”

Claire felt rage rise. “We cannot keep using shared drives as if they are safe.”

Marianne said, “We use them because we need collaboration.”

Claire replied, “Then we secure them.”

Oliver said, “Focus. They have eyes. That is the reveal. The question is where.”

Edward said, “If they can see Oliver’s incident draft, they have access to the incident workspace. That suggests compromise of chat or ticketing or document system.”

Aisha added, “Or compromise of a user account with access. Possibly a compromised session token.”

Claire thought of the support operations analyst account anomalies. A compromised account with broad access could see documents.

Rita said, “We need to cut off broad access. Principle of least privilege. Immediately.”

Marianne groaned. “That will disrupt collaboration.”

Rita replied, “We are already disrupted.”

Claire said, “We need to find the account they are using.”

Oliver nodded. “Edward, run a query. Who accessed the incident draft. Who accessed the directory document. Correlate with anomalous sessions. Find a common identity.”

Edward nodded and began.

While he worked, the room faced the high stakes choice that the attacker was forcing.

The attacker had proof.

They had eyes.

They wanted the company to reopen the lever.

They wanted payment.

If the company refused, the attacker would likely leak or cause noise.

The company could choose silence and pay to restore quiet. Or it could choose truth and fight.

Claire knew her choice.

She also knew the building’s choice would be harder.

Marianne was thinking of customers and headlines. Julian was thinking of his analysts and their fear. Connor was thinking of the partner and their relationship. Edward was thinking of the build and how to eradicate. Aisha was thinking of data and language and the way systems learn. Rita was thinking of governance and the fact that safety cannot be negotiated. Oliver was thinking of response and the line you do not cross.

Claire spoke into the silence.

“We do not pay,” she said. “We do not reopen. We do not let them teach us our values.”

Rita nodded. “Agreed.”

Oliver nodded. “Agreed.”

Aisha nodded. “Agreed.”

Edward nodded. “Agreed.”

Julian nodded slowly. “Agreed.”

Connor nodded after a moment. “Agreed.”

All eyes turned to Marianne.

Marianne looked at the table, at the printed email, at the hashes, at the fact of eyes in their walls.

“I hate this,” she said.

Claire replied, “Me too.”

Marianne looked up. “But fine. We do not pay.”

The choice was made.

It did not feel triumphant. It felt like stepping into a cold river because the bridge was burning.

***

Edward’s correlation returned an hour later with the answer that made the room go still.

“I found a common identity,” he said.

He turned his screen to show the list.

A contractor account. Solis Consult.

The same name the attacker had tried to add to the executive override role.

The account had accessed the incident draft. It had accessed the directory document.

It had accessed support operations templates. It had accessed the rules repository. It had authenticated through a token refresh path, then maintained access through session persistence.

Claire felt her mouth go dry.

“They already have Solis Consult,” she said.

Rita’s eyes narrowed. “Where did the account come from?”

Edward replied, “It was created two months ago through the workflow automation tool. It was approved by a manager in support operations as a temporary contractor for documentation help.”

Julian’s face drained. “Support ops.”

Claire felt anger and pity collide. The support operations analyst account compromise.

The templates. The drift. The contractor account. The workflow automation tool. It was all connected.

Aisha said, “They created a contractor account to read our internal voice and to edit our training templates.”

Oliver said, “They planted a human-like identity. That is the foothold.”

Rita said, “Disable account. Now.”

Edward replied, “Disabled.”

Oliver said, “Invalidate sessions. Rotate keys. Audit all actions performed by that account.”

Edward replied, “Doing.”

Claire felt the reveal hit her like cold.

The attacker was not only outside. They were inside as a legitimate looking contractor identity. A face inside their directory.

And the high stakes choice was now sharper.

If they disclosed, they had to admit that their internal access controls allowed a contractor identity to gain broad access and persist. If they stayed silent, the attacker could keep pressing.

Now they had something else. They had a specific foothold to eradicate.

But eradication is not the end. Eradication is the beginning of recovery. And recovery requires choices that affect reputations and relationships.

Marianne asked, “Who approved the contractor.”

Rita replied, “We will investigate without blame first. We will focus on mechanism.

But yes, approvals will be examined.”

Marianne’s face tightened. “There will be accountability.”

Claire said, “Accountability is not scapegoating.”

Marianne’s eyes flashed. “Do not lecture me.”

Claire replied, “I am not. I am protecting the process.”

Oliver cut in. “Focus. The account is disabled. Now we trace what it did. We find whether it created other accounts. We find other arteries.”

Edward nodded. “Initial scan shows it requested elevated access in small increments.

It also modified support ops templates and posted into internal channels.

It used language patterns we identified. It also requested the runner manager tag update through automation.”

Connor whispered, “It was them.”

Claire nodded. “Yes.”

Aisha added, “And they likely used the partner VM to establish the initial trust relationship that got them into our contractor pipeline. They nested supply chains. Partner marketplace image. Our contractor. Our build. Our assistant.”

Oliver said, “That is the campaign. A chain of trust exploitation.”

Claire felt grim satisfaction. The story had structure. Structure is how you fight.

But wave three needed to end with a major reveal and a high stakes choice.

They had the reveal: Solis Consult was the internal foothold. The attacker had been inside with a contractor identity. They had been reading and shaping. They had eyes.

The high stakes choice was now this.

Do they cut the partner relationship entirely and disclose to the broader ecosystem, or do they attempt quiet remediation to preserve reputation?

Because if the attacker used partner marketplace images and contractor pipelines, others were likely vulnerable. If they stayed silent, other companies might be compromised.

Claire looked at Oliver. “We have to notify.”

Marianne snapped, “Notify whom?”

Claire replied, “The partner. Our customers if impacted. Possibly the marketplace provider. Possibly others through coordinated disclosure. The domain in partner logs may be in use elsewhere. If we do not share, we become part of the harm.”

Marianne’s face tightened. “That is not your decision alone.”

Rita said, “It is a governance decision.”

Oliver said, “It is also an ethical one.”

Connor said, “Evelyn deserves to know what we found. They are compromised.”

Julian said, “And my team deserves to know why we are doing this.”

Aisha added, “If this campaign is real, other organizations using similar patterns are at risk. If we can prevent harm, we should.”

Marianne looked around. She looked cornered by responsibility.

Claire said, softly, “This is the choice. Quiet or coordinated.”

Marianne exhaled. “If we disclose, we lose confidence.”

Claire replied, “If we conceal, we keep the attacker’s shadow alive.”

Oliver said, “We can do coordinated disclosure. We can work with legal. We can do it in phases. But we cannot do nothing.”

Rita said, “And we cannot restore partner integration until they cooperate fully.”

Marianne looked at Connor. “Will they cooperate?”

Connor said, “Evelyn will. Caleb will fight.”

Marianne looked at Claire. “And if Caleb fights?”

Claire replied, “Then we separate.”

Marianne’s face hardened. “Termination.”

Rita said, “Separation.”

Oliver said, “Boundary.”

Claire said, “Survival.”

Marianne stared at them for a long moment.

Then she said the sentence that ended wave three with a high stakes choice that would change the rest of the story.

“Prepare the disclosure plan,” Marianne said. “And prepare the termination plan.”

Connor blinked. “You mean it.”

Marianne nodded, jaw tight. “Yes. Because if they were used as the staging ground, they are either compromised or complicit. Either way, we cannot keep pretending this is normal.”

Claire felt the word normal land differently for the first time in days.

Not as a lever.

As a thing they were finally willing to let go of.

Oliver nodded. “Wave four begins with execution.”

Claire wrote the final line in her notebook for wave three, not as a dramatic line, but as a simple record of what had changed.

“We found the face inside. Now we decide who we tell.”

Then she closed the notebook.

The building had stopped being polite.

It had started being honest.

And honesty, in this kind of war, is how you stop bleeding.

***

The next twenty-four hours felt like a narrow corridor with doors on both sides.

Every door could be another artery.

Edward led a technical sweep. Aisha led a language sweep. Rita led a governance sweep. Julian led a human sweep. Connor led a partner sweep. Claire and Oliver led the corridor itself, walking back and forth between rooms and systems, making sure that every action was verified, documented, and executed with intent.

The first step was to understand what Solis Consult had truly done.

Edward pulled the account’s activity log and projected it on the wall.

The account had accessed the rules repository and downloaded constraint bundles.

It had edited support operations templates. It had commented on internal knowledge base articles with subtle suggestions that used the building’s favorite euphemisms. It had submitted requests through the workflow automation tool. It had interacted with the build registry and triggered promotion jobs.

But the most disturbing activity was quiet.

The account had joined the incident workspace weeks before the incident was officially recognized.

“How?” Julian asked. “How did it get access?”

Rita replied, “Because we treat internal collaboration as harmless.”

Claire said, “And because a contractor needs access to be useful. We gave access. We did not supervise.”

Marianne asked, “Who approved?”

Rita looked at her. “We will not ask that question first.”

Marianne’s eyes flashed. “We need accountability.”

Claire replied, “We need containment first. Accountability without containment becomes theater.”

Oliver nodded. “Containment, then accountability.”

Marianne looked away, jaw tight.

Claire knew Marianne’s impulse. When executives feel threatened, they want a culprit.

A culprit makes the incident feel like a person, not a system. A person is easier to punish than a system is to rebuild.

But the attacker had already shown they could wear faces. Punishing faces without understanding mechanisms is how you miss the real artery.

Edward zoomed in on one entry.

A role membership request submitted by Solis Consult two days after its creation.

The request asked to add Solis Consult to a group called Ops Rapid.

Edward said, “Ops Rapid has broad read access across support, templates, and internal docs. It also has limited write access in the knowledge base.”

Claire asked, “Who approved that?”

Edward replied, “The workflow automation tool approved it automatically based on a rule: contractors with documentation responsibilities get Ops Rapid.”

Rita’s eyes narrowed. “That rule is wrong.”

Aisha added, “And convenient.”

Julian said, “Support ops wanted documentation help.”

Claire said, “And someone wrote a rule to make it easy.”

Oliver wrote on the whiteboard.

Easy is an artery.

Rita said, “We remove the rule. Immediately.”

Edward nodded. “Removed.”

Marianne asked, “How many other contractors were added through that rule?”

Edward replied, “Four.”

Julian’s eyes widened. “Four?”

Claire felt her skin go cold.

Four contractor identities with broad access. Any could be compromised. Any could be an attacker wearing a badge.

Rita said, “Disable all contractor accounts pending verification.”

Marianne protested, “They are working.”

Rita replied, “They are not worth a breach.”

Claire added, “If they are legitimate, they will tolerate verification. If they refuse, that is information.”

Marianne’s mouth tightened, but she did not argue further. She had already agreed to prepare the termination plan. She was adjusting to the new logic.

Edward disabled the contractor accounts. He invalidated sessions. He rotated keys.

He hardened the workflow automation tool. He restricted role membership creation to manual, verified processes.

The building began to feel like a fortress under construction, noisy with scaffolding.

***

The human sweep mattered as much as the technical sweep.

Julian brought in the support operations analyst whose templates had been implicated.

His name was Morgan. He looked frightened. He also looked exhausted in a way Claire recognized. Exhaustion is how people become vulnerable to convenience.

Rita insisted the conversation be held with respect.

“We are investigating compromised accounts,” Rita said. “This is not an accusation. We are asking you to help us reconstruct what happened.”

Morgan’s hands trembled slightly. “I did not do anything wrong,” he said.

Claire kept her voice calm. “We believe your account may have been used. We need to understand your workflow.”

Morgan swallowed. “I wrote templates. Connor’s partner team asked for premium response language. Julian wanted faster closures. Marianne wanted stability metrics.

I tried to help.”

Marianne flinched at being named, but she did not interrupt.

Claire asked, “Where did the phrase diagnostic window come from?”

Morgan frowned. “I think I heard it from platform. Or from a partner ticket. People used it in chat. I used it because it sounded precise.”

Aisha spoke softly. “It sounds precise because it is euphemism.”

Morgan looked at her, confused.

Aisha continued, “It hides access behind a softer word. That softness is persuasive.”

Morgan’s eyes widened. “I did not mean that.”

Claire nodded. “We know. When did you first create the premium partner rapid response template.”

Morgan thought. “Two months ago. I remember because the partner escalations were intense. Connor asked for a better script.”

Connor swallowed. “Yes.”

Morgan continued, “I created it in the knowledge base, then I shared it in chat.

People copied it into tickets. I later updated it to include executive directive language because someone said Marianne wanted faster handling.”

Marianne’s face tightened. “I did not request that phrase.”

Morgan looked panicked. “I heard it in chat. Someone said it.”

Claire asked, “Who?”

Morgan shook their head. “I do not know. It was in a thread. It could have been anyone.”

Aisha leaned forward. “Do you recall unusual sign-in prompts? Password resets. MFA prompts you did not initiate?”

Morgan nodded slowly. “Yes. Six weeks ago, I got a prompt. I thought it was a glitch.

I approved because I was trying to get into a meeting.”

Claire felt a cold wave.

Approved because of a meeting.

Relief as gap, again.

Claire kept her voice gentle. “Thank you for telling us. That prompt may have been the compromise. We will help you recover. This is not shame. It is evidence.”

Morgan’s eyes filled with tears. “I did not know.”

Julian said, quietly, “None of us did.”

Claire looked at Marianne. Marianne’s eyes were hard, but there was something else there too. A recognition that human error is not solved by anger.

Rita concluded the interview with simple instructions.

“We reset your account,” she said. “We re enroll your MFA. We audit your devices.

We will work with you. You did not cause this alone.”

Morgan nodded, breathing unevenly.

After Morgan left, Connor spoke, voice low.

“I pressured them.”

Claire replied, “Yes. You did. And you are not the only one. This is why the system must refuse pressure.”

Connor nodded, face pale.

***

The partner sweep produced another crucial detail.

Evelyn called Connor with urgency. Connor looped Claire and Oliver in.

“We isolated diagnostic relay,” Evelyn said. “We found the marketplace image had a bootstrap script. It pulled updates from that external domain. We also found stored credentials in the VM for your integration endpoint.”

Claire asked, “Credentials for which endpoint?”

Evelyn replied, “The premium diagnostic backchannel. The one you disabled.

The credentials are long lived. They were created by our engineer months ago for convenience. We should have rotated. We did not.”

Claire felt the tired anger of a pattern repeating.

Convenience.

Long-lived credentials.

The attacker did not need magic. They needed neglect.

Oliver asked, “Do you have evidence of someone accessing the virtual machine manually?”

Evelyn replied, “Yes. We found an SSH key, a credential used for secure remote login, that does not match our inventory. It was added four weeks after the virtual machine was created.”

Aisha asked, “So the attacker got in after creation?”

Evelyn replied, “Yes. It seems they exploited an exposed service on the VM. Then they used the VM to reach your integration.”

Connor asked, “Do you think they intended to compromise you from the start?”

Evelyn hesitated. “I do not know. But the bootstrap script indicates the image was designed to pull remote rules. That looks intentional.”

Claire asked, “Can you share the image hash with us?”

Evelyn replied, “Yes. We will share through legal.”

Claire nodded. “We will coordinate disclosure with the marketplace provider.”

Evelyn exhaled. “We should have vetted.”

Claire replied, “We all should have.”

Evelyn said, “Caleb is furious. He says your terms are insulting. He wants to escalate to executive channel.”

Claire replied, “He can. We will not reopen the lever.”

Evelyn’s voice softened. “Thank you for being hard. It forced us to look.”

Claire felt a small fierce alignment. The partner was likely a victim, but their systems had been used as a staging ground. That meant the company’s choice to prepare a termination plan was still valid. Not because the partner was malicious, but because the risk of their integration could be existential until they were clean.

Oliver said, “We will continue to treat the integration as hostile until you can prove it is rebuilt. That is not punishment. That is protocol.”

Evelyn replied, “Understood.”

***

The near-miss that almost ended the week in disaster happened on a Wednesday evening when everyone was tired enough to forget that attackers love the last hour of a long day.

Edward was rebuilding runner images in the clean room. The process was slow.

Two humans, no network, deterministic build steps, signed promotion under Rita’s manual approval. It was the opposite of modern DevOps speed.

It was also working.

At 7:48 p.m., a platform engineer not on the incident team attempted to restore automated promotions, thinking it would help the backlog.

They received a message from what looked like Oliver authorizing it. The message had the right tone. It included the daily verification code. It included a link to a procedure document.

The engineer almost complied.

Then the engineer hesitated. The ritual had been spreading.

They called Rita’s office using the printed list.

Rita answered.

The engineer said, “Oliver authorized restoring automation.”

Rita replied, “Oliver did not. Do not comply.”

The engineer exhaled and said, “Thank you.”

Rita posted the incident to the bridge with one line.

“They are copying the daily code.”

Claire felt cold.

“How?” she asked.

Edward replied, “If they accessed the directory document, they may have also accessed photos or scans of the code sheet.”

Aisha said, “Or someone spoke it in chat.”

Julian said, “Or someone posted it.”

Rita’s face tightened. “We used paper. But we still wrote it where someone could photograph.”

Oliver said, “Then paper is not enough. We need a call back ritual with a dynamic challenge.”

Aisha nodded. “A challenge that cannot be stolen ahead of time. Something based on real time context.”

Claire thought. “We use a question. A fact only the current bridge knows. A rotating incident specific detail.”

Oliver nodded. “We can use a per-call callback. Ask for the current incident line number from the bridge. Something the attacker would have to see.”

Claire replied, “They may see.”

Rita said, “Then we use double callback. Two independent calls. One to Oliver and one to Rita. If both confirm, then action. If not, deny.”

Oliver nodded. “We do that.”

The ritual evolved again. The attacker was forcing them to grow stronger by copying what they used.

That was the attacker’s pattern. Copy, then weaponize.

The building’s pattern had to become: verify, then change.

***

Solis Consult was disabled. Contractor accounts were locked. Workflow automation was restricted. Support ops templates were corrected and moved under governance review.

Runner manager identity was rebuilt. Build runner images were rebuilt. Partner staging VM was isolated. External domain was identified and being coordinated through legal channels for takedown and investigation. Impersonation attempts continued but were increasingly denied.

The attacker was still there, but their options were shrinking.

The final question was what the company would do with the truth it now held.

Marianne had agreed to prepare a disclosure plan and a termination plan.

Now she had to execute, and execution is where courage is tested.

Claire watched her in meetings. Marianne was still an executive. She still cared about perception. But she was learning to speak differently.

She stopped saying normal. She started saying safe.

It sounded awkward in her mouth, like a new language.

But she said it anyway.

Connor stopped chasing praise. He started chasing evidence.

Julian stopped praising speed. He started praising discipline.

Edward stopped trusting automation. He started trusting determinism.

Aisha stopped assuming models could be safely trained on messy internal truth. She started insisting on curation like it was a moral act.

Rita kept being the wall.

Oliver kept being the bridge.

Claire kept being the boundary.

Wave three had begun with the counterplay paying off.

It ended with a building learning to treat its own voice as a weapon until proven otherwise.

And with a decision written on the whiteboard in Rita’s handwriting, clear and blunt.

We will tell the truth. We will cut what we must.

That decision was not comforting.

It was necessary.

What came next would not be about finding the hidden thing.

They had already done that.

It would be about naming it, cutting it out, and enduring what the truth would cost.