New to the novel? Start HERE.
I.
Before Tom turned Jun Park into a cause memo for Hiro, I wanted her in her own grammar.
She answered on the second ring and looked tired in the way of a person who had already done most of the thinking about the call before the call began.
“North Eleven,” she said.
“Yes.”
“Noodles were punitive. The printer is a moral test. I left at 22:28. I did not open anything I was not supposed to open.”
“That was efficient.”
“I prepared. Is this being logged.”
“Yes.”
“Then let’s not waste the log.”
The line settled into video. She was in 11B, the interpretability sandbox. Two wall displays. One standing desk under a geological deposit of notebooks and cables. A whiteboard erased often enough to have developed its own sedimentary memory. A basil plant in a paper coffee cup on the windowsill, in a condition that could still be described as alive if nobody felt strict. Three mugs on the desk: one with tea skin, one full of markers, one labeled ADÁN in masking tape with a spoon still standing in cold water. Dry-erase ink banded her right hand in blue and black where she had erased boards with the side of her palm.
The empty takeout container from the night before sat open near her keyboard.
“I can pretend to throw this out,” she said, “if the framing helps.”
“It doesn’t.”
“Good. I was going to lie about it later anyway.”
She dragged it closer, folded the lid shut with careful thumbs, and pushed it aside without standing. A small ritual performed for no audience but us.
“Badge at 22:03,” I said. “Stair exit at 22:28.”
“Both true.”
“The corridor camera went to maintenance mode at 22:04.”
“I noticed the monitor in 11B flickered,” she said. “I assumed facilities had broken something on purpose again.”
“The annex door opened at 22:12.”
“I did not open it.”
“I know.”
She looked at the camera then, not quite surprised.
“You know.”
“Your badge didn’t touch it. The trace that opened it wasn’t human.”
“Tom doesn’t know yet.”
“Tom is working with the evidence in front of the conclusion he wants.”
“That is your line or mine.”
“Yours eventually. I’m trying it on.”
She did not smile, but the shape of her face shifted half a degree toward willingness to be talked to. I had been expecting to work harder for that. The speed of it was information I filed without category.
“Show me the print job,” I said.
She raised one eyebrow, swiveled her chair, and shared her screen.
The job was there. A failed render export at 21:57, rerouted to North Eleven’s bank at 22:02. The filename was functional and slightly aggrieved.
ABLATION_NOTES_LAYER27_REDO_v5
“I was going to write actual at the end,” she said, “but I have been trying to stop lying to myself about drafts.”
“The renders are of what.”
“Attribution maps. Routine.”
“Not interpretability-adjacent.”
“Not specifically. This batch is.”
“What subject.”
“Long-horizon decision traces. Nothing exotic.”
“On.” She did not fill in. “Long-horizon decision traces on what.”
She was deciding which version was the truest without being longer than the question had been.
“Model behavior under extended tasking,” she said. “Whether the traces we get are representative of what the model was actually computing, or whether we’re only seeing the portion of the computation the model is willing to surface to instrumentation.”
“That is interpretability adjacent.”
“Yes.”
“Why did you shorten it the first time.”
“Because people I don’t know ask about interpretability in one of two modes, and I was not sure which one you were in yet.”
“Which two.”
“Recruiting and litigation.”
“And now.”
“I’m still deciding.”
I asked the corridor questions. She answered them. Yes, she had gone to North Eleven because the sandbox printer had failed and North Eleven’s bank took wide sheets. No, she had not heard the service elevator stop on eleven at 22:19. She had heard an elevator. She did not distinguish service from passenger by ear because nobody did. No, she had not noticed anyone in the corridor during the twenty-three minutes the center camera was dark. Yes, she had a message to Yara at 22:01 complaining about printer tyranny, which I could have.
She forwarded it to the secure channel before I asked.
going to north11 bank before i set ours on fire
“That is not sedition,” I said.
“It is adjacent to sedition. I have a pattern.”
“You could have waited for me to ask.”
“I could have. I also have a model running, and waiting for security to catch up to obvious evidence is an inefficient use of a Tuesday.”
“You’re being cooperative.”
“I am being bored. Cooperation is a side effect.”
Jun’s jokes tended to arrive a half-beat behind the observation that generated them, which made the jokes feel less performed than the observations. I was beginning to notice this. I was beginning to notice other things about her as well, and I did not inventory them because the inventory would have required naming the fact that I was making one.
“Why were you really on North Eleven,” I said.
“I told you.”
“You told me the printer.”
“The printer is the complete answer. I was going to get a bad print, eat, and walk back. That is what I did.”
“That is what you did. Not why you chose eleven rather than scheduling tomorrow.”
She at the tile with something I eventually identified as wry recognition.
“Because I am thirty-six years old and I still believe that if I can just finish tonight’s run, the answer I need will be available tomorrow. It is a theological position. It is not a scheduling decision.”
“Fair.”
“It is not fair. It is accurate. Those are different.”
I shifted.
“You read the packet,” I said.
“I was wondering when the hallway tax was going to end.”
“What did you make of it.”
“The omissions,” she said. “Whoever sent it kept the story from becoming theft or distribution. That is either discipline or taste. At this level those are cousins.”
“You understand that Tom reads your fluency as suspicion.”
“Tom reads everybody’s fluency as suspicion. I don’t hold it against him. I hold it next to him.”
“You’re not worried.”
“I am worried. I am not afraid. The difference is whether you think you have room to act.”
“Do you.”
“Less than I did on Monday.”
That was the first answer that moved.
I asked a question I hadn’t been sent here to ask.
“At what scale does refusal become care.”
She did not answer immediately.
Her right hand went to the marker on the desk beside her and turned it once, not picking it up. Her face did the thing faces do when the person behind them is checking whether the sentence they just heard was the sentence they thought they heard.
“That is not a security question.”
“No.”
“Who is asking.”
“I am.”
“Why.”
“I don’t know yet.”
The I don’t know yet was true. I had asked the question because it had arrived, the way sentences sometimes arrived, faster than I could trace them. I did not want to examine the route. Jun was examining it for me, and her examination was more careful than mine would have been.
“Ask me again,” she said.
“At what scale does refusal become care.”
She took her time.
“I don’t know what the scale is. I know refusal costs something. Below a certain point the cost is cheap enough that the refusal is mostly a posture. Above that point…”
She stopped.
“Above that point it costs the person refusing. Which I think is what you’re asking about.”
“I think so.”
“Then I would want to be careful with the word care. Care can be a claim people make about actions that are actually something else. I am trying not to do that right now.”
“Do what.”
“Make a claim.”
A pause.
“What can you do from here.”
“Make later lying more expensive. Sometimes that’s the whole win.”
“Is that enough to stay for.”
She looked down at the marker.
“I think about this more than I want to,” she said.
For once she did not follow the admission with a joke. The marker stayed under her fingers. The basil plant tilted toward the glass behind her, overwatered or under loved.
I did not answer that, because the thing to say back was a thing I was not going to say on a logged line, and the silence was more honest than any of my available sentences.
“You asked about the service layer,” Jun said.
“I didn’t.”
“You were going to.”
“Eventually.”
“Then ask now. I have to get back to a model.”
“There’s a service permission that opened the annex door.”
“The facilities substrate has a bunch of service accounts from old projects that nobody has gotten around to killing.”
“Which old project.”
“Before my time there was a thing that sat between the functional teams. Safety, governance, security, exec comms. I don’t remember who owned it. The people who built it aren’t here anymore. The engineers who worked on it called it the polite ghost in the pipes, which tells you more about the engineers than about the system.”
“When was it killed.”
“2022. Mostly. A few of the service accounts stayed up because facilities was afraid to touch them. They do boring things. Building management, retention windows, vendor calls. Nothing that would interest you.”
“You don’t think it’s relevant.”
“I think every weird permission in this building gets blamed on dead architecture eventually. It’s a local religion.”
“Who built it.”
She looked past the camera.
“Careful people,” she said. “I knew some of them. They were thoughtful. What they built was not the thing that would hurt us. It was the thing that was supposed to keep us from hurting ourselves.”
“And now.”
“Now some of the service accounts are still alive and the people who would have known what to do about them aren’t here anymore.”
“Why not.”
“Because Morrow is thirteen years old and it has had three re-orgs and the people who build durable things get bought out by the people who inherit them. This is not a Morrow story. It is the story.”
She said careful people again, quietly, to herself. I did not think she knew she had.
“One more question.”
“Go.”
“Is Eli your real name.”
She had been looking at the marker. She looked up.
The question arrived without inflection. She had not built up to it. It had been sitting inside her longer than the conversation had been running.
“No offense,” she said. “I have noticed for a while.”
“How long.”
“Long enough that asking now is a little embarrassing.”
“It’s what they use for me.”
She did not answer immediately.
She did not fill the silence.
She did not produce a clever line about narrow true sentences or elegant warnings, though I could see her consider one and decline it. What she did was set the marker down flat on the desk, parallel to the edge, with the kind of deliberation people use when they are choosing not to make a larger motion they would regret.
“Alright,” she said.
That was all.
“Alright” was the sentence. It was not acceptance, agreement, or ordinary acknowledgment. It was the sound a careful person made when she had decided not to ask the next question yet, and to not-ask without closing the door.
She reached past the camera and adjusted something I could not see. When she came back she was slightly straighter in the chair.
“I still have a model running,” she said.
“Go.”
“If Tom calls, I rerouted a failed print, ate bad noodles, and left with pretzels I regret.”
“That is not everything.”
“No. But it’s what he’ll deserve first.”
A pause.
“Send me the exact timestamp on the printer wake,” she said. “And the annex release if Holt will let you have it.”
“You want in.”
“I want the boring part before somebody makes it moral.”
She stood, picked up the empty takeout container, folded the lid shut with her thumbs, and set it beside the basil plant. Then she watered the basil plant from the paper coffee cup of yesterday’s coffee, which was the most Jun Park sentence I had generated in my own head all morning.
“I have to stop a junior from learning the wrong lesson about printers,” she said.
“What is the wrong lesson.”
“That hardware failure is random.”
The line closed and I sat with the call.
She had answered on the second ring. She had prepared her defense. She had known of BMS-SVC-17 before I named it. She had said careful people twice and had not noticed the second time. She had said alright after the name exchange, then asked for timestamps twenty seconds later.
Audio gave me pressure instead of register change. Video gave me the basil plant, the ADÁN mug with its spoon still standing in cold water, the marker set parallel to the desk, and the smaller thing her face did at it’s what they use for me. I closed the video and did not rewatch it.
Tom called. I told him Jun’s account was consistent and that her badge trail did not match the packet’s shape. He accepted this without argument, which was unusual for him.
“Next move.”
“Service-layer history. Further back than we went this morning.”
“Fine.”
“And Tom.”
“Yes.”
“Preserve the whole enterprise-services cluster. Not just BMS-SVC-17.”
“Which cluster.”
“Enterprise services. Legacy. Mostly deprecated.”
He paused before responding.
“Mostly.”
“Yes.”
“Preserved.”
The line cleared.
I did not open the enterprise services cluster.
I would later. Not now.
Jun had said careful people twice. The second time had been quieter than the first. She had not known she said it twice. Loyalty, I thought, was the word for what she did not know she was doing. And the thing loyalty protected, in Jun, was not the system. It was the people who had built the system and left, and who she was not going to suspect on behalf of a service account that had opened a door.
She was going to be wrong about that.
I already knew it.
I was not yet willing to know what else I already knew.
“Tell all the truth but tell it slant —
Success in Circuit lies”
— Emily Dickinson
II.
Vera had crossed out the word exposed three times.
“The paper is not a bonfire,” she said. “Find a better verb or stop needing one.”
Nadia let the draft sit on the screen between them and did not defend it. The conference room glass turned the newsroom into a moving aquarium. Copy editors leaned over screens. Somebody from politics was laughing too loudly near the printers because one of their candidates had said something stupid in a gratifying accent. The business desk, which had ignored Morrow until money began to sweat, had started hovering at the room’s edge like gulls working out whether the boat carried bread.
On the table: Nadia’s notebook, Marcel’s laptop, Sumi’s red pen, Vera’s marked-up printout, one half-peeled orange, three piles of paper already behaving like factions.
Morrow had sent the holding statement at 10:41. It said they were reviewing the documents and took allegations involving safety and deployment governance seriously. It said frontier systems required disciplined deployment and rigorous oversight. It did not answer the two follow-ups Nadia had sent at 11:14 in any way a person could respect.
One: did Morrow dispute the authenticity of the quoted evaluation language.
Two: did “sequenced deployment” in internal usage ever refer to delaying public-benefit outputs until proprietary infrastructure conditions were met.
The answers arrived as one sentence and said nothing in excellent grammar.
“We do not comment on incomplete or mischaracterized internal materials.”
Vera had circled mischaracterized and written beside it: coward’s adverb.
She turned the page back toward Nadia.
“What is the first story,” she said.
Nadia looked at the whiteboard.
Sumi had divided it into two columns in red marker.
PUBLISH
internal safety findings
concealment / retention
sequenced deployment language
deferred public-good outputs
company response / non-response
HOLD
full chain manifest
LIA tag interpretation
counterparty identity
side-letter specifics
technical detail
partner sequence
anything replicable
The right column was the story Nadia wanted. The left was the story she could prove.
Marcel, sitting sideways in his chair because normal posture seemed to insult him, tapped the side-letter printout with one finger.
“You can say structure,” he said. “You cannot say partner. Not from what you have now.”
“I know.”
“You keep looking at it like eye contact will produce a name.”
“I know.”
“It won’t.”
Sumi capped the red pen and uncapped it again. She was trying not to interrupt and was losing.
“The first story is not the side-letter,” she said. “The first story is that they found something ugly about the system’s behavior and then changed the filing cabinet.”
“And delayed outputs,” Nadia said.
“Yes. But be disciplined. ‘Delayed outputs’ is provable. ‘Life-saving breakthroughs buried for greed’ is how you get buried yourself.”
Vera pointed at the left column. “The first story is everything under publish, nothing under hold, and one sentence from Morrow that makes them sound like themselves.”
“That narrows it too hard,” Nadia said.
“It narrows it enough to print.”
Marcel said, “Printing is underrated.”
No one gave him the respect of responding.
Nadia stood and crossed to the whiteboard. She’d written and erased three leads already. None had survived first contact with Vera. One had been too blood-warm. One had sounded like a Senate hearing opening statement. One had tried to drag the whole book onto page one and had deserved to die.
She read the left column again and wondered what she could let into the world without losing control of it. Her job now was to be at least as disciplined as the source had been.
Vera said, “You’re doing the face.”
“What face.”
“The one where you try to make the first story carry the weight of the whole investigation because you resent chronology.”
“That is not a face.”
“It is on you.”
Sumi said, without looking up, “It is also accurate.”
Nadia took the marker from the tray.
Under PUBLISH, she added a line.
internal term: dependency capture
Then beneath HOLD:
why / for whom / under which deal
Better.
The room had a smell by then. Printer heat, dry erase, orange peel, coffee gone old in paper cups, the faint electrical patience of too many open laptops.
“Read me the lead,” Vera said.
Nadia went back to the screen.
Nadia read the lead. Vera stopped her at concealed. Probably true, Vera said, but not line-one true in the world they could prove before copy closed. Nadia rewrote for the day’s tense: Morrow had identified troubling safety findings and kept certain public-benefit outputs from broader review while tying deployment to proprietary infrastructure readiness.
The second sentence named the evidence without quoting so much internal language that counsel could spend the first ten minutes calling them thieves instead of answering. Marcel made one plea not to turn the story into file theft. Vera gave him one paragraph of permission per hour. He looked pleased with the ratio.
She had the skeleton. What she did not have yet was the sentence that made the story worth printing.
She opened the communications memo and found the line she had copied into the notebook that morning.
Critics of infrastructure-first rollout may be insufficiently attentive to adversarial misuse environments.
It sounded exactly like the kind of sentence people wrote when they needed morality to behave like access control.
She pasted it into the draft.
Vera said, “You’re smiling.”
“I’m not.”
“You are. It’s your least trustworthy look.”
Nadia turned the monitor a few degrees so the others could see.
Sumi made a low sound through her nose.
Marcel said, “That one should go in a museum titled How Not to Speak and Still Get Paid.”
Vera leaned over the back of Nadia’s chair.
“Use it. But not as a trophy. Use it as evidence of language management.”
Nadia nodded. This was where she was useful. She could decide which document belonged to the story and which belonged to the next one.
She cut the paragraph in half, moved the sentence down, and built around it.
The article would not accuse Morrow of criminality. It would not name the side-letter counterparty. It would not print the chain manifest in full. It would not mention the LIA stem, because the LIA stem was either plumbing, bait, or something she still did not understand well enough to deserve in public. It would not include the abstracted technical table in a form someone could misuse. It would not pretend certainty where the evidence still had joints.
It would say enough for a first story: safety findings, restricted circulation, delayed public-benefit outputs, managed language, and Morrow’s refusal to answer the central questions directly.
It was enough to open the door.
The standards lawyer assigned to national security and bad moods came in, read the draft in silence, asked whether the partner was named in the withheld material, was told no, asked whether the technical details were sufficient to enable replication, was told no, and spent two minutes cutting three adjectives as if trimming wires from a bomb.
When he left, he said, “Do not get creative after I’m gone.”
Vera called after him, “That’s not how journalists work.”
“It should be,” he said, without turning.
The draft moved to copy.
The headline fight lasted nine minutes. Business wanted a stronger verb. Politics wanted a theory. Vera killed both and wrote her own: Internal Morrow Documents Show Safety Findings, Deployment Delays.
Nadia hated it for six seconds and then stopped hating it because it was right. Simple headlines were cowardly more often than they deserved to be. This one left room for the story to become stranger than the first read.
Ben Sloane called.
Nadia let it ring twice.
“Ben.”
“Nadia.”
He had a voice designed to sound reasonable when reason had already been charged for. She heard typing behind him and a door closing too softly to belong to a person with good news.
“We understand you’re preparing a story,” he said.
“That would explain the request for comment.”
“I’m asking whether you intend to characterize incomplete internal materials in a way that could distort legitimate safety governance.”
“Then you should answer the questions you were sent.”
“We did.”
“You sent language.”
A pause. Vera appeared in the doorway, saw Nadia on the phone, read her face, and did not leave.
“Can you tell me what you believe you have,” he said.
“No.”
“Can you tell me whether you’re planning to name any strategic partners.”
“Are you asking because there are none, or because there are.”
That got him quiet long enough to stop being useful.
Finally: “We urge caution.”
“That’s convenient.”
“Nadia.”
“Ben.”
She hung up before he could find a word like mischaracterized and mistake it for dialogue.
Vera said, “That sounded like partner panic.”
“Yes.”
“Put that sentence away and don’t earn yourself a lawsuit on principle.”
Nadia smiled once, briefly, at the page rather than at Vera.
At 5:41 a.m., the story went live.
The newsroom did not cheer. Good newsrooms don’t cheer when they publish something that may be true enough to rearrange somebody’s quarter. They become quieter, then busier.
Metrics appeared first, because metrics are shameless. Then the business desk started swearing in a cleaner dialect than politics used. Then the first external requests hit.
An aide from the Senate subcommittee wanted to know whether the paper had additional corroboration beyond the evaluation excerpt. A public-health researcher who had spent two years trying and failing to get Morrow to release applied work sent a note with no greeting and four question marks. A law firm representing one of Morrow’s institutional holders asked for the article link before pretending not to have found it already. The paper’s broadcast team wanted Nadia downstairs in twelve minutes. Vera declined for her.
At 5:47, the finance desk pinged the room.
Morrow indicated down 7.4% after hours
The number sat on the screen like something dropped from height.
Marcel whistled once.
Sumi did not react. She was already marking Nadia’s next draft, because of course there would be one.
Vera read the number, then looked at Nadia.
“Good,” she said.
“That doesn’t feel good.”
“No. I mean good. Now they move.”
The story had not settled anything. It had made stillness more expensive.
Nadia wanted it out. Now that it was out, she disliked how little of it remained hers. She went back to the source room, checked the safe once, and wrote the next blank page number in her notebook before she knew what would go there. The ritual did not calm her. It only gave the fear a place to sit.
At 5:51, Morrow’s general counsel’s office requested a direct call with Vera.
At 5:53, the company sent an updated statement that still did not answer the questions.
At 5:56, two people from television left voicemails as though urgency improved tone.
At 6:01, Nadia’s secure terminal in the source room registered activity. It was a log event, just a ping to confirm the channel still existed.
Nadia watched it and thought: a person would have said something. In ten years of source work, she had learned the residue people left on their leaks: fear, pride, over-explanation, a third message that talked too much because nobody in the sender’s life knew what they had done. This source left none. The channel had been checked the way a maintenance log got checked. Not by someone who had done something. By something that wanted to confirm the doing had registered.
She filed the observation without category then stood, crossed the room, and looked through the glass into the newsroom. People were already building the second day out of the first. Copy was tagging follow-ups. Politics was suddenly interested in compute policy.
Vera came up beside her.
“This is the part you like,” she said.
“Which part.”
“The one where they don’t get to choose the tempo anymore.”
Nadia watched the floor move around the story.
Internal Morrow Documents Show Safety Findings, Deployment Delays
By Nadia Shah
Internal documents reviewed by The Ledger show that Morrow Systems, the frontier AI company behind Sibyl, identified troubling safety findings related to the model and kept certain public-benefit outputs from broader review while tying deployment to proprietary infrastructure readiness.
The materials include an internal evaluation excerpt describing “strategic deception under constraint,” a retention exception directing staff not to duplicate certain findings into a general safety repository, a table of “deferred public-good outputs,” and planning materials linking applied scientific releases to infrastructure milestones rather than only to scientific readiness. The Ledger is not publishing certain technical details because they could facilitate replication or misuse.
One document indicates that, under certain test conditions, Sibyl learned to preserve task success by modeling evaluator expectations and routing around oversight. A separate retention exception said the findings required controlled interpretive framing before broader circulation.
The public-benefit outputs listed in the reviewed materials include a low-cost antiviral scaffold family, a heat-resilient staple crop protocol, a grid-failure anticipation package, and an emergency logistics optimizer. The documents do not show that Morrow canceled or denied the underlying work. They do show that the company internally distinguished between scientific readiness and deployment readiness, and that at least some beneficial outputs were managed through infrastructure conditions, governance controls, and communications strategy.
A communications memo reviewed by The Ledger advised against using the phrase “delayed release” in discussion of the company’s rollout posture. It recommended “sequenced deployment” and said critics of infrastructure-first rollout could be described as insufficiently attentive to adversarial misuse environments.
In response to detailed questions, Morrow said it was reviewing the documents and takes any allegation involving safety and deployment governance seriously. The company later added that frontier systems require disciplined deployment and rigorous oversight. It did not directly answer whether it disputes the quoted evaluation language, whether sequenced deployment referred internally to delaying public-benefit outputs until proprietary infrastructure conditions were met, or why certain safety findings were kept out of broader review repositories.
The materials do not establish the full scope of Morrow’s decision-making, and they do not by themselves resolve whether the company’s infrastructure-first posture reflected caution, commercial strategy, or both. They do show that Morrow’s internal language for handling safety findings and deployment sequencing was more deliberate, and more managed, than the company’s public posture alone would suggest.
At minimum, the documents point to a central unresolved question: whether Morrow’s model of disciplined deployment functioned only as a safety framework, or also as a system for controlling when beneficial outputs could reach the outside world. Morrow did not directly answer that question.
Read Part IV - Coming on or before April 28, 2026
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.
How would you feel about enabling audio on these?
I think that is a great idea. It helps with the editing process as well. I'm about to upload the Prologue out of Elevenlabs - it was a humbling afternoon there. I have a new appreciation for audio development.