Story code: ST-000637
Part 2: The Rule Broke the Second It Touched Another Parcel
By the time the crowd at the Parcel Access Desk thinned, the question was no longer whether I was locked out. Everybody could see that on my access panel. The question was simpler and worse: if Dax Harlan’s rule was real, why couldn’t anyone in the Virtual Courthouse show it on a screen. Leon Price stayed at the counter with one hand hovering over his own wrist display. He wasn’t grandstanding. He kept asking short questions in the same flat voice people use when they want to know whether their bank card still works. “Run my parcel,” he said. Iris Chen hesitated, then answered carefully. “There is no active restriction on your boundary at this time.” “At this time?” Leon said. “So the same thing could be put on mine?” Dax stepped in before she did. “Only where conditions warrant it.” Leon looked at him. “What conditions?” Dax said, “Managed environment risk factors.” I said, “That’s another phrase, not a rule.” Iris reopened the policy lookup console and this time angled it more toward the public side, maybe because too many people had already seen enough to know she didn’t have a clean answer. The search field showed every version of what Dax had said: shared environment stability, occupancy restriction, managed environment risk factors, landlord controls. Results populated in fragments-community noise standards, commerce zoning, common-area build limits, event safety throttles. None of them said a landlord could deny the deed holder access to a deeded parcel without a visible case record or transfer. I asked, “Can you pull the rule page by source code from the restriction flag?” She enlarged the abbreviated source field. It resolved into a string that looked less like a policy code and more like a manually entered note stitched into the action path. She tried to click through it. No rule page opened. No registry entry opened. No linked case opened. Only the restriction stayed active. The line behind us stopped pretending not to listen. A creator avatar with half-rendered wings muttered, “How do you place a hold with no article?” Somebody else said, “That’s not supposed to happen from counter level.” Dax turned just enough to address the room without fully facing it. “There are internal moderation pathways not exposed to public users.” I said, “Then the courthouse can confirm one exists.” Iris did not confirm it. She kept clicking. On the Public Rule Wall behind her, the same guidance looped again: enforceable restrictions require linked authority. The words sat there in white text while her console failed to produce linked authority for the thing keeping me off my parcel. Leon said, “Try the comparison clean. Same district. Same environment class. Same landlord grouping. If her deed can be overridden by this mystery rule, can mine?” Iris answered, “I can’t issue hypothetical restrictions.” “That’s not what he asked,” I said. “He asked whether the rule you’re honoring would also apply to him.” She looked down at her panel and said, “I can’t verify scope from this station.” That was the first time she said verify. Dax’s posture changed after that. He stopped leaning casually on the counter and stood straighter, like he wanted more distance from the console. “This is becoming unproductive,” he said. “The access hold remains in effect pending review.” “Whose review?” I asked. He did not answer that directly either. “Further escalation can go to moderator channels.” I said, “Good. Put it in a case and attach the rule.” Iris opened a dispute shell. The case stub appeared over the counter glass where all of us could see the required fields: claimant, parcel ID, challenged action, supporting rule or record, action owner. She filled in my name, my parcel ID, and the challenged action. When she got to supporting rule or record, her hand stopped in the air for a second. “Reference the policy you cited,” I said. Dax said, “Use the existing restriction source.” She tried. The field rejected it. A red note appeared under the box: invalid support target. Nobody needed that translated. Leon let out one short breath through his nose and checked his own parcel panel again like he was making sure it still existed. “So you can lock her out first,” he said, “and build the explanation later?” Iris said, “I’m trying to route this correctly.” “Route what?” I asked. “A rule, a record, or his voice?” That one landed because she did not fill the box. Dax said, “The restriction is already active. The case is for review, not creation.” I said, “Then there should be a creation record somewhere behind it.” Iris finally pulled the action metadata instead of the policy page. That screen was uglier and more technical. It showed timestamp, parcel ID, permission layer, and initiator class. She closed one tab fast, then reopened it because I had already seen enough to ask for it. “Who initiated the hold?” I said. “That is for moderator review,” Dax said. I looked at Iris, not him. “Did a moderator initiate it?” She did not say yes. She did not say no either. She read what was in front of her and chose the safest sentence she had. “The current visible metadata does not show a completed moderator case attachment.” There it was. Not the full truth yet, but the shape of it. The denial had authority at the gate and no support at the desk. The policy could not survive a comparison test. The case form would not accept the source being used to keep me out. And when I asked the one question that mattered-who actually owned the denial action on record-Dax stopped talking like a landlord and started talking like a man trying to get the matter out of public view. Iris sent the dispute upward anyway, with the support field marked unresolved and the access restriction still live. The destination tag flashed on the top of the case stub before it left her console: Moderator Review Chamber. That was the moment.