Story code: ST-001874
Part 2: Circular Dependencies
The phone vibrated again, spinning slightly on the slick granite countertop. David unlocked the screen. The direct message from Connor was a block of text sent at 2:42 AM.
*Connor Vance [2:42 AM]: Hey Dave. Saw you were still online in the commit logs. Need a massive favor. VP announcement means I have to present to the board at 9 AM. Need you to throw together a ten-slide deck detailing the migration architecture. Make sure it highlights the new resource-allocation strategy I implemented. You’re a lifesaver. We’ll talk about getting you some comp time next quarter.*
David stared at the screen. The “resource-allocation strategy” was Connor going to a golf resort in Arizona and telling David to handle everything.
Another message popped up.
*Connor Vance [2:43 AM]: Also, saw you got the mid-year review. Don’t take the promo denial personally. You’re a great code monkey, but HR wants to see more ‘big picture’ leadership before we move you to architecture. We’ll get you there.*
David looked down at the two identical signatures on the countertop. The thick blue ink. The jagged cross of the last consonant. Connor wasn’t just taking credit for David’s work. Connor was the anonymous head of the Cedar Grove Homeowners Association Compliance Committee. Connor was the one who had issued the warning for the two-point-six-inch grass.
The realization hit David like a physical blow. It wasn’t a coincidence. Connor knew exactly where David lived; he had approved David’s relocation package three years ago. Connor knew David’s salary, knew he had depleted his savings paying for his mother’s medical bills, and knew David couldn’t afford to quit. By bleeding him with HOA fines, Connor was ensuring David stayed desperate, chained to his desk, churning out the code that fueled Connor’s promotions. It was a closed-loop system of exploitation.
David didn’t throw the phone. He didn’t scream. The panic and exhaustion that had been drowning him for a week suddenly crystallized into a cold, sharp focus. He was a senior backend engineer. His entire career was built on dismantling complex systems, finding the logic flaws, and breaking them.
He opened his laptop on the kitchen island. The bright screen illuminated the dark circles under his eyes. He bypassed his company VPN and navigated straight to the Cedar Grove HOA portal, downloading the complete, seventy-page PDF of the neighborhood bylaws.
If Connor was running the HOA, he had likely drafted or heavily amended these rules. And David had spent three years cleaning up Connor’s code at work. Connor was a lazy architect. He liked nested conditions, infinite loops, and unchecked authorities. He never wrote tests. He always left a backdoor.
David opened his text editor, placing it side-by-side with the PDF. He began treating the legal document like legacy spaghetti code, mapping out the dependencies.
*Rule 4B: Grass height.* This pointed to *Section 8: Penalties*, which pointed to *Section 9: Appeals*.
He traced the logic flow. If a homeowner received a fine, they had fourteen days to appeal. The appeal had to be reviewed by the Compliance Committee. The committee was comprised of three anonymous members appointed by the HOA President. The President was Connor. It was a circular dependency. The judge, jury, and executioner were all the same variable.
A chime sounded from his email client. An automated alert from the HOA portal dropped into his inbox.
David clicked it. The subject line read: *NOTICE OF ESCALATION AND INTENT TO LIEN.*
He opened the attachment. It wasn’t just the grass. It was an aggregated list of infractions, backdated to incidents he had never received initial warnings for.
*March 12: Trash receptacle visible from street after 8:00 PM. Penalty: $250.*
*April 4: Unauthorized window treatments (blinds not perfectly horizontal). Penalty: $300.*
*April 28: Driveway oil stain exceeding 4 square inches. Penalty: $500.*
Combined with the grass fine, the total balance due immediately was $1,550.
The bottom of the notice contained a boilerplate legal threat: *Failure to remit payment within 48 hours will result in a lien placed upon the property at 424 Elm Street, pursuant to Section 14, Paragraph C of the bylaws.*
David opened a new tab and checked his bank account. Available balance: $412.18.
His chest tightened. The air in the kitchen felt thin. A lien meant they could freeze his assets and eventually force a foreclosure. Connor wasn’t just trapping him; Connor was going to take his house. If David fought back at work, Connor would fire him, guaranteeing he couldn’t pay the fines. If David paid the fines, he would have to take out a high-interest loan, plunging him further into debt and reliance on his paycheck.
He forced his eyes back to the bylaws. There had to be an unhandled exception. He scrolled through the document, his eyes scanning the dense legalese, looking for a structural weakness.
He found it buried on page sixty-one. *Section 12, Subsection D: Committee Member Conduct.*
*”Any acting member of the Compliance Committee or Executive Board found to be in violation of a Level 1 Community Standard (including but not limited to structural modifications, unapproved landscaping, or exterior neglect) shall have their enforcement authority and voting rights immediately suspended pending a full disciplinary hearing by the general assembly.”*
David read the paragraph three times. It was a hardcoded override. If a committee member committed a violation, the system automatically revoked their admin privileges. No appeal to themselves. No anonymous protection. If Connor’s powers were suspended, the pending lien against David’s house would be frozen in the system.
His phone buzzed again with another Slack notification.
*Connor Vance [3:14 AM]: Just looked at your timesheets, Dave. The late nights are a red flag for your time management skills. HR agrees we need to put you on a Performance Improvement Plan. Let’s discuss it at 8:00 AM before I present your deck to the board. Don’t be late.*
A PIP. It was the first step to termination. Connor was squeezing every last drop of usefulness out of him for the 9 AM presentation, then setting him up to be fired once the database migration was perfectly stable.
David looked at the time in the corner of his screen. It was 3:17 AM. He had less than five hours to build a ten-slide presentation praising his abuser, or he would be fired. He had forty-eight hours to find fifteen hundred dollars, or he would lose his home.
He looked at the digital micrometer resting on the counter next to the plastic bag of grass clippings.
Connor lived three streets over, in the massive corner-lot house with the wrap-around porch. David didn’t just need to find a violation on Connor’s property; he needed to find something undeniable, a catastrophic failure of the rules that would instantly trigger Section 12, Subsection D before 8:00 AM.
David closed his laptop. He didn’t start the slide deck. Instead, he grabbed his flashlight, picked up the micrometer, and walked out his front door into the suffocating darkness.