Story code: ST-001037
Part 2: The Rule Started Spreading Everywhere
When I asked Ethan what this supposed restriction would stop me from doing somewhere else in the building, he tried to answer like the rule covered everything and nothing at the same time. We were still at the research lab reception counter with my token on the desk, the scanner idle, and Nora Patel waiting for words she could attach to an actual process. That was the moment the bluff stopped sounding strict and started sounding absurd.
He said, “It would apply wherever the overlap applies.”
Nora did not move her hands from the keyboard. “What overlap?”
“Family overlap around sensitive work zones.”
“That is not a processing term,” she said.
He answered faster. “It doesn’t need to be your processing term to be a real restriction.”
That line got attention from two people standing near the wall monitor because now the problem was visible even to anyone who did not know us. He was making a rule bigger every time someone asked him to make it specific.
I kept my voice even. “Does it stop me from entering the lobby?”
He looked at the lobby around us, realized where he was standing, and shifted. “No.”
“Does it stop me from receiving a temporary badge if my token wasn’t active?”
“That would depend.”
“On what?”
He paused. “The nature of the connection.”
Nora asked, “Connection between whom?”
That is how narrow questions expose a broad bluff. Every answer needs a label. Every label needs a field. Every field needs a place in the system. Ethan kept speaking like he was above the fields while standing at a counter built entirely out of fields.
I asked, “Would this rule stop a delivery courier if they were related to someone upstairs?”
“That is different.”
“How?”
“Because that is a vendor lane.”
“Would it stop a guest lecturer?”
“That is not the same category.”
“Would it stop Lena from walking in here right now if she was meeting me first?”
He looked past me toward the outer doors just before they opened.
Lena Cole came in carrying the flat handled bag she had brought for the handoff, dressed like somebody expecting a normal visit, not a scene. She crossed the tile toward us, slowed when she saw the counter, and stopped close enough to hear the last line.
“I was meeting Maya here,” she said. “That’s what we planned.”
No one raised a voice. That made it sharper. Nora asked Lena only what she could use. “Can you confirm the scheduled time?”
Lena gave it. It matched what Nora already had on her screen. She added that Maya had been expected for the handoff and that she had come prepared to go through the normal lobby process. Then she fell quiet. She did not try to certify policy. She just stood there with the scheduling context Ethan’s rule had not accounted for.
Nora turned back to him. “If this is a real restriction, I need a process source. Policy code, exception note, shift instruction, supervisor direction, something I can log.”
He set one hand on the counter edge. “You can log that I notified you.”
“That is not the same thing,” Nora said.
He changed scope again. “Fine. Then log that the issue is cross-association with internal lab personnel.”
“Whose term is that?”
“It is understood on site.”
“By whom?”
He did not answer that one directly. He stepped sideways and pointed, not at the screen, not at my token, but vaguely toward the secured elevator hall beyond the glass partition. It was the kind of gesture that tries to borrow authority from architecture.
“This is exactly why we separate access decisions from personal assumptions,” Nora said. Her voice never got loud, but the sentence landed flat and official. She clicked into another screen and asked Ethan one more time which policy field he meant.
He gave her a string of words that did not match anything she repeated back. She tried one term. No match. She tried another. No match. Then she picked up the shift contact list and made the move the counter uses when desk-level certainty runs out.
“I’m escalating this,” she said.
That was the first visible sign of support entering the scene, even before anyone else arrived. It mattered because the whole structure of Ethan’s claim depended on not being tested above the lobby voice level.
While she waited for the supervisor line, the silence around the counter tightened. The scanner light stayed green. My token stayed on the desk. Lena stood with both hands on the bag handles, watching Ethan instead of me. He kept repositioning his explanation without naming a source that existed anywhere Nora could check.
Then Nora asked the question that made his earlier certainty look impossible.
“If this restriction is real,” she said, “why was Maya permitted to be approved in the first place without any note, any block, or any exception instruction attached to her access?”
Ethan answered, but he answered in layers instead of facts.
“Because some people assume other people will use judgment. Because not everything is written where it should be. Because certain family-linked entries are supposed to be stopped before they get this far.”
That was not one explanation. It was three replacements for the explanation he did not have.
Nora listened, wrote nothing, and said into the phone, “Daniel, I need supervisor review at reception. Claimed restriction on an active token. No matching field. No verifiable source.”
She set the receiver down and looked at me. “Please stay at the counter.”
Then she looked at Ethan. “Do not interfere with the review when he gets here.”
Ethan started to speak anyway, and that was when Daniel Ruiz stepped into the lobby from the secured side, already reaching for the access log.