She Reassigned My Project to an Intern. I Migrated the Repo and Destroyed Their Sprint Review

They Reassigned My Project To An Intern Friday. I Migrated The Repo Sunday. Monday’s Sprint Review Was Fifteen Minutes Of Stunned Silence…

Part 1


The last message I sent before it all unraveled was a pull request comment: Please review the updated fraud trigger logic. It finally catches synthetic IP trails without overfitting. Should reduce false positives by 19%.

It was the kind of comment you leave when you’re tired but proud. Not proud in the LinkedIn way, where people are proud to “circle back” and “drive alignment.” Proud in the quiet, private way, where your shoulders unclench because the math finally behaves and the edge cases stop screaming at you in red.

The next morning, the pull request was gone.

So was the entire repo.

I noticed it in the breakroom while eating stale pretzels from a vending machine that charged like it was a luxury boutique. I was scrolling through notifications on my phone the way I always did when I wanted to avoid Trent from sales. Trent had a permanent sheen, like he moisturized with Axe body spray and questionable tax deductions. He waved at me once, and I pretended not to see him by staring harder at my screen.

I refreshed GitHub. Then I refreshed again. The page blinked into a polite error: 404. Not found.

No fork. No archive. No warning. Just the digital equivalent of someone looking you in the eyes and saying, I don’t remember you.

A second later, an email arrived.

No greeting. No sign-off. Just:

hi camila. for transparency. the predictive risk engine has been reassigned to kyle (intern summer rotation). please provide a knowledge transfer doc by EOD.

I laughed so loudly a junior dev dropped her LaCroix. The can hit the counter and hissed like it was judging all of us.

Kyle.

The same Kyle who once asked me if the backend was “the place where the emails go.” Kyle whose crowning achievement last sprint was changing a button color to what he described as “Bitcoin blue,” then accidentally breaking half the CSS in dark mode. Kyle whose pull request descriptions read like fortune cookies written by someone with a mild concussion.

That Kyle.

They didn’t even call it a demotion. They called it a learning opportunity, which is corporate for: you built something valuable, so we’re going to hand it to a golden retriever in a startup hoodie and then call you “collaborative” when you smile about it.

My first instinct was to march into Aaron’s office and ask him what kind of mind-altering wellness tincture he’d started microdosing.

My second instinct was to do something quieter, sharper, and more permanent.

Because here’s what they forgot about me: I didn’t build things like sandcastles. I built them like vaults.

The predictive risk engine, the one they liked to call “the fraud filter” as if it was a cute little plug-in you grabbed off a shelf, wasn’t a filter. It was a system. A web. A living set of assumptions and counter-assumptions that learned patterns the way good investigators learned lies.

And I didn’t build it in isolation. I built it in a company where access was political, credit was currency, and “agile” meant the loudest person in the meeting got to rewrite reality.

I stood up, tossed my pretzels, and walked back to my desk. People did that thing they do when trouble walks past: their eyes looked busy while their attention snapped to you like static.

At my monitor, I opened the company wiki page for the engine. I already knew it would be there: my name, in tiny letters at the bottom, like an ingredient list.

Primary Owner: Camila Reyes.

And now, apparently, Primary Owner: Kyle, Intern Summer Rotation.

I clicked our internal repo mirror. Access denied.