I was 90 minutes late, and my manager fined me $500. Then, days later, when the company’s entire production platform collapsed, I sat at my desk for ten hours without touching a single server console. By the time I finally opened my terminal, the firm had racked up $1. 8 million in unrecoverable losses.
At the tenth hour of the outage, my manager, Bradford Hayes, slammed the original fine notice onto the conference table in front of the executive board. He pointed a finger at the paper and raised his voice. “Look at this document,” he shouted. “Nathan Vance, 90 minutes late, $500 penalty.
Now our primary processing network has been paralyzed for 10 hours. If you knew how to restore the database, why did you sit there like a stone and watch this enterprise lose $1,800,000? ”
The main conference room on the 12th floor of Cloud Arc Technologies was packed. Victoria Albbright from human resources stood near the wall with her arms tightly folded, watching me with cold scrutiny.
Clare Dupon from finance clutched the latest loss assessment report, her knuckles white. Brandon Miller sat with his eyes fixed on his lap, pretending he was merely an innocent bystander. My production permissions had been unilaterally revoked. My annual performance incentive had been frozen.
Now they expected me to bow my head and absorb full responsibility for a catastrophe caused by their own arrogance. Bradford assumed I had no choice but to surrender. He was dead wrong. Behind him, the monitoring wall flashed crimson alerts.
I looked at the red dashboard, reached into my briefcase, and pulled out an encrypted flash drive alongside three documents signed directly by Bradford Hayes. Three days earlier, I had been stopped beside the time clock the instant I stepped into the atrium. The digital display registered my punch-in as 10:32 in the morning, exactly 90 minutes after our 9:00 start. Bradford stood beside the reception counter holding a freshly printed disciplinary memorandum.
“Nathan Vance,” he announced, pitching his voice so every engineer, receptionist, and account manager in the lobby could hear. “Late is late. Do not offer me excuses about traffic. Cloud Arc does not pay senior leads who demonstrate zero personal discipline.
”
I didn’t raise my voice or offer an emotional defense. At 1:30 that morning, Bradford had issued an emergency dispatch ticket, forcing me to access the data center to execute an urgent payment gateway migration. I had worked on the cold server floor from 2:00 in the morning until 6:40. After a quick shower, I had driven toward headquarters only to be halted by a commuter rail power failure.
The system logs, emergency dispatch messages, and facility access swipes all confirmed the timeline. Bradford refused to look at a single piece of evidence. Brandon Miller leaned out from behind his workstation with a smirk. “I used to tell everyone that high-availability production architecture cannot tolerate delays,” he said smoothly.
“I guess senior engineers shouldn’t be late either. ”
A couple of junior staff members chuckled nervously. I unclipped my silver security badge. “I understand that an unexcused arrival affects attendance tracking,” I stated evenly.
“But which corporate governance policy authorizes a $500 direct payroll deduction against a salaried employee? ”
Bradford’s eyebrows knit together. “Are you attempting to lecture your operational vice president on legal compliance? ” he snapped, shoving the notice against my chest.
“Sign the receipt immediately. ”
Victoria stepped out of the HR office, her tone sharper than ice. “Cloud Arc operates on strict policy compliance. Nathan, refusing to sign a management memorandum constitutes willful insubordination.
”
I took the document but didn’t sign. Instead, I pulled out my phone and photographed the memorandum. Bradford’s eyes narrowed. “What are you doing with that camera?
”
“Documenting an administrative action,” I answered. “If this penalty is backed by statutory authority, I will handle it through proper legal channels. But I intend to know which statute permits an unauthorized wage deduction from my guaranteed earnings. ”
Victoria’s jaw tightened.
Bradford leaned closer and lowered his voice to a whisper. “Do not overestimate your leverage here, Nathan. The enterprise platform will continue running smoothly, whether your hands are on the console or not. ”
He had been repeating that phrase ever since he was parachuted into the infrastructure division two months earlier.
Before Bradford arrived, I was a 47-year-old principal site reliability lead, overseeing 99% uptime across our cloud architecture. My 74-year-old mother, Eleanor Vance, relied on me for financial support, making job security vital. After Bradford arrived, he publicly referred to me as the “legacy maintenance guy,” attempting to demote my authority by half with a single title tweak. Bradford possessed zero technical understanding of distributed systems.
But he possessed a master’s degree in corporate maneuvering. He knew who sat in executive chairs, who whispered to board directors, whose names were repeated in quarterly summaries. I called my cousin Daniel Vance, a veteran employment attorney specializing in statutory labor protections. Daniel listened and asked one straightforward question: “Has HR already processed the $500 deduction on your official pay stub?
”
“Victoria confirmed it will be withheld from this month’s disbursement,” I replied. “Keep every screenshot,” Daniel advised. “Record all workplace conversations where permitted under state law. Preserve your pay stubs.
Maintain full compliance. ”
Before I departed that evening, Victoria sent me an urgent message: “Nathan, you are required to sign the disciplinary acknowledgement before the end of the day. ”
I replied within two minutes: “Please provide the specific employee handbook provision and statutory authority permitting a direct payroll penalty against exempt earnings. ”
The typing indicator hovered for nearly three minutes, then vanished.
Finally, Victoria wrote back: “Your continued refusal demonstrates a lack of alignment with corporate culture. ”
I saved the chat log and closed my laptop. As I walked down the corridor, Bradford’s office door was left slightly ajar. I heard him speaking to Brandon Miller in hushed, triumphant tones.
“Tomorrow morning, we officially strip Nathan’s production deployment rights,” Bradford was saying. “We will not permit him to use system complexity to hold this department hostage. ”
I did not interrupt. I reached into my coat, activated the high-fidelity recorder on my phone, and slipped it into my front pocket.
Some executives didn’t misunderstand operational risk. They simply believed someone else would always pay for their blunders. The following morning at 8:30, a corporate broadcast flashed across the engineering channel signed by Bradford Hayes. The memo bore a polished title: “Standardized Governance of Production Systems and Access Controls.
” But the operational contents targeted a single engineer. My primary administrative credentials were downgraded to basic monitoring status. My emergency deployment access was completely revoked. My database permissions were reduced to read-only.
Brandon Miller was formally designated as primary on-call lead for all production infrastructure. The engineering channel remained completely silent for over fifteen seconds. Then Brandon posted: “Received with thanks. ”
Victoria added: “Standardized access management is essential for Cloud Arc’s long-term growth.
Everyone is expected to cooperate fully. ”
I read the announcement without an emotional response. Moments later, I entered a formal reply into the public channel: “Received. Please update the incident responsibility registry accordingly to reflect that administrative execution rights have been transferred and log dual approval requirements for emergency access.
”
Bradford replied instantly: “You do not need to instruct me on how to manage my department. ”
“Not instructing. Creating an immutable audit record. ”
Before anyone else could respond, the glass door of the main conference room swung open.
Bradford stood in the entryway, anger flashing behind his eyes. “Nathan, step inside this office now,” he commanded. He led me into a small meeting room, Victoria following closely. Two printed documents rested on the desk.
One was a production access handoff certificate. The second was an emergency system responsibility acknowledgement. Bradford tossed a pen onto the desk. “Sign both forms immediately.
”
I picked up the papers and read every line. The handoff form stated: “I hereby certify that I have fully transferred all production system credentials, emergency recovery keys, and operational procedures to Brandon Miller. ”
The responsibility acknowledgement stated: “I agree to cooperate unconditionally during any production incident and accept full personal liability for operational losses resulting from system disruptions. ”
It was a classic corporate trap.
Deprive the engineer of all administrative authority, but legally obligate him to absorb all failure liability. Management takes all the credit; the engineer takes all the blame. I pushed the papers back across the glass table. “I am happy to sign the access transfer certificate once it accurately reflects my reduced permissions,” I said calmly.
“However, I will not sign a document claiming responsibility for production systems I no longer have authority to manage. ”
Bradford let out a harsh laugh. “Stop hiding behind legal bureaucracy, Nathan. Cloud Arc pays you a substantial salary to solve problems, not to act like an untouchable monarch.
”
Victoria tapped her nails against her folder. “You have displayed a troubling pattern of defiance regarding leadership decisions, Nathan. ”
I looked directly into her eyes. “I have a strong preference for lawful management decisions.
May I take these proposed responsibility agreements to corporate legal counsel for formal review? ”
Victoria’s composure flickered. “These are internal managerial documents,” she snapped. “They do not leave this room.
”
“Then invite corporate legal counsel to join our meeting right now,” I suggested. Bradford slammed his palm against the table, jumping to his feet. “Do you honestly believe this firm cannot survive without you? ” he bellowed.
I didn’t answer verbally. I pulled out my phone, unlocked the screen, turned the active red recording icon face-up, and set the device in the exact center of the table. “Brad, we may continue our discussion,” I said smoothly. Bradford stared at the red light, his throat moving as he swallowed hard.
Victoria sat up straight, her eyes widening. “What do you think you are doing? ” she demanded. “Protecting both parties.
When facts are documented in real time, misunderstandings are far easier to resolve before regulatory boards. ”
Bradford stared at me for several agonizing seconds. Then he forced a cold smirk, grabbed the two forms, and ripped the signature pages in half. “Fine.
You want strict procedure? ” he spat. “Effective immediately, you are relegated to basic operational support. Your annual performance score will be reduced to unsatisfactory.
”
Victoria offered no objection. She opened her notebook and scribbled several lines. I knew precisely what words she was writing: uncooperative, negative attitude, poor team alignment. Those vague corporate labels seemed harmless on paper.
But by the end of the fiscal year, management used them to strip an employee’s bonus and justify termination. That afternoon, I abstained from touching any production servers. Instead, I completed three vital tasks: I preserved the audit logs from the previous night’s emergency migration, I documented the rejected risk assessments, and I secured a cloud infrastructure vendor preservation receipt covering all access records. The mandatory assembly convened in the 11th-floor auditorium at 9:00 the following morning.
The hall was filled with staff from engineering, logistics, finance, sales, and administration. Bradford stood at center stage holding a wireless presenter. Victoria sat in the front row with her tablet ready. Brandon Miller sat two rows ahead of me, his spine straight, his head held high.
The presentation began with standard slides about operational discipline. Then Bradford clicked to the third slide. Projected in giant text was my name: “Nathan Vance. 90 minutes late.
$500 penalty. Performance review under immediate observation. ” At the bottom: “Technical senior leadership must set the standard for compliance. ”
A murmur rippled through the auditorium.
An account manager turned to stare at me. Two logistics coordinators whispered behind their hands. People only witnessed the person blocking a blow, never the aggressor who threw it. Bradford pointed his laser at my name.
“This disciplinary measure is not personal,” he declared. “But Cloud Arc cannot be held hostage by individual egos. Production infrastructure belongs to the enterprise, not to any single engineer who uses technical complexity as a shield. ”
Victoria took the microphone.
“Human resources reminds all staff that management possesses full legal authority to enforce workplace discipline against employees who violate company policies. ”
I raised my hand calmly. The auditorium fell silent. Bradford narrowed his eyes.
“Do you have a question, Nathan? ”
I stood up. “First, the official emergency dispatch log from three days ago proves I worked on production servers until 6:40 in the morning to resolve a P1 outage. Second, I request that human resources identify the specific statutory provision authorizing a direct $500 wage penalty against a salaried professional.
”
A dozen senior managers looked up from their phones. Victoria’s pen stopped moving. “The employee handbook outlines attendance regulations,” she stammered. “Which page and which section authorizes monetary payroll deductions?
” I pressed. “I fully accept that unexcused lateness can impact performance metrics. But under Title 29, United States Code, Section 203, an employer cannot arbitrarily confiscate earned wages without statutory authorization. ”
No executive spoke.
Victoria flipped through her binder with visible agitation. “We will address legal technicalities privately after this meeting,” she said defensively. “Excellent. Please ensure that my legal inquiry and your response are fully documented in the official meeting minutes.
”
It wasn’t a total victory, but it shattered their rehearsed narrative. Bradford quickly reclaimed the microphone. “Nathan, do not convert a corporate assembly into a personal grievance hearing,” he said brusquely, changing the slide. “Moving forward, Brandon Miller will serve as sole primary on-call lead for all production infrastructure incidents.
”
Brandon stood and bowed slightly. Scattered applause followed. In the main hallway, Scott Bradley, director of operations for Horizon Pharmacy Network, intercepted me. “Nathan, I don’t care about internal IT politics,” Scott said, his face tense.
“Horizon’s national pharmacy promotion begins at 8:00 tomorrow morning. We process over $1 million in prescription orders every single hour. Do not let your platform fail. ”
“I have already filed the technical risk assessment in ticket 4,271, Scott,” I informed him calmly.
Scott frowned. “I don’t care about tickets. I care about operational uptime. ”
Bradford strolled past at that exact moment and slapped Scott on the shoulder.
“Rest easy, Scott. Brandon Miller is assigned as primary on-call lead. Personal disagreements will not impact your promotion. ”
Scott looked at me with cold skepticism.
“It had better work. If our pharmacy network experiences checkout failures, financial damages will be catastrophic. ”
At 8:00 the following morning, Cloud Arc’s headquarters buzzed with frantic energy. Sales teams gathered around revenue monitors, watching Horizon’s promotion numbers climb.
The engineering display wall showed bright green. Too green. From my corner desk, I monitored the read-only telemetry dashboard. Cash routing queue latency was creeping upward.
The payment pipeline was stuttering. Yellow warning bands expanded across the screen. I sent a quiet message to Bradford: “Recommend executing cash route failover now before peak morning traffic overloads the primary queue. ”
He replied instantly: “Are you actively wishing for a corporate failure just to prove yourself right?
”
I closed the messaging window and smiled faintly. Arrogant managers always confused a technical warning with a curse simply because they knew the warning was accurate. At 9:00, Bradford gathered the department. “Today marks Brandon’s first independent execution of a major enterprise shift,” he announced proudly.
“Everyone offer him full support. ”
Brandon sat at the primary console, my printed emergency binder open beside his keyboard, sticky notes covering the pages. I glanced at his binder and froze. Several critical remediation steps had been rearranged in the wrong sequence.
“Step two cannot be executed prior to freezing the primary transaction queue,” I advised quietly. Brandon looked up, his face flushing. “Bradford told me you are passive support only, not command. ”
“I am not commanding you, Brandon.
I am telling you that if you process route shifts in that order, you will lock the entire database. ”
Bradford marched over, his face red. “Nathan, return to your assigned desk immediately. ”
The entire floor fell dead silent.
Bradford stepped close, lowering his voice just enough for nearby engineers to hear. “You have zero deployment authority here,” he sneered. At 10:20 in the morning, the first crimson alert detonated across the engineering monitoring wall: “Primary payment gateway response failure. Transaction timeout exceeded.
”
Within ninety seconds, customer support phone lines exploded into a continuous, deafening wall of ringing. Scott Bradley sprinted onto the floor, his tie loosened, his face pale. “What is happening to the pharmacy checkout pipeline? ” he screamed.
“Store registers across three states are declining prescription payments! ”
Brandon began typing frantically at the primary console, sweat beading across his forehead. “I am inspecting cluster metrics right now! ” he yelled, his voice cracking.
Bradford stood behind him, barking panicked orders. “Follow the printed binder. Execute the failover sequence. ”
I sat quietly at my spectator desk.
My read-only laptop displayed the cascading disaster, but my credentials possessed zero execution privileges. Red alert lines multiplied across the screen. I published a concise technical guide in the engineering channel: “Failure can still be contained within a 40-minute recovery window. Mandatory sequence: execute cash route isolation, freeze transaction queue, process order compensations.
Primary incident owner must issue written authorization to proceed. ”
Bradford immediately replied: “You are on suspension. Do not interfere with authorized personnel. ”
At 10:45, the unprocessed transaction backlog doubled.
At 11:15, dozens of Horizon retail outlets were forced to shut down electronic checkout lines and shift to manual paper processing. Scott Bradley turned on Bradford with wild eyes. “Our client executive board is on the line right now! They want to know who is responsible for this catastrophe!
”
Bradford turned toward me, his arrogance dissolving into desperation. “Nathan, come over here and fix this console immediately. ”
I stood up slowly. “Restore my full administrative credentials in the system registry and provide a written authorization memo signed by you as primary incident owner,” I stated calmly.
Bradford flinched as if he had been slapped. “The corporate house is burning to the ground and you are negotiating paperwork! ”
“This is not a negotiation, Bradford. This is the operational liability boundary.
”
Everyone on the floor was watching us. Victoria moved beside me, her voice dropping to a harsh whisper. “If you refuse to assist the enterprise during an active crisis, Nathan, legal and professional consequences will be catastrophic for your career. ”
“The more severe operational consequences become, Victoria, the more essential strict legal compliance becomes,” I answered without flinching.
At 12:00 sharp, Brandon attempted to manually alter cash routing weights. Three minutes later, his improper sequence triggered a total database lock. The monitoring wall transitioned from crimson to deep purple — the universal indicator of a total system freeze. Nina Jenkins stood up from her desk.
“Stop touching the terminal, Brandon! You just locked secondary transaction logs! ”
Brandon pulled his hands away from the keyboard, his face drained of all color. Scott Bradley answered another call, his voice shaking.
“I understand, director. Yes, we are attempting to restore access. ” He hung up and stared at Bradford with pure fury. “Horizon has just initiated contract termination proceedings.
We are losing over $200,000 every single hour. ”
At 2:00 in the afternoon, the platform remained completely paralyzed. A third-party consultant hired by Bradford logged in remotely but possessed zero understanding of our custom architecture. At 3:30, Horizon’s corporate legal team formally served Cloud Arc with a notice of intent to seek commercial damages.
At 5:40, Clare Dupon from finance entered the floor carrying an updated loss ledger. “Total direct operational losses and contractual penalty claims have crossed $1,800,000,” she announced grimly. At 5:50, Bradford opened the glass door. His hair was disheveled, his collar unbuttoned, his eyes bloodshot.
“Nathan, the general manager has arrived. Step into the executive boardroom. ”
I closed my laptop. “Are you restoring my credentials and issuing written authorization?
”
His jaw clenched so tight his facial muscles twitched. “General Manager Henderson is convening an emergency board review right now. ”
The executive boardroom was packed. General Manager Richard Henderson sat at the head of the table, his face stern.
On the projector screen, the outage timeline was displayed: 10 hours continuous downtime. $1,800,000 financial loss. Every eye turned toward me as I entered. Bradford immediately stepped forward, holding the crumpled $500 fine notice from three days prior.
“General Manager Henderson,” he began loudly, “three days ago, Nathan Vance was disciplined for gross tardiness and fined $500. When our primary platform experienced a technical glitch today, Nathan sat at his desk for 10 hours and intentionally refused to touch the console, allowing this enterprise to suffer $1,800,000 in damages out of personal malice. He cannot be permitted to escape total liability. ”
Victoria stepped up beside him.
“Human Resources confirms that Nathan has exhibited a continuous pattern of insubordination, policy defiance, and hostility toward corporate management. ”
Scott Bradley slammed his fist onto the table. “I don’t care about your internal personality clashes! Who actually owns technical responsibility for this platform?
”
Richard Henderson turned his piercing gaze toward Bradford. “Walk the board through the exact timeline of events. ”
Bradford spoke rapidly. “Initial alert occurred at 10:20.
Brandon Miller followed our approved operational protocols. Nathan actively sabotaged recovery efforts by refusing to cooperate and demanding legal paperwork while the platform was down. In my professional judgment, Nathan placed his personal ego above the survival of Cloud Arc. ”
Victoria pushed a stack of documentation toward Richard.
Then Cloud Arc’s senior legal counsel, Rachel Montgomery, entered the room carrying a thick stack of compliance dossiers. Her first sentence was delivered with absolute professional detachment. “We will establish undeniable legal facts before evaluating managerial emotions. ”
Bradford’s cheek twitched nervously.
Emotions could be debated. Immutable system records offered zero room for negotiation. Rachel turned first to Victoria. “Which specific section of the employee handbook or state labor code authorized a direct $500 wage deduction against Nathan Vance for 90 minutes of unexcused lateness?
”
Victoria gripped her pen tight. “The employee manual contains general provisions regarding attendance discipline,” she stammered. Rachel opened a master reference book. “I reviewed our corporate manual and state labor statutes.
Unexcused lateness permits attendance warnings and performance scoring adjustments. It does not authorize arbitrary wage confiscations or direct payroll penalties under Title 29, United States Code, Section 203. ”
Victoria pressed her lips into a thin line. “It was recommended as an internal management penalty by Vice President Hayes.
”
Clare Dupon added, “Payroll records confirm that human resources submitted a direct wage deduction ticket labeled ‘attendance fine. ’”
Victoria’s fingers trembled. She looked at Bradford for support, but he kept his eyes fixed on the table. The first individual pulled into the legal vortex wasn’t Bradford.
It was the HR director who had handed him the illegal whip. Rachel issued an immediate directive. “Victoria, cancel that payroll deduction ticket tonight. Issue Nathan a formal written retraction by 9:00 tomorrow morning.
Human resources disciplinary procedures will undergo an immediate external compliance audit. ”
All color drained from Victoria’s face. “Understood,” she whispered. I looked at the crumpled $500 memo on the table.
Three days ago, it had been used to humiliate me in the atrium. Now it was crushing the executives who issued it. Next, Rachel turned to Brandon. “Incident log shows that at 12:30 p.
m. you executed a manual route weight modification. Which operational protocol did you follow? ”
“The paper binder given to me by Vice President Hayes,” Brandon answered softly.
“Did you verify whether that binder represented the active version in the encrypted compliance repository? ”
“No. ”
“Did you possess verified administrative credentials or technical experience to execute cache routing shifts on an active production cluster? ”
Brandon’s head drooped.
“No. Not independent experience. ”
Scott exploded. “Then why did you report in the public engineering channel that the issue was merely a minor cash delay?
”
Brandon’s face burned crimson. “Vice President Hayes told me to keep the channel quiet,” he confessed. Nina Jenkins displayed backend telemetry. “The system was generating critical P1 alerts when Brandon posted that message,” she verified.
Brandon’s posture completely collapsed. “I was wrong,” he wept quietly. The hardest part for Brandon wasn’t losing temporary status. It was realizing he had never been valued as a rising leader.
He had merely been positioned in front of Bradford as a human shield. Rachel documented the findings. “Brandon Miller’s on-call privileges are suspended indefinitely. He is assigned to mandatory technical retraining and compliance re-evaluation.
”
Finally, Rachel turned to Bradford. She placed three master documents directly in front of him: the access freeze order, the rejected risk tickets, and the cloud audit preservation receipt. “Vice President Hayes, please explain your operational rationale. ”
Bradford sat up straight, attempting to project residual executive authority.
“I acknowledge certain administrative imperfections,” he began defensively. “But Nathan Vance displayed persistent uncooperative behavior, and this enterprise cannot remain dependent on a single technical lead. ”
Richard Henderson’s voice cut through the air like a razor. “So your solution to avoid single-point dependency was to freeze our principal lead’s access on the morning of our largest commercial promotion and hand execution rights to an inexperienced junior using an outdated draft?
”
“You were not dismantling a technical monopoly, Bradford,” I added calmly. “You were attempting to dismantle an immutable audit trail. ”
Bradford’s eyes flashed with rage. “Do not slander my managerial integrity!
” he shouted. I clicked my console mouse, projecting a final evidentiary file onto the screen. It was an audit log preserved by our cloud infrastructure vendor. It displayed file names, timestamps, and IP addresses — no proprietary source code, but immutable transfer metadata.
Core enterprise emergency recovery protocol. Exported by Bradford Hayes at 8:14 p. m. two nights prior via a temporary external download link.
Rachel’s pen stopped moving. “Who was the external recipient of that proprietary recovery protocol? ”
Bradford’s temple twitched violently. “An external technical consulting firm assisting our division,” he stammered.
Richard’s voice sharpened. “Which consulting firm? Where is the executive procurement authorization? ”
Bradford’s answer was barely audible.
“It had not reached formal procurement yet. ”
“So you transmitted a core proprietary trade secret outside our enterprise network without legal, security, or procurement approval,” Richard stated, his voice trembling with fury. The room fell into total silence. Scott Bradley stood up, his chair crashing backward.
“Are you completely out of your mind? That recovery protocol governs our entire pharmacy network! ”
Richard motioned for Scott to sit down. Bradford’s shoulders began to shake uncontrollably.
“I was attempting to secure a backup vendor to protect the enterprise,” he pleaded. “By manufacturing an artificial outage, sabotaging internal recovery, and framing your principal lead,” Richard countered coldly. Bradford’s head drooped. Victoria lowered her face into her hands.
Brandon refused to look at Bradford. At 8:30 p. m. , an executive broadcast notice was published across Cloud Arc corporate channels:
The $500 attendance penalty against Nathan Vance is officially cancelled and expunged.
All disciplinary notices are withdrawn. Bradford Hayes is relieved of all managerial authority pending formal legal investigation. Brandon Miller’s on-call credentials are suspended.
Nathan Vance is appointed interim director of infrastructure stability.