Story code: ST-000057
Part 2: When the Rule Spread Past the Laptop
By Tuesday, Derek Collins was still calling it a compliance issue, but the rule now changed depending on what object Jenna Morales touched and who happened to be asking questions. That was when the bluff stopped looking like a private roommate argument and started leaving a work trail. The morning began with a simple attempt to avoid another scene. Jenna set her laptop on the desk, angled the screen toward the wall, and used the built-in camera only long enough to check framing before her first call. Derek appeared in the doorway almost immediately. “No activation without clearance,” he said. Jenna did not raise her voice. “It’s a framing check.” “Still counts.” She asked, “Clearance from who?” “From the household side.” That was new wording again. Not landlord. Not building. Not lease. Not any named policy anyone could verify. Just household side, as if there were an office somewhere past the laundry closet. At 9:12, Marisol sent a calendar update moving Jenna off a client-facing slot and onto note-taking for the day. The message was short and flat: Until this is clarified, I can’t put you in a role that requires camera participation and may fail at the last second. That was the first concrete loss outside the bedroom. Same job, same team, but not the same work. Jenna saved the message and sent back: Understood. Still no written source from him. Marisol replied: Then ask for one in writing. So Jenna did. She texted Derek from ten feet away because that created a cleaner record than another doorway argument. Please send me the house work compliance rule you’re enforcing about my laptop camera. I need the source, who issued it, what devices it covers, and why it applies during my work meetings. Three dots appeared, disappeared, and came back. What Derek finally sent was a paragraph full of authority language and no authority. It said the camera restriction was part of shared-home compliance expectations, intended to regulate visible business broadcasting, and enforceable during standard work periods. It did not name a lease clause, building notice, employer request, city rule, or any person besides Derek. Jenna forwarded the screenshot to Marisol. The answer came back in under three minutes. This is not a policy source. This is him restating himself. That was the first work-side sentence that treated the whole thing exactly as it looked. The same afternoon, the cross-application problem got worse. Jenna was in the kitchen scanning a grocery receipt with her phone for a reimbursement app tied to her health stipend. Derek saw the camera screen light up and said from behind the counter, “That falls under the same restriction if it connects to your employment.” Jenna asked, “So a receipt scan in the kitchen is now controlled by the same rule as my laptop camera in my bedroom?” He said, “If it enters a work system, yes.” A few hours later he walked through the hall while she was using her laptop camera to unlock a banking app with facial recognition. “No camera use during business hours,” he said again. Jenna answered, “This is my bank.” He said, “You’re still on the clock.” The supposed rule had now spread from client calls to phone photos, camera diagnostics, receipt scans, and personal app login. Every expansion made the original claim harder to pin down. The object stayed the same, though: camera on, Derek objecting, no source named. By Wednesday morning, Marisol stopped treating it as a weird anecdote and started treating it as an attendance risk. She asked Jenna for timestamps, screenshots, and the exact words Derek had used. Jenna sent the work chat, the text thread, the rescheduled meeting notice, and a list of the rule’s changing labels: house work compliance, residential work restriction, household side, visible business broadcasting. Marisol then asked one question Jenna had already asked several times in person. Who issued the rule? Jenna texted that one to Derek exactly as written. His response came back twelve minutes later. It’s understood authority in a shared environment. I shouldn’t have to explain basic compliance management every time. No name. No office. No document. Not even a fake committee. Just another layer of language over the same empty center. That was enough for Marisol to move it one step out of ordinary supervision. She sent Jenna a message saying she was looping in operations because a claimed outside restriction was now interfering with required work participation. A short email followed, copied to Jenna, asking for clarification on whether there was any legitimate housing, safety, privacy, or legal rule that barred routine laptop camera use in Jenna’s room during scheduled business calls. The wording in that email was calm enough to be deadly. It did not argue with Derek. It simply asked for source and scope. Derek saw Jenna reading it at the desk that afternoon and asked, “Why is your job involved in house procedure now?” Jenna turned the screen slightly so he could see the subject line and said, “Because you told me to explain it to them as a residential work restriction.” He stayed at the doorway longer than usual, then said, “They don’t get to review internal home compliance.” Jenna asked, “Then why does it control whether I can appear on a work call?” He answered in pieces this time. “Because the camera creates exposure. Because the house has standards. Because I already said so.” None of that matched the question in Marisol’s email, and none of it answered who had issued anything. Late that evening, another message landed in Jenna’s inbox, this one copied from operations to a neutral reviewer named Alicia Grant. It was brief. If a third-party restriction is being asserted as a barrier to essential remote-work participation, please identify the issuing authority and provide the exact rule language for our records. All at once, Derek’s made-up camera rule had a record request attached to it, and the next step was no longer Jenna asking from her desk. It.