Story code: ST-000877
Part 2: The Rule Kept Spreading Until It Stopped Making Sense
By the time Dev Patel reached the front counter, Grant had managed to turn one made-up sounding restriction into a problem for half the floor. He was still saying Nina Alvarez could not go in because of an old headshot, but now he was also asking whether Rhea Monroe’s drop-in guests had current images, whether a remote contributor’s visitor badge should be reissued, and whether anyone had checked archived promo files before letting people into the glass-walled control-room corridor. That was the moment the rule started looking less like policy and more like something that only worked if nobody stopped to compare it across real people.
Dev came from ops with his badge clipped to a dark hoodie and a tablet under one arm. He does not rush, which is useful in a building full of people who think urgency can replace process. He stepped up beside me, looked at Nina’s booking on my monitor, then at the old headshot printout on the counter.
“What rule are we using?” he asked.
Grant answered first, again. “The current likeness restriction.”
Dev did not react to the phrase. “Where is it written?”
Grant gave him the same kind of answer he had given me. “It’s standard. We’ve all worked under it.”
Dev set the tablet down and opened the shared policy channel himself. He searched. Then he opened the internal manual. Search again. Then the booking system. Then the media asset folder attached to Nina’s scheduled recording. Everything he did was visible from my side of the desk.
Nina did not fill the silence. She kept one hand on her folder and the other near the old headshot like she was making sure the object stayed in the center of the conversation.
Rhea stayed too. She had places to be, but she did what producers do when process starts threatening the schedule: she asked practical questions.
“If Nina’s not cleared,” Rhea said, “are we also pulling every guest whose photo in the system is older than today? Because I need to know whether to cancel two intros and a panel.”
Grant said, “Don’t make it theatrical. We’re talking about standards.”
Rhea held up her pad. “I’m talking about a noon recording.”
That is what made the absurdity visible. Nobody was debating image branding in the abstract. We had a lobby full of normal recording-day movement, a booked participant standing at the desk, and a rule broad enough to stop her but somehow flexible enough to leave everyone else untouched until someone asked for examples.
Dev started checking examples.
He pulled the guest list for the morning blocks and compared badge entries to attached assets. One visiting comic had a six-year-old festival photo in the system. One author had no uploaded photo at all, just a publisher logo. A panelist in Rhea’s afternoon booking had a cropped conference still instead of a headshot. All had either arrived before or were scheduled to arrive later with routine access.
Grant leaned on the counter and changed the wording. “This is not about every image. It’s about a flagged conflict.”
Dev looked up. “Flagged by who?”
Grant said, “By the people responsible for protecting the studio.”
Again, not a source.
Dev turned the tablet so I could see the asset trail attached to Nina’s booking. The old headshot had been pulled into the episode prep folder. Same file name. Same thumbnail as the glossy printout on my desk. It had not been rejected, hidden, or quarantined. It was sitting in the system attached to the day’s work like any other usable asset.
Nina tapped the printout lightly. “So this image is trusted enough to package me for the recording, but not trusted enough to let me walk to the room where the recording is happening?”
Nobody answered right away.
A sound engineer pushed past with a coiled cable and asked if Studio A was clear. Rhea answered over her shoulder that it was not clear yet. Even that small exchange made the whole thing sharper. The building was trying to keep moving while the rule kept mutating at the counter.
Dev kept narrowing it. “Mara, did you get any operations note to deny this guest?”
“No.”
“Any security note?”
“No.”
“Any booking hold?”
“No.”
He looked at Grant. “Then what I have is a booked guest, an active room assignment, and a live asset in the folder. I do not have a policy citation.”
Grant crossed his arms and shifted to family authority without saying the word family. “You do not understand the sensitivity here.”
Nina answered that one. “Then explain it in a way that applies to somebody besides me.”
That line hung there because it matched the exact problem. If the rule only existed when Nina stood at the counter, then the counter was not enforcing studio process. It was enforcing a person.
Dev opened one more screen, this one tied to administrative controls instead of bookings. He did not touch anything yet. He just looked at it, then at Grant.
“I need one clean answer,” he said. “Are you instructing front desk to deny a scheduled participant based on a policy you can identify in our system, or are you asking staff to act on your personal directive?”
Grant’s voice stayed polished, but he did not give the rule a location, a document name, or a process owner. He started talking about precedent, exposure, confusion, branding, and standards. The more specific Dev’s questions got, the less specific Grant’s answers became.
Then Dev enlarged the asset trail and found the detail that changed the shape of the whole argument. He turned the tablet just enough for me and Nina to see it, and said, very evenly, “That’s interesting. This old headshot wasn’t uploaded by Nina’s side at all.”
He tapped the line with the account name attached to the file, and every set of eyes at the counter went to Grant.