On the thirtieth day, I make a plan.

Not impulsively. Not reactively. I've been building toward it for a week — since *so fix it* and *yes* and the question I finally stopped avoiding: *if not the right to be jealous, what right do I have.* The answer to that question, when I finally let myself look at it, is not romantic. It's not about what I feel or what I want or what I've been circling for thirty days of amber light and supply records and a window facing east. The answer is simpler and harder than any of that.

The right I have is the right of anyone who has caused harm and has the capacity to address it.

That's it. That's the whole thing. Not love, not obligation, not craft-decision guilt. Just: I made choices that produced consequences for real people, and I am here, and I have information that might change those consequences, and choosing not to use it would be its own kind of decision.

So: a plan.

I sit at the narrow table in my room the night before with the candle and a piece of paper and I think through it carefully. Not the whole arc — I've learned enough by now to know that large interventions produce large corrections, and The Ink is faster and more thorough than I want to test. Something small. Specific. One decision point in the chain of events that leads to chapter 30.

I know the chain. I built it. In chapter 25 of the draft I haven't published, Kael makes a decision to go to a specific location — an outpost on the northern edge of his territory — that seems reasonable at the time and turns out to be the first link in the sequence that ends in chapter 30. He goes there because he receives a request and he doesn't have a reason not to.

If he had a reason. A small one. A piece of information that made the northern outpost a lower priority than something else that day — something that would redirect him without changing who he is or how he thinks or anything that would draw The Ink's attention.

I think I know what that piece of information is. I know the archive. I know what's in it. And I know what Kael doesn't know yet that would make him reconsider.

I write the plan on the paper.

Then I sit back and look at it.

It's a small piece of paper with a small plan. Four sentences. A piece of information, a timing, an expected outcome. It looks almost nothing like the hours of deliberation that produced it. Most plans are like that — the thinking is invisible, and what remains is just the decision.

I think about what Aldren said: *person's questions have more traction.* Not author's questions. Not *what does the story need* or *what serves the arc.* What do I want. And what I want, when I take it apart and look at it honestly, is not to change a narrative. It's to give someone I care about a chance at more time.

That's a person's want. Not an author's.

I fold the paper. I put it in my pocket.

In the morning I go to the archive early.

---

Kael arrives at his usual time and I have the paper folded in my pocket and the morning's records in front of me and nothing in my expression that I'm aware of, which may or may not mean nothing is showing.

He comes in, hangs his coat, goes to his table, opens his file. The morning proceeds.

I work through the first stack of corrections with the mechanical efficiency of someone who has been doing this long enough that the hands know what to do without supervision. Part of my attention is on the records. Part of it is on the timing — when to introduce the information, how to do it naturally, what the right moment looks like.

I've been watching Kael work for thirty days. I know his rhythms.

Around mid-morning, he reaches a decision point in whatever he's reviewing — I can tell from the quality of his pause, the particular stillness that means he's weighing options rather than processing information. He picks up his pen. Sets it down. Looks at the document.

This is the moment.

"The northern outpost report from last month," I say, not looking up from my own work. "The one about the supply access through the eastern ridge. There's a note at the back about the structural assessment — the eastern approach has been rated as unstable since the autumn rains. It would affect any significant movement through that route for at least the next few weeks."

Kael looks up.

"Which file?" he says.

"Third alcove, second shelf. The autumn maintenance survey — it was cross-filed with the supply reports, which is why it didn't come up in the standard routing."

He gets up. Goes to the third alcove. Comes back with the file I described. Reads the relevant section. Makes a note. Sets the file aside.

"That changes the northern outpost timeline," he says, mostly to himself, in the way he processes information out loud when it's recalibrating something.

"I thought it might," I say.

He looks at me briefly — the reading-look, quick — and I'm looking at my own records, and whatever he reads in my profile he apparently files under *useful observation from someone with good recall,* because he goes back to his work without further comment.

I go back to mine.

I breathe.

This is what it feels like, then. Not the author's certainty of *I wrote this therefore it happened.* The person's uncertainty of *I did something and watched it land and now I wait to see if it holds.* The difference is enormous. The author's certainty is clean. This is not clean. This is the ordinary anxiety of anyone who has made a choice and can't take it back and doesn't know yet if it was right.

It worked. Or it seems to have worked. He's updated his thinking about the northern outpost timeline, which means the decision he would have made — the one that starts the chain — is now competing with a different set of priorities. He didn't make the decision under pressure or because I told him to. He made it because the information was relevant and he processed it the way he processes everything: efficiently, without drama, and entirely of his own volition.

Law Five. Natural change from genuine human action. The Ink can't stop this.

I work through the afternoon with something that I identify, cautiously, as hope.

---

The afternoon is normal. Kael reviews his files. I work through the eastern supply corrections. Theo comes and goes twice with document runs. Aldren is in his alcove.

I've learned to track the ambient sounds of the archive the way I track Kael's footsteps — not consciously, but the way you learn the sounds of any space you inhabit long enough, where the absence of an expected sound becomes its own kind of signal. At some point in the late afternoon I notice that I can no longer hear the faint turning of pages from Aldren's alcove.

Not unusual. He moves around. He steps out sometimes for reasons he never explains.

Except I didn't hear the door.

I look up from my records.

Kael is at his table, reading. Theo left about twenty minutes ago and hasn't returned. The archive has the particular quality of a space with two people in it, when it should have three.

I look at the alcove. Empty.

I go back to my records.

Five minutes later, Kael stands up to get a file from the shelf near the door — the intake shelf, where Theo deposits new documents when he brings them in. He reaches the shelf. Looks at it. Looks again.

"The northern outpost report," he says. "The one Theo brought in this morning. Did you move it?"

I look up. "No. I saw him put it on the intake shelf when he came in."

Kael looks at the shelf again. It's not there.

We both look at the shelf as if looking harder will produce the document. It doesn't.

"Theo," Kael says, and goes to the door to call him.

Theo is in the corridor — he'd been about to come back in, apparently, with a small stack of documents from the outer office. He confirms: yes, he brought the northern outpost report in this morning. Yes, he put it on the intake shelf. He remembers doing it clearly.

We all look at the empty shelf.

Theo goes in to check the shelves, methodically, the way you search when something should be somewhere and isn't. I watch him.

And I notice.

It's subtle — the kind of thing you'd miss if you weren't watching closely, if you weren't already alert, if you weren't already aware that something has gone wrong. But I'm watching closely and I'm alert and I am very much already aware.

Theo is searching the shelves, and somewhere in the middle of the search, he stops. Looks around. The specific look of someone who has momentarily lost track of what they were doing and is trying to reconstruct the purpose from the environment. His eyes move from shelf to shelf and back to the room's entrance, and there's a quality to the movement that is wrong — not the focused reconstruction of *where did I put that* but the confused reconstruction of *why am I in this room.*

He stands there for a moment.

Then he says, slowly: "I'm sorry — what were we looking for?"

Kael and I look at each other.

---

Kael sends Theo on a task — something unrelated, something that gets him out of the archive without making his confusion conspicuous. Theo goes without question, apparently satisfied with the explanation, apparently unaware that anything has happened.

The archive is quiet.

Kael turns to me.

He doesn't ask immediately. He stands in the space between the intake shelf and the center table and he looks at me with the full-presence look — the one that isn't reading, isn't assessing, just looking — and he waits.

I've known since the moment I noticed Theo's confusion. I've known what it means. I've been running through the options for the past three minutes while Kael managed Theo, and the options are: say something or don't say something, and I know which one I'm going to choose because I chose it before — in the archive, with the scar story, with *before or after,* with every honest answer I've given in thirty days.

"I tried to change something," I say.

Kael doesn't move.

"This morning. The information I gave you about the northern outpost — the structural assessment, the eastern approach. I found that information specifically to redirect your thinking about the timeline." I look at my hands on the table. "I thought it was small enough. Natural enough. I wasn't using authorial force, I was just — giving you real information that would affect a real decision. Law Five."

Silence.

"And I think this —" I gesture toward the empty shelf, toward the space where Theo was standing confused. "I think this is the cost."

Kael is quiet for a long moment. I don't look up. I'm aware of the archive around us — the amber light, the shelves, the document that has been erased from existence to balance a change I made.

A sound from the back alcove.

Aldren comes out. He doesn't explain where he's been. He looks at the intake shelf, at me, at Kael. He crosses to the alcove where Theo was searching and looks at the shelves in the specific way of someone confirming something they already knew.

"The Ink corrected," he says. Not to either of us specifically. To the room. "It always corrects." He turns. "The boy will be fine by morning. He'll think he had a headache — a bad afternoon, not enough sleep. He won't remember anything unusual."

"The report?" Kael says.

"Gone. It served its purpose as a corrective and doesn't exist anymore." Aldren looks at me. "Now you know what the cost looks like when it's a small intervention."

He goes back to his alcove.

I sit with what he said. *When it's a small intervention.* When it's small, the cost is a few hours of a young man's memory and a document that apparently never quite existed. When it isn't small —

I don't finish that thought.

I think instead about Theo. About the specific quality of his confusion — not frightened, not in pain, just briefly untethered from the purpose that had been in his head. He'll wake up tomorrow with a headache. He'll think it was a bad afternoon, not enough sleep. He won't know.

That's supposed to be the reassurance. He won't know. The cost is invisible to the person who pays it.

I'm not sure that makes it better. I'm not sure it makes it worse. I'm sitting with the fact of it, the way I've been sitting with a lot of facts lately: directly, without the editorial management of someone who can choose what gets written next.

Kael has moved to his table. He's standing rather than sitting, which is unusual — he's the kind of person who sits down when he's in the archive, who makes himself comfortable in spaces he uses regularly. Standing means he's not settled. He's still processing.

I wait.

"Was it worth it," he says finally.

Not *should you have done it.* Not *why didn't you tell me.* Just the practical question: did the value of the outcome justify the cost.

"I think so," I say. "What I tried to change — I think it worked. The decision you updated this morning, about the northern outpost. I think that's the change I needed." I pause. "But I don't know yet. I won't know for certain until —" I stop. Until chapter 25. "Until more time has passed."

Kael looks at me for a long moment.

Then he pulls out the chair at his table and sits down. The return to sitting — to the ordinary posture of this room, this work — has the quality of a decision being made and filed.

"Tell me what you were trying to change," he says. "Not the mechanism. What you were trying to prevent."

I look at him. He's sitting at his table with his hands flat on the surface, not holding anything, the posture of someone who has cleared the decks for a conversation that requires full attention.

This is the thing I haven't done before. I've told him I know things. I've confirmed that I know his ending. I've said *yes* and *including yours* and all the other careful partial truths that get close without being the whole thing. I haven't sat across from him and walked through the actual sequence — here is what happens, here is when, here is the specific shape of what I've been trying to prevent.

I tell him. Not chapter numbers, not the full architecture of the draft — but the thread: the northern outpost, the decision that starts the chain, the sequence that leads to the place where his story was supposed to end. I tell him what the chain looks like and where I tried to cut it.

He listens without interrupting.

When I'm done he's quiet for a long time. Long enough that the amber light in the archive shifts slightly, the way it does as the afternoon gets older and the angle changes.

"Next time," he says, "tell me first."

I look at him.

"If you're going to try to change something in the chain," he says, "tell me what you're doing. Not for permission. I'm not asking for permission to be involved in my own story." The word *story* comes out with a specific weight — not bitterness, not irony, just the weight of someone using a word accurately and knowing exactly what they're doing. "But I live here. I know things about how this place works that aren't in any record. I might be able to help."

I look at him across the archive. The amber light. The empty intake shelf. The alcove where Aldren has returned to his reading as if nothing happened.

"Yes," I say.

He nods. Goes back to his file.

I go back to my records.

From somewhere in the warm archive air, arriving in the particular way of a signal that's been listening and has something to say:

*— next time tell me first —*

*— he said NEXT TIME —*

*— they're doing this together now aren't they —*

I look at the intake shelf where the report used to be. I think about Theo, who will wake up tomorrow with a headache he can't explain. I think about the northern outpost and whether the thread I cut will hold, whether the chain will find another link, whether *small* is ever actually small when The Ink is watching.

And I think about *next time tell me first* — the assumption of a next time built into it, the assumption of telling, of a *me* worth telling. The assumption that this is something we're doing together, that the pronoun has shifted from singular to plural without either of us formally announcing it.

They're right, whoever said that in the reading voices.

We are.

I don't know what that means for the rest of this. I don't know if two people working together can undo what one person decided alone at a desk at 2 a.m. I don't know if Law Five is robust enough to hold against what I know is coming in the draft, if small changes will accumulate into something the chain can't recover from, if The Ink will keep taking things in proportion or if the corrections will scale with the interventions.

I don't know any of that.

What I know is that tomorrow Kael will be at his table in the amber light and I will be at mine and there will be a *we* where there used to be a complicated solo problem, and that changes the shape of everything even if it doesn't change what's coming.

It's enough to work with.

For tonight, it's enough.