My Famous Uncle Tried to Get Me Locked Out of the Podcast Studio With a Rule Nobody Could Prove – Part 3

Story code: ST-000877

Part 3: The File Trail Led Back to the Man Quoting the Rule

The line Dev had opened on the tablet did not need any dramatic translation. It was an upload trail, the same kind we use every day when a producer swaps artwork, adds a guest asset, or drags a file into a prep folder. The account name beside Nina Alvarez’s old headshot was Grant Holloway’s studio login. Not a label from Nina’s team. Not a generic archive import. His name.

From my side of the counter, the sequence got simple fast.

Dev zoomed in enough for the file history to be readable without taking the tablet out of his hands. “This asset was attached from Grant’s account,” he said. “Same file currently tied to today’s booking.”

Nina did not move the printout. She just looked from the tablet to Grant. “So the image blocking me is the image you put into the system.”

Grant answered right away, but not with anything that fixed the record in front of us. “That does not change the restriction.”

Rhea gave a short laugh with no humor in it and shifted her legal pad to her other arm. “It changes quite a bit, actually.”

Around us, the studio kept doing what studios do. Someone came through the front door carrying a pastry box with a vendor sticker. A guest in a denim jacket asked where Studio B was. The badge printer made its usual mechanical chirp when I cleared a different check-in from the queue. That ordinary motion mattered because it kept highlighting how narrow this supposed emergency really was.

Dev did not let the conversation widen again. “Let’s make this clean,” he said. “We have no policy citation. We have comparable guests with old or missing images who are not being blocked. We have an active booking with no hold. And we have the disputed asset attached by your account.”

Grant straightened and switched from broad phrases to overexplaining. That was the first point where his polished delivery started slipping against the details.

“Because I knew there could be confusion,” he said. “The image was provisional. It was there for internal reference, not physical clearance. There are reputational issues, sponsor issues, floor sensitivity issues. This should never have reached the desk this way.”

Dev asked, “Where is provisional marked?”

Grant said, “It’s understood.”

“Where is floor sensitivity marked?”

“Not every standard lives in a public channel.”

“Who owns the standard?”

Grant looked past him toward the corridor and then back at the counter. “People who have to manage consequences when branding conflicts spill into production.”

Again, no system field. No owner. No note. Just a sentence trying to stand where process should have been.

Nina stayed on the same point she had been on since the beginning, which is probably why the bluff kept losing air. “If this was real, you could apply it to someone besides me without changing the words every thirty seconds.”

That was when Rhea made the comparison impossible to ignore. She stepped closer, opened her tote, and pulled out a one-sheet for her noon panel. Three guest names, three thumbnail images. One was clearly an old event photo.

She put the page beside Nina’s headshot. “Here’s my lineup. If we are doing this now, tell me which one of these people loses access. Or tell me why none of them do.”

I looked at the panel sheet, then at the guest queue on my monitor. She was not exaggerating. If I enforced Grant’s claimed rule the way he had described it at first, I would have had to halt half the day and start auditing everybody’s likeness history at the front desk. There was no process built for that because there was no rule built for that.

Dev asked me, “Mara, has front desk ever been trained to deny entry based on currentness of a headshot alone?”

“No,” I said.

“Ever had a badge field for it?”

“No.”

He looked at Rhea. “Ever got an operations warning tied to thumbnail age before room access?”

“Never,” she said.

Then he turned back to Grant. “So the only place this restriction exists is in your instruction to staff this morning.”

Grant put his hand flat on the counter again, the same way he had at the start, but now it looked less like control and more like he needed the surface. “I am telling you the image creates a problem.”

Dev nodded once. “That is different from telling us there is a studio policy.”

Nobody rushed to fill the silence after that because the distinction had finally become visible to everyone standing there. Nina’s old headshot had gone from being the excuse to being the proof object. It was in the booking, in the prep folder, in her hand, and under Grant’s account history.

Dev picked up the tablet and opened the administrative controls screen fully this time. “Then we have a second issue,” he said. “If your account was used to inject an unsupported restriction into live operations, I need to secure the account path that touched today’s booking.”

Grant’s head turned sharply. “You are not locking me out of my own studio tools over a misunderstanding.”

Dev’s voice stayed level. “I am not calling it a misunderstanding. I am calling it an access-control event.”

That was the first irreversible phrase anyone used all morning, and it landed hard enough that even the people pretending not to listen in the waiting area looked over.


Leave a Comment