At AstraCorp, My Mother Demanded I Hand Over My $80M Project to My Failing Brother – My Single Question Exposed Everything
Eleanor’s call left me with a burning sense of injustice, but also a renewed clarity. Her denial was absolute, her gaslighting relentless. This wasn’t just about a leaked memo; it was about a systemic pattern, one I had lived with my entire life. My thoughts drifted back to earlier, seemingly unrelated frustrations with Project Horizon.
I decided to go through the project’s entire development log, not just for recent issues, but from the very beginning. I called David again, asking him to join me in my office, stressing the need for complete discretion. The door was closed, the blinds drawn, creating a bubble of confidentiality.
“David,” I began, “I need your help with something beyond the memo. I need to review all of Project Horizon’s early development phases, especially any anomalies or unexplained issues.”
He set up his laptop, connecting it to the large monitor on my wall. We started sifting through months of data: code commits, system performance logs, access records, and bug reports. It was tedious work, a deep dive into the digital history of my project.
“What exactly are we looking for?” David asked, his fingers flying across the keyboard, pulling up various metrics.
“Anything that felt… off,” I replied, staring at the scrolling data. “Any unexplained slowdowns, performance dips, or minor system glitches that never quite made sense.”
We worked in silence for a while, the rhythmic hum of the servers filling the room. David highlighted a few minor errors, attributing them to early-stage development bugs or network fluctuations. But as we dug deeper, a pattern began to emerge, subtle yet distinct.
“Look at this,” I said, pointing to a cluster of small, almost imperceptible system anomalies. “October 15th, November 3rd, December 12th… these were all periods where we saw slight dips in processing power, or small delays in data rendering.”
David zoomed in on the dates, cross-referencing them with the system’s access logs. His fingers paused, then moved quickly, pulling up another set of records.
“Interesting,” he murmured, his brow furrowed in concentration. “These dates… they coincide with Mark Jensen’s ‘oversight access’ periods.”
My heart gave a sudden lurch. “Oversight access?” I repeated, my voice sharp. “What oversight access? He had no official role in Project Horizon’s early development.”
David pulled up a series of internal emails, all originating from Eleanor’s office. They were directives, formally granting Mark “temporary, read-only oversight access” to Project Horizon’s backend systems. The stated reason was always vague: “to familiarize himself with the project’s scope,” or “to provide a fresh perspective on integration challenges.”
“Eleanor granted these directly,” David confirmed, pointing to her digital signature on the access requests. “Each time for a short, defined period. But she always specified full system access, not just high-level overviews.”
A cold wave washed over me. This was the specific, insidious cruelty I had suspected. The little, nagging issues, the “glitches” that had always bothered me but were too minor to flag as serious problems. They weren’t accidental. They coincided precisely with Mark’s unauthorized “familiarization” tours. It was a drip-drip of undermining, designed to subtly hinder progress and make the project look less efficient than it was.
“He wasn’t familiarizing himself, David,” I stated, my voice low and laced with a bitter certainty. “He was tampering.”
David didn’t respond immediately, his eyes still scanning the logs. The evidence was circumstantial, but the correlation was too striking to ignore. The dates of the “glitches” and the dates of Mark’s “oversight” were perfectly aligned. It was a pattern, a quiet, insidious form of sabotage that had gone unnoticed for months.
“The resource dips, the rendering delays… they were never severe enough to trigger an alert,” I mused, remembering my past frustrations. “We always just patched them, optimized a bit more, assumed it was a standard development hurdle.”
“Precisely,” David said, now looking at me, his expression grave. “It was designed to be just below the threshold of alarm. Enough to slow you down, to make it seem like the project was encountering more ‘technical difficulties’ than expected, but not enough to point to deliberate interference.”
The realization hit me with the force of a physical blow. Mark wasn’t just leaking memos; he had been subtly, deliberately sabotaging Project Horizon from the inside, under the guise of “oversight.” And Eleanor had provided him with the key. This wasn’t just favoritism; it was active complicity in undermining her own daughter’s work.
The personal cruelty of it was stark. All those extra hours I had put in, troubleshooting phantom bugs, pushing my team harder to compensate for unseen delays. All those moments of self-doubt, wondering if I was missing something, if my management was truly up to par. It had all been meticulously orchestrated, a quiet campaign of psychological warfare designed to wear me down, to make Project Horizon appear less robust.
My mother, Eleanor, had given him the keys to my kingdom, allowing him to subtly poison the well, making me question my own competence. It was an insidious betrayal, far more painful than any open confrontation could have been. The subtle, almost invisible nature of the sabotage made it feel like a constant, unseen hand pushing against my efforts, making every step forward harder.
“Can you trace the exact actions taken during those ‘oversight’ periods?” I asked, my voice tight with resolve. “Not just that he logged in, but what he *did*.”
David nodded, his fingers already moving across the keyboard.
“It will take some time. We can pull the full activity logs for those sessions. It’s usually standard practice, though sometimes less detailed for ‘read-only’ access. But if he made any changes, however minor, they should be logged.”
“Find them,” I urged him. “Find every single one.”
The air in the room felt heavy with the weight of this new discovery. The leaked memo was just the tip of the iceberg. Beneath it lay a deeper, more systematic pattern of interference, orchestrated by Mark and enabled by Eleanor. It was a carefully constructed web of deceit, designed to slow Project Horizon’s progress, to erode its perceived value, and to ultimately justify handing it over to Mark.
I leaned back in my chair, picturing Eleanor, so composed, so dismissive on the phone. She had granted those accesses, knowing full well what Mark was capable of, or perhaps even instructing him to do it. The betrayal cut deep, not just as a professional setback, but as a profound personal wound. My own mother had allowed my brother to undermine my life’s work.
This realization solidified my understanding of the family dynamics: Mark’s incompetence wasn’t just tolerated; it was actively protected and, in this case, weaponized against me. The systemic glitches weren’t random occurrences; they were echoes of a deeply entrenched favoritism, a quiet cruelty designed to keep me from shining too brightly.
David continued to work, his concentration unwavering. I watched the lines of code, no longer seeing just data, but a narrative of calculated deceit. Every one of those “glitches” was a testament to Mark’s insidious efforts, and Eleanor’s complicity. The silent, invisible attacks were far more damaging than any open confrontation, as they forced me to doubt my own work, my own capabilities.
This wasn’t just about corporate politics; it was about the very foundation of trust within my family. That foundation had been systematically eroded, brick by invisible brick, by these subtle acts of sabotage. I needed concrete evidence, something undeniable that even Eleanor couldn’t dismiss as “imagination.” The next step was to confirm these were deliberate manipulations, not just random errors.
More Stories
+ There are no comments
Add yours