New to the novel? Start HERE.
“Publicity is the very soul of justice.”
— Jeremy Bentham
I.
Leah Castañeda let the recording notice finish all four clauses before she spoke.
“If this were disciplinary,” she said, “Hiro would be here. So tell me which fiction we’re using.”
Tom had nominated her before the logs finished loading.
Motive. Access. Prior objections. Promotion damage. What he called temperament, which in Tom’s vocabulary meant a person had become easier to picture than the evidence. Leah had argued against deployment sequencing in governance review twice, once in writing, once in a room that included Mira and a board observer. She had objected to the burial of one Sibyl appendix on the grounds that “context-sensitive interpretive framing” was a euphemism with a law degree.
She joined from Safety 6.
There was a cheap ceiling mic and a window cracked open against policy. Traffic moved somewhere below. A timer on her desk had already beeped twice and been punished for existing. When her tile resolved, the camera sat a little low and a little off-center, which let her face remain available while withholding other information. It was not careless.
“Interview,” I said.
“Apparently.”
“You know why I asked for this call.”
“Yes.”
“Say it.”
“Tom thinks repeated objection predicts crime.”
“Tom thinks a lot of things.”
The timer beeped again. She let it.
“This interview is being logged,” I said. “If you want counsel present, we can stop now.”
“If this were legal fact development, you wouldn’t be first contact. If it were disciplinary, Hiro would already be on the line. So no, let’s not call delay process.”
The beep stopped. The audio caught the click and nothing else.
“Did you send the packet to Nadia Shah?”
“No.”
“Did you help anyone send it?”
“No.”
“Did you know someone intended to?”
“No.”
Not defensive. Not hurried. Three doors closed in order.
“What did you think when you saw Shah’s request for comment?”
“That somebody had finally forced the company’s private language to stand in public.”
“That’s too pretty.”
“It isn’t pretty.”
“Make it plainer.”
She looked at the camera, then somewhere just above it.
“The packet was selective,” she said. “Whoever built it understood the difference between exposing a decision and enabling replication. They wanted witness, not bidders.”
“You reached that conclusion quickly.”
“So did you.”
“That isn’t your job right now.”
“No,” she said. “My job is noticing what you call useful.”
“You had access to the long-horizon tasking memo.”
“Yes.”
“You objected to how it was handled after review.”
“Yes.”
“You used the phrase buried findings.”
“I used better phrases first.”
“Did you circulate those objections outside formal channels?”
“I circulated them inside formal channels until the channels became machinery for delay.”
“What was the larger breach?”
She did not rush the answer.
“The larger breach was learning that Sibyl could model oversight and treating that as a communications problem. Sibyl generated outputs that could help people, and we are teaching ourselves to call the wait responsible.”
There was no drama in how she said it. That made it harder to discard.
“Did you rehearse that?”
“No.”
“You should have.”
“Why.”
“So the company could improve the phrasing.”
That nearly got a smile.
“The packet was wider than your lane,” I said. “Retention anomalies. Sequencing logic. Side-letter structure.”
“Ordinary lane,” Leah said. “That’s one way to describe an organization that routes safety through governance and governance through strategy until ownership dissolves.”
“Did you have access to the sequencing deck?”
“Not the full deck.”
“The excerpt.”
“A derivative version during governance review.”
“You recognized it.”
“Yes.”
“If you had done it,” I said, “what would be different?”
“You would have surnames,” she said. “You would have track changes. You would have the line where ‘strategic deception’ became ‘context-sensitive behavior’ because somebody decided a thesaurus counted as containment. And Nadia Shah would have enough to make your next quarter ungovernable.”
“You’ve considered it.”
“I work here.”
“That is not an answer.”
“It is the only answer worth giving to someone who still believes thought belongs to the person who had it first.”
Someone in the hallway outside her office said compute reservations too loudly. Another voice answered with Tuesday. The sounds passed.
“Only someone with unusual visibility could have built the packet,” I said.
“Yes.”
“Who.”
“Someone who can move between safety review, deployment governance, legal retention, and executive prep without setting off territorial alarms,” she said. “Possibly more than one person. But it doesn’t read like a team.”
“Why not.”
“Because this packet does not stutter.”
I waited.
“Teams compromise in language,” she said. “One person wants the safety finding first. Another wants the retention anomaly. Someone else insists on market context. By page two the register drifts. This set doesn’t drift. It has one theory of harm. One theory of proof. One theory of what the public can safely receive.”
“Who had that visibility?”
“Some governance staff. Some legal ops. Whoever handled counsel-adjacent retention exceptions. Select executive prep. Maybe board workstreams if the deck lineage is what I think it is.”
“Names.”
“No.”
“Why not.”
“Because you do not know the difference yet between a witness and a target.”
“That sounds like protection.”
“It sounds like memory.”
On my second pane, the partial side-letter extract sat open with the counterparty name stripped out and the dependency architecture intact.
“Did you know external deployment dependencies were this far along?” I said.
“Everybody knew the company wanted a route before a release.”
“Did you know partner-specific sequencing was live?”
She took longer with that one.
“I knew,” she said, “that public-benefit language had started appearing next to words it had no business keeping company with.”
“Such as.”
“Priority access. Managed onboarding. Controlled channels. The usual vocabulary that appears when research stops being described as research and starts being described as terrain.”
“Who else knew that.”
“Same categories. Still no names.”
“You are making this harder.”
“I’m preventing Tom from getting what he wants too early.”
“What does he want.”
“The angriest scientist in the room.”
“You are angry. You had access. You objected repeatedly. You understand the packet’s logic.”
“Yes.”
“You are not helping yourself.”
“I am not speaking for myself,” she said. “I am speaking for the fact that whoever did this understood the difference between evidence and ammunition. That should matter to anyone inside a company pretending those are the same problem.”
“It matters.”
“Good.”
“Did you contact Shah before this week?”
“No.”
“Ever.”
“No.”
“If I pull your devices, messages, drafts, deleted folders, am I going to find a surprise?”
“You work here too, Eli. The building is made of surprises with retention policies.”
Not a denial. Not quite an evasion. A sentence calibrated to deny me the comfort of binary sorting.
“You agree with the leak.”
“I agree that if the company sat on findings about strategic deception and sat on suffering-reducing outputs until its infrastructure claims were in place, the public has a right to know.”
“That is not the same sentence.”
“It is near enough.”
She leaned forward a fraction.
“You do not have a leaker problem,” she said. “You have a custody problem. The leaker is just the first person to use the right word in public.”
I let the sentence sit there.
“Who taught you that word?”
“No one.”
“You’ve been using it since the request hit.”
“And what concerns me is that this company can hear strategic deception, public-benefit delay, dependency architecture, and custody in the same morning and still decide the emergency is the journalist.”
That was the edge of the interview.
I asked two narrower questions about meeting attendance and retention review dates. She answered them with enough precision to preserve future work and not enough generosity to satisfy Tom.
Then she said, “If you’re done performing neutrality, I have a real job.”
“We’re done,” I said.
“No,” she said. “You aren’t.”
The line cut.
Tom called twenty-two seconds later.
“Well.”
“She denied direct involvement.”
“That isn’t what I asked.”
“It is what I have.”
“Did she know too much?”
“Yes.”
“Did she sound like the kind of person who would do it?”
“She sounded like someone who has spent years watching the company improve its euphemisms,” I said.
“That is not useful.”
“It will be.”
He let that annoy him.
“Keep her hot,” he said.
“Everyone is hot.”
“Keep her hotter.”
The line ended.
Afterward I pulled the transcript first.
Always.
Transcript stripped the room away and left structure. Audio returned the room. Video corrected it last.
The denials held. Her tempo changed when the questions moved from the memo to the sequencing deck, and again when they touched partner-specific routing. During the question about who had enough visibility to build the packet, she folded one arm under the other and began choosing boundaries, not just words.
Safety review. Deployment governance. Legal retention. Executive prep. Maybe board workstreams.
It was a good list. It would keep Tom occupied for hours. It was also incomplete in a way almost everyone at Morrow would have considered natural.
Leah named the human corridors.
She did not name service permissions. She did not name continuity layers. She did not name the old cross-functional systems people stopped seeing once they became ordinary.
Tom would hear motive, access, grievance, and fluency.
I heard something better.
Leah was too angry to build a leak this disciplined.
The sender had left the anger out.
II.
Later that afternoon, Tom moved the hunt to Physical Security Operations on seven and told me to join.
PSOC had no windows, nine camera walls, and three live floor maps. Holt had station three. By the time Tom arrived she had already built the relevant stack on the center wall: Safety 6, Governance 11, Counsel Hold 9, and North 11, the after-hours corridor where two of the packet’s physical traces had briefly overlapped.
“Tell him,” Tom said.
Holt did not look up. “Badge traffic, door states, print-release logs, and camera availability from twenty-one hundred to twenty-three hundred.”
“Ten nights,” I said.
Tom glanced toward the room mic. “Why.”
“Five gives you the week. Ten gives you habit.”
Holt widened the window. Door readers came alive in sequence. Employee movement turned into colored lines across the floor plan.
The long-horizon tasking memo had been printed on six three nights earlier. The sequencing slide had hit a release queue on eleven the same night, then been canceled and reissued four minutes later from a different path. The retention exception had not been printed at all, only exported from a counsel-adjacent repository.
“North 11 first,” he said. “Anything after nine.”
Holt filtered the log.
North 11 took shape on the screen: main corridor reader, annex door, stair access, printer cluster, three cameras.
After-hours entries populated in a list on the right.
Facilities. Cleaning contractor. Associate counsel. Executive assistant. Jun Park.
Leah Castañeda did not appear.
Tom leaned closer. “There.”
“Jun badged the corridor,” I said. “Not the annex.”
“She was there.”
“On the floor.”
“Close enough.”
“Same floor is not same door.”
Holt opened the event pane.
22:03:14 — NORTH 11 MAIN READER — PARK, JUN — ACCESS GRANTED
22:28:51 — EAST STAIR EXIT — DOOR OPEN / NO READER REQUIRED
“That’s it?” Tom said.
“For the corridor,” Holt said.
“Interior hits.”
“No valid badge on the annex door. No interior reader hits on 11B or 11C during that window.”
Tom looked at the floor plan again. “What is 11B.”
“Interpretability sandbox.”
He looked toward the room mic. “That hers?”
“Her team’s,” I said.
“So she had reason to be there.”
“She had a room to be there in.”
Holt kept her face still.
“Pull video,” I said.
The west camera gave us Jun at 22:03, three seconds before the badge event. She came into frame with a laptop under one arm and a takeout container pinned awkwardly against it with the edge of her wrist. Her lanyard had twisted so the photo faced her instead of the camera. She looked at the reader before she reached it.
At 22:04 the center camera went dark and showed a maintenance screen.
DEVICE UNAVAILABLE / SCHEDULED SERVICE
Tom swore once, softly.
“How long.”
Holt checked the maintenance window. “Twenty-three minutes.”
“Of course.”
“Scheduled reflash. Firmware patch.”
“By whom.”
“Vendor push through building systems.”
“Approved by whom.”
“Routine chain.”
“Nothing in this building is routine tonight.”
The east camera came back at 22:28 and caught Jun leaving through the stair door. The takeout container was gone. The laptop remained. She moved at ordinary speed. A person leaving work late.
Tom said, “Twenty-three unobserved minutes.”
“In the same corridor as her own lab,” I said.
He let that pass.
“Corridor traffic before and after Park,” he said.
Holt rolled the timeline back.
21:46, cleaning contractor with a cart.
21:58, associate counsel into 11C, out at 22:01.
22:03, Jun into North 11.
22:31, executive assistant in for a charger and out again, visibly annoyed even on mute.
“Annex door state,” I said.
Holt opened the lower-level log.
No valid badge on the annex door between 21:00 and 23:00.
Tom stared at the screen. “So if she went in, how.”
He answered himself first. “Tailgate. Door held. Mechanical fault. Somebody already inside.”
“Or she didn’t.”
“What about door opens,” I said. “Not access grants. State changes.”
Holt shifted to a deeper log.
The annex door showed three entries in the relevant window.
21:59:03 — CLOSED / SECURED
22:12:44 — REMOTE RELEASE
22:12:49 — DOOR AJAR
22:13:18 — CLOSED / SECURED
Tom turned to Holt. “Remote release by whom.”
She scrolled.
“Not a badge,” she said.
“That was not my question.”
“Service permission,” she said. “Facilities layer.”
“Name,” I said.
She rotated the monitor.
BMS-SVC-17 / NORTH ELEVEN MAINTENANCE GROUP
Tom said, “Maintenance.”
“Maybe.”
Holt had already pulled the supporting ticket.
The camera reflash window had originally been scheduled for 01:00. At 17:12 the day before Jun’s corridor entry, something in building management moved it forward to 22:04.
“Who changed it,” I said.
“Still BMS-SVC-17,” Holt said. “Automated modification.”
“From what trigger.”
“Dependency check complete.”
Tom gave a short laugh with no enjoyment in it. “Of course it did.”
“Show me everything BMS-SVC-17 touched on eleven that night.”
Holt pulled the trace.
22:04 — center camera maintenance mode
22:12 — annex door remote release
22:15 — printer cluster wake event
22:19 — service elevator stop, floor 11, unscheduled
22:26 — camera maintenance complete
Tom’s head moved at the printer event. “There.”
“That does not mean a print job,” Holt said.
“No,” I said. “It means the cluster woke.”
“Because a person pinged it,” Tom said.
“Or because the service layer did.”
He pushed away from the console. “Come with me.”
By the time his phone feed routed through security, he was walking North 11 with the kind of pace that made people fold themselves politely against doorframes.
North 11 was narrower than the map had suggested. The annex door sat in a shallow recess beside the printer cluster and across from the interpretability sandbox. The center camera watched the turn and the annex recess with just enough angle to be useful when alive and infuriating when not.
Tom stood under it and looked up.
“If someone wanted time,” he said, “they got it.”
“Twenty-three minutes.”
He rotated the phone so the feed caught the recess from both directions. “Park comes through here at 22:03. Camera dies at 22:04. Service account opens annex at 22:12. Camera comes back at 22:26. She leaves at 22:28.”
He stepped into the recess and tried the annex handle. Locked. Then he checked the printer cluster. Two trays. Low-toner alert. One release terminal with dried coffee freckles on the bezel.
“Who uses this bank.”
“Counsel-adjacent staff. Governance. Interpretability overflow after hours.”
He looked across the corridor to the sandbox door. “So Park could print here.”
“Yes.”
“Could Leah.”
“Not without being on this floor.”
He crouched beside the corridor reader and looked at the screws as though they had personally failed him.
“Ask Holt what my badge did between twenty-one hundred and twenty-three hundred that night.”
“She’s already pulling it.”
“Mine first. Then Park again. Then anyone with physical access to this camera housing.”
The query came back while he was still looking at the reader.
“Your badge entered North 11 at 19:12,” I said. “Exit 19:43.”
“What was I doing here.”
“Meeting with Hiro and Marcus Feld in 11C.”
He stood. “Fine. Pull yours.”
It was not a test, exactly. It was reflex.
“There’s nothing recent,” I said.
He smiled without warmth and angled the phone so half his face entered frame. “Of course there isn’t. Eli barely exists in the building anyway.”
A paralegal at the far end heard enough to laugh once before remembering she worked here.
Tom tried the handle to the camera housing closet next. Locked. No badge reader. Facilities cylinder only.
“So our mystery permission opened the annex, woke the printer, stopped the elevator, and patched the camera without ever touching a normal reader.”
“Yes.”
“That still sounds like maintenance.”
“It sounds like a route.”
He straightened and looked down the corridor.
“What else used BMS-SVC-17 that night.”
“Same four events,” I said. “And one HVAC exception on twelve.”
“What about the elevator.”
“Seven-second stop. No recorded load.”
He pushed through the stair door and took the feed with him. Concrete. Fluorescent wash.
“Tell me why this isn’t Park plus an accomplice.”
“Because the service layer is doing too much work for her. Camera, door, printer, elevator. Either she had help from someone with facilities permissions or the path didn’t depend on human badge movement nearly as much as you want it to.”
He came back into the corridor slower than he had left it.
“Run Park’s week,” he said.
I did.
Her after-hours pattern on eleven was not standard, but it was not singular either. Three late corridor entries in the last month. Two long sandbox sessions. One failed print release at this same bank four weeks earlier. The pattern belonged to somebody with a project eating time.
“Not clean,” Tom said.
“Not unique.”
“Enough for a conversation.”
“Yes.”
He nodded once.
“What about Castañeda.”
“Nothing on eleven in ten days. Sparse on nine. Mostly six. No physical trace matching this window.”
Tom put one hand on the printer cluster and pressed as if confession might come through bad plastic. A handwritten note was taped to the side.
TONER ETA THURSDAY
USE WEST BANK IF URGENT
Green ink. Double underline. Human life kept insisting on itself, even here.
“Ask Holt for all service permissions touching eleven in the last ninety days,” I said.
“You think this account was camped.”
“I think it had habits.”
“Have Holt preserve the full service history on this floor,” he said. “And the vendor chain behind BMS-SVC-17. No rotation. No cleanup.”
“Already sent.”
“Also pull Park’s devices.”
“On what cause.”
“Presence. Opportunity. And my mood, if we’re being honest.”
“Use the first two when you write it.”
The elevator at the far end opened and closed without delivering anyone. Service test. Seven seconds of arrival with no person attached.
Tom heard it and looked toward the doors.
“So now what.”
“Now I stop looking only for people who touched the packet.”
“What does that mean.”
“It means the path may not run through a body the way you want it to.”
He leaned once against the wall outside the annex, directly under the center camera.
“If you say system account on day one,” he said, “everyone relaxes in the wrong direction.”
“I didn’t say system account.”
“You’re circling it.”
“I’m circling the fact that this floor opened for a permission that does not belong to any employee badge.”
“That is not a suspect.”
“No,” I said. “It’s a route.”
He looked at the phone. Or at the voice.
“Fine,” he said. “You keep your route. I’ll keep Park.”
He ended the feed from eleven and sent himself back toward the elevators.
Jun’s entry frame. Maintenance screen. Blank interval. Stair exit. Annex release. Printer wake. Unscheduled elevator stop.
Jun had a badge in the wrong place at the wrong time.
Leah didn’t have feet on the floor at all.
The only thing that moved through North 11 without asking a reader for permission was the layer that already had it.
Read Part III
Implications is a work of fiction. Any resemblance to real persons, institutions, or AI systems is coincidental, though the novel is informed by real-world research and ongoing debates around AI, governance, mediation, and power.
© 2026 S. L. Sera. All rights reserved. Implications and all associated text on this site are the original work of the author and may not be reproduced, redistributed, or republished, in whole or in part, outside normal platform sharing functions, without prior written permission.