Story code: ST-001017
Part 2: How the Rule Started Spreading
By the time Maya asked that last question, the room had stopped moving like a bedroom and started moving like a test bench. The ring light stayed on over the desk. Jenna sat cross-legged on the bed with her phone aimed at the laptop screen to catch every warning as it appeared. Eli stood beside Maya reading menu labels out loud one at a time. Rosa stayed in the doorway with the charger cable looped around her hand, listening for wording changes. @ModNorth still had not explained how a rule could be about Jenna, then about “draft-adjacent controls,” then about the folder itself without any visible source behind it.
Maya did not argue the point in general. She narrowed it. “We’re going to test one small action at a time,” she said, and she put each result into the group chat with a timestamp.
First Eli used Jenna’s account to try renaming a draft from the folder preview panel. The rename field flickered open and then closed with the same message: “Access limited by admin policy.” Jenna grabbed the screenshot before the pop-up disappeared. Maya pasted it under the earlier ones.
Then Eli used the helper account to open the same draft preview. That account could still see the title. It could not move the draft into the posting queue. Different action, different account, same folder. He read the warning from his phone: “Action restricted due to ongoing integrity hold.”
Rosa straightened in the doorway. “That’s new wording.”
Maya scrolled up and read the first denial, then the new one. The first had said admin policy. The second said integrity hold. Neither showed where the rule lived, what triggered it, or how long it lasted.
She sent a clean message to @ModNorth: “Are ‘admin policy,’ ‘rule compliance clearance,’ and ‘integrity hold’ the same thing?”
The answer came back in less than a minute. “Different interface labels for the same enforcement state.”
“Where is that defined?” Maya asked.
No source came with the reply. Just another statement: “Admins are not required to disclose internal moderation architecture.”
Jenna set the phone down long enough to try something even smaller. She opened a draft she had already captioned earlier that week through a notification shortcut, not through the folder. The caption field loaded. The image loaded. When she hit save without changing anything, the draft vanished back to the dashboard and the same warning appeared again. She stared at the screen, then handed the phone to Maya.
“That wasn’t opening the folder,” Jenna said. “That was a notification.”
Maya asked @ModNorth if the alleged rule now covered notifications too. The answer: “If the notification leads to restricted draft assets, yes.”
Rosa said, “So now the rule follows the path, not the person or the folder?”
Nobody in the room answered her right away because the message thread answered for them. When Maya pushed again and asked whether comments, captions, and tags connected to a restricted draft were also blocked, @ModNorth wrote, “Any derivative workflow may be paused to preserve draft integrity.”
Eli turned the laptop slightly so everyone could see the page controls. “Tags are in a different menu from drafts,” he said. He clicked into a caption bank that usually fed several drafts at once. One caption attached to Jenna’s blocked meme was now marked unavailable. Another caption from the same week was still editable. He compared the timestamps. The blocked caption had been saved after the first admin warning. The editable one had been saved before.
Maya took another screenshot.
She was not building a theory out loud. She was building a sequence. First the folder was blocked. Then sorting was blocked. Then renaming. Then queueing from a helper account. Then saving from a notification. Then one caption attached to one draft was suddenly unavailable under a term the platform menus never used.
She sent another plain request into the thread: “List the exact platform controls this rule touches, using the labels visible to users.”
The response took longer this time. When it came, the wording shifted again: “Not all affected surfaces display the same public label. Enforcement is discretionary based on relationship to the protected draft environment.”
Rosa gave a short laugh with no humor in it. “Protected draft environment? Is that a setting on the page or is he just making names up as he goes?”
Maya did not answer for @ModNorth. She opened the permissions screen again and recorded the visible options one by one: role, posting access, comment moderation, message access, ad permissions. Nothing on that page said protected draft environment. Nothing said integrity hold. Nothing said rule compliance clearance.
Then Eli tried one more neighboring action. He used the helper account to duplicate a different meme draft from the same week, one Jenna had not touched that day. The duplicate button worked. He tried duplicating the blocked draft. The button was visible, then grayed out after one click, and the warning changed again: “Item unavailable under current admin restrictions.”
Maya looked at the thread, then at the permissions screen, then back at Eli’s screenshot. Same alleged rule. Fourth wording. Third boundary. Still no source.
She typed one sentence and read it aloud before sending it: “If this is one real rule, why does it keep changing names and expanding to whatever action we test next?”
This time @ModNorth did answer, but not with a definition. The account sent a fresh notice into the thread instead: “Further permission audits may be applied to associated contributors while review remains active.”
Jenna lifted her phone again. Maya opened the role panel. Eli refreshed the dashboard. And all three of them were looking at the same new question when the screen loaded: associated contributors now meant who, exactly, and what would happen if the anonymous admin pushed that invisible rule onto the rest of the page.