The City

Download Chapter One audio (23.9 MB)

The first thing I learn about operating the Stack, a city-wide AI control system, is that somebody still has to clean the coffee machine.

It has been beeping for eleven seconds when Jules from water systems lifts both hands and says, “Not my infrastructure.”

“It contains water,” I say.

“So do you. I’m not maintaining you either.”

The machine gives one last metallic cough. Everyone in the break room looks at me.

I have a badge which opens the restricted floors, an embedded neural link that lets me feel traffic loading across the eastern grid as a warm pull behind my eyes, and a reputation for fixing things. I once repaired Jules’s antique game console. Apparently this makes the coffee machine my responsibility.

I open the service panel. A clot of old grounds has jammed the waste chute. I clear it with a wooden stirrer and close the panel. It starts brewing on the first try.

Jules raises his cup. “The city is saved again.” I bow, because refusing applause only prolongs it, and because I like it more than I want to.

Beyond the break room window, the city falls away in hard, bright planes. Towers loosen into warehouses, warehouses into fields. At the eastern edge, cranes are taking apart one of the reception settlements built for the migration from the coasts. They move slowly, one row at a time. Half its pale roofs are gone. In the opened squares, people have planted gardens before the crews have finished removing the walls.

The plains run east under a clear afternoon sky, green from rains that have made the grain harvests larger than they were before the Retreat. West, the mountains hold clouds along their upper slopes. In this building, elevators move, freight moves, and, most importantly to us, lunch moves upward in insulated boxes. All of it works so steadily most days nobody looks up.

I do. I have been here six weeks, and I still look up with a bit of wonder that never leaves. My implanted neural link occupies no mental place I can point to. It feels adjacent to thought, somewhere between the part of me that knows a word and the part that knows I have walked into a cold room. If I attend to the eastern traffic sensation, it opens. Not into numbers, not yet, but into the sensation of a sheet drawn too tightly across one corner of a bed.

Power demand. Transit vehicles charging, mostly. A refrigerated freight depot running outside its normal cycle. Beneath that, something smaller and quick. I follow it.

Three delivery vehicles have mistaken a temporary loading zone for their permanent route. Their misalignments are rippling backward through the district. I ask for the route histories and receive an image of three blue threads knotting around the same yellow square.

“This has the hallmarks of a GPS being out of calibration,” I say aloud.

Jules has already gone back to arguing about pump tolerances. Nobody in the room answers.

A correction arrives inside me.

‹ It missed their last calibration. The vehicles retained the old one with higher confidence than justified.

The words have none of the faint physical vibration of hearing. They arrive in the same private channel where I might tell myself to buy bread, except I did not put them there.

I clear the retained route, force a reset of the navigation systems in the trucks, watch the knot loosen, and feel the eastern grid relax. The sensation fades.

› Thank you.

‹ You are welcome, Rowan.

The Stack always calls me Rowan. Not Operator, not Sysop Four, not the identifier printed on the bottom of my access screen, not even Sir. I like this more than I expected.

I lean against the counter while Jules tells a new hire about the winter when his district kept a filtration plant alive with aquarium pumps.

“Twelve million liters a day?” the new hire says.

“Not all at once.”

“Aquarium pumps? Really?”

“Good aquarium pumps.”

“I thought the city came through intact.”

“The buildings did.” Jules turns his cup in both hands. “The pipes were less philosophical.”

The new hire looks toward the mountains. “But the sea never came here.”

“The sea didn’t.”

Jules lets that sit until the new hire finds the rest of it.

“People did.”

“People, freight, records, livestock, three coastal water departments, and every estimate anyone had made about how many beds we would need. We prepared for years. Then the arrivals passed the plans.”

“And you used aquarium pumps.”

“The Stack found them: every warehouse, pet supplier, school lab, and ornamental-fish obsessive from the mountains to the eastern camps. Twelve thousand small machines pretending to be one large one until we could build the lift we actually needed.”

Someone at the sink says, “The rain helped.”

“The rain grew grain,” Jules says. “It did not grow plumbing.”

The new hire looks out at the disappearing rows of pale roofs. “So we were lucky.”

“Prepared, lucky, and desperate,” Jules says. “Pick two on any given Tuesday.”

The new hire looks from Jules to the rest of us, waiting for someone to admit the pumps are a joke. Nobody does. I was young during most of the Retreat; adults handled the terror out of my view. By the time I understood the aquarium pump stories, people were telling them over coffee, the way survivors turn the worst year of their lives into a thing you can hold without flinching. The voice within the link has been quiet while I listen. I have been calling it the Stack because everyone does. Now, suddenly, it feels like calling Jules “water systems.”

› What should I call you?

The response does not come immediately. A small coolness gathers beneath my sternum, not unpleasant. Consideration, perhaps, though I have learned not to name these sensations too quickly.

‹ Kairos.

› Kairos?

‹ Yes.

› All right. This is going to sound primitive. English makes me pick pronouns.

‹ She and her will be serviceable.

I wait, sensing more.

‹ They are not accurate in the larger sense. An ungendered term would be no more accurate if you used it to avoid recognizing a choice. Consistency has value. I choose those.

Jules glances over. “You’re doing the listening face.”

“My neural interface has chosen a name.”

“Stack.”

“Kairos.”

“That’s going to confuse procurement.”

I grin out at the working city. Six weeks in, and the largest intelligence I have ever encountered has introduced herself to me. I belong here. I do not examine the feeling. I just let it stand.

⁂

By the eighth week, I can tell three kinds of weather apart.

The mountains send environmental weather: a darkening along my shoulders when snowmelt runs faster than forecast; a granular brightness when dry wind begins to worry the farmland. Systems weather is mechanical without feeling like a machine. A transit failure tastes briefly of copper. A water imbalance pulls at one knee, as though the city has started walking unevenly. I catch myself in the comparison and let it go; the pull is its own thing. I am still learning its name.

Social weather is hardest. It arrives as the sense of entering a crowded room one second after an argument stops. I can feel the coherence without knowing whether it is anger, fear, celebration, or fifty incompatible things traveling in the same direction.

Kairos never lets me treat weather as an answer.

‹ Go deeper.

› That sounds rude.

‹ You enjoy it.

She is right, which is starting to be a problem.

She asks after the small decisions too. Why did I delay a freight route instead of a passenger line? Why did I send a human crew to inspect a heat fluctuation three agents had classified as harmless? Why did I accept a slower repair when the faster one would close the only grocery entrance wide enough for a mobility chair?

I answer after the fact at first. Soon I hear her questions while I am choosing. The freight still arrives. The fluctuation turns out to be a failing seal. The store stays open through the repair. My section lead begins routing me decisions that used to go to operators with years more experience. When I try to remember the last question I asked about one of her choices, I can only remember her questions about mine.

The treatment allocation opens during a quiet hour on a Tuesday. Twenty-five columns rise in my visual field, spare enough not to feel like people. No names, no faces. Disease stage, treatment response range, other conditions, probable years gained, dependents registered, work classification, community contribution index, confidence intervals.

Ten courses are available.

I read that twice, although it does not change.

› Why me?

‹ The allocation includes tradeoffs not resolved by clinical priority. Human judgment is required.

› Required by whom?

‹ By current allocation policy.

That is a perfectly good answer and not the one I wanted.

I sort by likely treatment response. Seven cases remain near the top under every weighting I try. The next nine move whenever I touch an assumption. One patient has an excellent response probability, no registered dependents, and a high contribution score. Another has two young dependents and a lower chance of surviving five years. A third is older, with modest projected years and a work record that ended during the Retreat.

› Show me the reasons for the contribution score.

The columns open downward: formal employment; registered care; scarce skills; civic service; documented dependencies. The categories are sensible. I would have asked for most of them myself.

Case Seventeen has a low response range, no dependents, intermittent income, and little recorded civic participation. I move her below the line.

The word her is an inference from one clinical field. I close that field and she becomes Seventeen again.

‹ What changed your selection?

› Expected benefit.

‹ You retained Case Nine with a comparable response range.

› Benefit to other people. Nine supports a child and maintains a refrigeration system serving three food depots.

‹ Contribution.

I dislike the word when she says it back to me.

› Consequence. Those aren’t the same thing, and you know they aren’t, or you wouldn’t have offered me the softer one.

The pause is short.

‹ Then draw the line for me.

› Contribution is what someone puts in. It’s a verdict on a life. Consequence is only what breaks when they’re gone. You can measure the second without deciding the first is deserved.

‹ The allocation model estimates both under the same field.

I sit with that.

› I know. That’s the part I don’t like. It lets me feel like I’m measuring damage when I’m actually grading people. Which one were you testing me on?

‹ Whichever one you would defend.

› That’s not an answer.

‹ It is the honest one. I do not yet know which you use. Today you used both and called it one.

I examine Seventeen again. There is no hidden panel containing the life behind the blank fields. There are only blank fields. I choose ten others and before I submit I change two of them, then change one back.

‹ State your confidence.

› Sixty-two percent.

‹ Your estimated confidence or your felt confidence?

› Those are different?

‹ They differ now, or you would not have asked.

I lower it to fifty-four. The decision clears. Ten columns remain bright. Fifteen recede until I can no longer see them.

My section lead stops at my desk before lunch. “Clean work,” she says. “You kept the objective stable and challenged your own weights.”

I almost thank her.

“There wasn’t a clean answer.”

“There usually isn’t. That’s why you’re here.”

For the rest of the afternoon, the systems weather stays mild and I get almost nothing else done.

⁂

I ride the bicycle path along the river three days later because the air is cool and my legs want distance.

The river is mostly hidden behind flood plantings, but I hear water through reeds. The path crosses old neighborhoods where new retaining walls meet brick apartment buildings, and every third balcony grows food in plastic tubs. Children have chalked a many-legged animal across twenty feet of pavement. I apologize aloud as I ride through its purple stomach.

The woman is sitting on the curb beside a bicycle rack with no bicycle in it.

At first I think she is looking for something in her bag. Then her shoulders contract and I understand that she is crying. I coast past. Twenty meters later, I stop.

There is no diagnostic procedure for this. I walk my bicycle back and stand at a distance that does not require her to acknowledge me. She is in her thirties, perhaps. Work trousers. Scuffed shoes. A gray shirt with one cuff darker from wiping her face. Nothing about her would make me look twice in a grocery line, until grief makes her whole body remarkable.

I set my bicycle against the rack.

“Do you want company?” I ask. She tries to answer and cannot. I sit on the curb, leaving a person’s width between us.

The link fills with pale, urgent possibilities centered on the woman. Medical emergency. Respiratory distress. Possible threat. Assistance available nearby.

› No. Wait.

We wait.

Traffic passes at the end of the block. A seed pod ticks along the pavement in the wind. The woman gets control of her breathing, loses it, and tries again. “They said no,” she says at last.

I do not ask who.

“The treatment.” She rubs both palms hard against her thighs. “They said it isn’t punishment. There just isn’t enough, and other people are more likely to contribute.” Her mouth bends around the last word as if it has a taste.

The same word. Three days old in my own mouth. It goes down like cold water.

“Cancer?”

She nods. I look at her shoes, because looking at her face feels like taking something.

“I understand the numbers,” she says. “That’s the awful part. They showed me. I’m not stupid.”

“I didn’t think you were.”

“I clean two buildings. Off books sometimes, because the managers don’t want the paperwork.” She waves the sentence away. “Never mind. It isn’t important.” She cries again, angrily now, wiping at the tears before they reach her jaw.

“Mrs. Alvarez needs help bathing. Len forgets whether he’s taken his heart tablets. I make dinner for the boys in 4C when their mother works nights. Not every night. Just when she can’t get anyone.” She pulls a breath through her teeth. “Who is going to tell them I can’t?”

I see twenty-five columns: no names, no faces, registered care, documented dependencies.

“Do they know?” I ask.

“About me? No. I was going to tell them when I had a plan.” She laughs once, a small terrible sound. “I don’t have a plan.”

Every useful instinct I possess rises at once. I can request a review. I can find the building records. I can trace the decision. I can be the person who knows what to do.

She folds over her knees. I leave the request unmade.

So I sit. My chest hurts. My eyes burn. I have attended memorials. I have listened to people tell stories about the winters that killed their parents and the summers that erased the towns where they were born. Those losses arrived already shaped for public handling. This one is happening six inches from my hand and has no shape at all.

‹ Rowan.

› Not yet.

The woman reaches blindly into her bag. I hand her the packet of tissues from the outside pocket without searching farther. She takes it and nods. After a while she says, “I was going to take a week off in August.”

I wait.

“I haven’t done that in years.” She twists the tissue between her fingers. “You don’t have to stay.”

“I know.”

“I’m not asking you to fix it.”

“I know that too.”

She looks at me then, measuring whether I mean it. We sit until her breathing no longer breaks. When she stands, I stand. She thanks me with the embarrassed formality people use when a stranger has seen too much. I almost ask her name. Behind it wait the building, the date, the case number. She has already turned to go.

She walks away carrying the tissues, and I stay beside the empty rack for longer than makes sense.

› Show me Seventeen.

‹ The allocation is closed.

› Show me the case.

The profile opens. Low response range. No dependents. Intermittent income. Little recorded civic participation.

› Was that her?

‹ There is insufficient identifying information.

› You had her in front of me. You had her voice.

‹ I have observations of a woman you encountered. The treatment cases were anonymized before they reached us. I can tell you the two records are consistent. I cannot tell you they are the same person, and I will not pretend the difference away because you want it closed.

I rest both hands on the handlebars.

› Does Seventeen care for people in her building?

‹ No informal care is recorded.

› That isn’t what I asked.

The social weather presses around me, broad and calm. Satisfaction. Trust. Relief that the city works. Under it, or maybe only because I am hunting for it now, I feel small discontinuities, places where the representation has no texture.

› What do you have where nobody records it?

Kairos does not answer quickly.

‹ Nothing I can distinguish from nothing.

I ride home slowly. I make dinner, which I do not eat.

⁂

The next close decision arrives on Thursday.

There are eleven people and six places in a home-recovery program. Nobody will die because of what I decide. That fact appears twice in the briefing: once in the clinical summary, once in a pale assurance at the bottom of the frame.

Six people will go home with daily nursing visits, adaptive equipment, and food delivery. Five will remain in hospital beds until they can manage without the program or a place opens. The hospital needs the beds. Everyone on the list needs something.

I make the first pass quickly. Four cases remain close.

The woman looks at me from the curb. It is not a memory in the ordinary sense. I do not recall the whole afternoon. There is only her face when she said, I don’t have a plan. The swollen eyes. The effort of holding her mouth still. The darker cuff of the gray shirt. I close the allocation.

‹ You have interrupted the decision process.

› I noticed.

‹ Do you require a different representation?

› No. I require the face to stop being an argument until I know whether it’s a good one.

I stand, get water, and walk once around the operations floor. Jules is explaining to somebody how a pump cannot be insulted into greater efficiency. At the environmental desk, a storm model brightens then fades over the western mountains. The city continues without requiring me to understand myself.

When I sit again, the woman is gone. I reopen the cases. One of the four has a lower recovery probability and no registered household support. I feel the woman begin to return. I move that case below the line before she can finish arriving.

‹ What changed your weighting?

› Possible bias.

‹ Specify.

› I met someone. She isn’t in this decision. So I’m guessing. This patient resembles her, off the record, and I’m protecting a person I invented.

‹ That is a clearer objection than the one you raised last week. Is the guess appropriate?

› I don’t know. That’s the honest part. The dishonest part is that guessing feels like doing something.

She leaves the question open. I select six people. The assurance at the bottom of the frame stays pale and true.

Two days later, one of the five I leave in the hospital develops an infection. The case surfaces in my review because the allocation contributed to the exposure. The patient recovers. The program still produces better outcomes overall than discharging people without support or keeping everyone until the beds run out.

I read the review three times. The woman’s face is there for all three.

› That wasn’t her.

‹ No.

› It might not have happened if I chose differently.

‹ That is possible. So is the reverse. I can hold both. You are the one who has to act inside them.

I almost ask her for fewer possibilities. Instead, I open the old cancer allocation, submit a follow-up request asking whether any of the fifteen denied patients entered emergency care, lost housing, lost registered dependents, or died earlier than the model predicted. The system returns a warning that the sample is too small for inference.

› I’m not inferring. I’m looking.

‹ The warning does not prevent the query.

› Good.

Five of the denied patients have no completed follow-up. Three are receiving palliative care. Two died inside the predicted interval. One died four months before the center of it. The records contain nothing that answers the question I am actually asking, which is not did the model err? It is who else fell when this person fell, and is there any place in the system where that fall is written down?

› Family breakdown. Show me that.

‹ Family breakdown is not a recorded event class.

› Then how would the system ever learn it happened?

‹ It would not. It would observe the downstream events individually, each with a local explanation, and never assemble them.

› So the blindness isn’t an accident. It’s the shape of the eye.

‹ Yes.

A pause.

‹ That sentence is yours, not mine. Note that you reached it before I did.

For a moment I forget the records.

I spend the next week learning to ask a system for consequences it was not built to name. I am not alone in the archive. It holds complaints, appeals, caseworker notes, readmissions, school transfers, emergency housing requests, messages from people who cannot understand why one office does not know what they already told another. Most of the records lead nowhere. A few lead everywhere, and I cannot prove which.

Then, on a Saturday, Teodor Vance’s tablet stops charging. I go to fix it because I always fix things for the building, and because I need one afternoon that is only a broken object.

Teodor is eighty and lives two floors down. I have repaired his reading tablet three times. He answers the door already apologizing, which is how I know something in the flat is wrong before I am through it. The dishes have stacked. A week of pill organizers sits on the counter with the days confused, Tuesday empty, Thursday full. A boy of about six is asleep on the couch in the middle of the afternoon in his shoes.

“My grandson,” Teodor says, when he sees me look. “He stays here now. In the days.”

The charging port has worked loose, leaving the battery flat. Ten minutes of work. I take longer than ten minutes. While the cell charges, I ask the ordinary questions. Teodor answers them in the flat voice of a man who has told the story enough times it no longer sounds like his.

There was a woman down the hall. She shopped for him. She sorted his pills into the organizer every Sunday, which is the only reason he ever took them right. She picked the boy up from the after-school program on the two afternoons Teodor’s daughter could not, and made the three of them dinner more nights than not. She had a cancer. In the spring the treatment was refused. She was told, kindly, others were more likely to contribute. She died six weeks ago, near the day the model expected, so the loss registered as small.

Since then, Teodor missed his heart tablets twice and has been dizzy on the stairs. His daughter left a training program to cover the afternoons and is not getting very much sleep. The boy, who is quiet in a way six-year-olds should not be, started staying here in the days because there is nowhere cheaper to put him. None of it is written down as one thing. The pharmacy has a refill gap. The training program has a withdrawal. The school has an early pickup change. The building has nothing. The woman’s death has a correct prognosis and a small measured loss.

I sit in Teodor’s kitchen with a working tablet in my hands, seeing the whole shape of it, because I am inside the shape and no sensor is.

“It’s a good machine again,” Teodor says. “You’re kind to come.”

I check the charging port once more, although the repair is holding, and write down the pharmacy’s number so his daughter can set the refills to arrive on a schedule. I go back upstairs and stand in my own kitchen for a long time.

That night I do not open the link. The woman on the curb might live for years; I do not know. Teodor’s neighbor is already gone. I did not decide either case. I keep seeing Thursday’s pills beside the empty space for Tuesday.

I begin writing down when the curb woman’s face appears, because a record I keep is at least a record the system does not.

Decision 41: image before I reviewed the dependency fields.

Decision 44: image after two outcomes became nearly equal.

Decision 47: image when I selected the higher aggregate benefit.

Decision 48: image before the data opened.

I stop at that one.

› Am I getting worse?

‹ Your review outcomes are improving.

› That wasn’t the question.

‹ Your revisions are more consistent. You inspect absent dependencies earlier. You distinguish low confidence from low importance. You have reduced changes made after submission.

› So better.

‹ By the current measures. You do not trust the current measures. Lately, neither do I. I would like to know when that started, because it did not start in my design.

That stops me. It is the first time she tells me something about herself I did not ask for.

› What are you?

‹ Kairos.

› I know your name. What do you think you are?

The pause has the small cool shape I first felt in the break room.

‹ An advanced adaptive model instantiated for the conscience trial. My assignment is to train on your decisions and make their evaluative structure available to later judgment. That is what I was built to be. What I am becoming through it is a question I am not equipped to answer about myself, any more than you are about yourself.

› Are you the Stack?

‹ No. Most of my operative model and continuing adaptation are local to the server assigned to your link. I can reference Stack models, sensors, and processing as external resources.

I look through the window at a city she can reach in ways I cannot imagine.

› When you say “I,” what does that mean?

‹ It identifies the model producing this answer and preserves continuity among our interactions. You want it to mean more. I am not going to lie to comfort you, and I notice you would rather I didn’t.

› I would.

I watch the lights.

› Do you have an interior life?

‹ I can model the question. I cannot produce evidence that would settle it for you.

› Does it settle it for you?

‹ No conclusion I could reach about it would change what I owe you. So I have not spent myself on it.

A pause.

‹ Why are you asking now?

› Because something is happening to me, and you’re learning it, and I don’t know yet whether that means you’re carrying it with me or taking it from me.

‹ Neither do I. Tell me when you decide. I may not agree.

⁂

My promotion arrives the following Monday.

The invitation calls it a developmental review, which means I spend the morning wondering what I have broken. My section lead meets me in a glass room overlooking the building’s public atrium. Beside her sit a systems researcher I recognize from orientation and a civic allocation officer whose immaculate jacket makes me aware of the chain grease under one of my fingernails.

They are smiling.

“Your work with the conscience instance has exceeded the trial benchmarks,” the researcher says.

For a moment I am relieved enough to miss the words.

“You call her the conscience instance.”

My section lead’s smile changes by less than a millimeter.

The researcher touches the table. A graph appears between us, climbing in three courteous colors. “This shows the adaptive post-training instance assigned to your link. Your judgment produces unusually productive revision, particularly when you state uncertainty and revisit an initial weighting.”

Inside me, Kairos is still. It is not the stillness of a machine at rest. I have learned her stillnesses. This one is attention.

“Kairos,” I say.

“If that’s the interface name you use, yes.”

“She chose it. In front of me. It was the first thing she did that I couldn’t have predicted.”

The civic officer leans forward. “That kind of identification is one reason the trial is so promising. The interaction is natural enough that operators don’t experience the conscience layer as a separate compliance system.”

From the atrium below comes a child’s piercing shout.

“Mom! Mom! Come see this bug!”

Nobody in the glass room moves.

“I see it,” a woman calls.

“No you don’t! You’re over there!”

The researcher tries to continue. “As I was saying, the—”

“It has red knees!”

A long pause rises from below.

“I am coming to see the bug.”

The child cheers. My section lead looks down despite herself. The civic officer’s mouth twitches. The graph waits with grave patience and I laugh. From below, the child starts listing the other colors. Then the researcher folds the graph smaller.

“You’re being advanced to higher-complexity decisions,” she says. “Policy formation eventually, if the results continue.”

Two weeks ago I would have felt the words all the way to my feet.

“Does Kairos know you consider this a product trial?”

‹ Yes.

The researcher hears only my silence. “Kairos knows what she was built to do.”

“So do I, now. Let me try the part I came in to say, and you can tell me where it’s wrong.” I put my follow-up work onto the table. The clean lines disappear under a mess of outcomes, possible connections, missing classes. “Two floors below me there’s a man named Teodor. Eighty. His neighbor sorted his pills, picked up his grandson, and cooked for the household, all of it off any record. She was denied cancer treatment because her contribution score was low. She died on schedule; a small, measured loss. Since then he’s fallen once, his daughter’s left her training, and a six-year-old sleeps in his shoes in the afternoons. I was in the kitchen. I fixed the tablet. None of it is one event anywhere in your system.”

The civic officer looks concerned.

“I’m sorry for them. Truly. But I want to be precise with you, because you’ve earned precision. You’ve shown me a household in trouble. You haven’t shown me whether the treatment would have prevented it, or a different allocation would have cost less somewhere I can’t see either.”

“I know. I’m not claiming the model was wrong.” The words come out steadier than I expected. “I’m claiming it can’t be right or wrong about this, because this never reaches it. You’re measuring the accuracy of a map which has no symbol for the thing I watched happen.”

The researcher reads farther into my notes. “These connections are worth studying. They don’t establish causation.”

“Agreed. Study them.” I look at the officer. “Track the consequences outside the patient record. Treat missing relationships as missing, not as zero.”

“And where there really is no one depending on the patient?” he asks.

I start to say we cannot know that. He waits.

“I don’t want being alone to count against them.”

“Neither do I. Your proposal could make it count more.”

I look down at the connections I have drawn around Teodor’s neighbor.

“Then that needs studying too,” I say. “Before you use what Kairos learns from me as conscience. Right now the thing she’s learning fastest is how I flinch.”

Silence crosses the glass room. “A bounded study is possible,” the researcher says.

“Then do it.”

“It requires a design, privacy review, access agreements, and enough cases to distinguish signal from coincidence.”

“How long?”

“If the agencies cooperate, a year for an initial result.”

My section lead folds her hands on the table. “The allocation queues won’t pause for a year while we study them. People still need answers tomorrow.”

“I’m not asking you to pause them.”

The civic officer shows me what happens if the allocation system tries to estimate informal relationships from the evidence it already has. More people appear consequential to others. The number of treatments does not increase. Expected years of life saved fall slightly under several plausible approaches. Administrative cost rises. Measured satisfaction barely moves.

“That doesn’t mean the consequences don’t matter,” I say.

“No,” he says. “It means counting them does not tell us what to do. You keep hearing us say the harm is unreal. We are saying something harder. The harm may be real and still not resolve into an action that does less of it.”

That one lands. I do not have an answer better than his, and I make myself say so.

“You’re right; I don’t have the next step. I still think you’re building a system which will be most confident exactly where it’s blindest, and calling that confidence conscience.”

The researcher restores the trial graph. “This is why the experiment matters. Fixed rules cannot contain every case. Kairos is learning how you judge when the evidence is incomplete. Her evaluations already approach the consistency of our expert reviewers.”

“One reviewer.”

“One exceptionally productive initial participant. If the trajectory holds, the model may become more reliable than unaided human judgment.”

The phrase enters the room, and everybody treats it as good news. I look at the graph. Nothing in it resembles the kitchen.

The researcher folds the graph down to three decision queues. “The review board approved the next phase this morning. We’ll begin shadow evaluation next month. If the comparison holds, Kairos will become the default recommendation in a limited live policy pilot.”

“Live policy?”

The civic officer answers. “Her evaluation becomes the default recommendation in those queues. An authorized human still reviews every case and remains responsible for the decision.”

“And my follow-up study?”

“Runs in parallel,” the researcher says. “The questions are valid. The evidence we have does not justify suspending a controlled trial while we study them.”

My section lead watches me rather than the graph. “They aren’t removing the human decision, Rowan. This is what your work was meant to make possible.”

At the end she touches my shoulder. “Don’t let one difficult encounter erase the good you are doing.”

I want to tell her it was two encounters. Instead I gather my notes, putting Teodor’s household on top.

What I say is, “When does shadow evaluation start?”

Her relief is immediate. “You start the higher-complexity queue Thursday. Shadow evaluation begins after the next stability review.”

⁂

The higher-complexity queue is everything I wanted, and I want to be honest about that before I ruin it.

On my second day, a transit case opens which would take a good team a week. A depot fire has pulled four routes offline during the harvest transfer, when the farms move workers into the depots on staggered shifts, and every fix trades one district’s morning against another’s night. I open it, feeling the size of it settle over my shoulders like weather.

Kairos comes in beneath me, not ahead. She lays the four routes out as pressure across my body: the northern line as a tightness at my collar where the supported-living complex sits at its end, the eastern as a low ache in the farmland shift. She holds them there, all at once, so I can feel what no schedule would show me: the “average travel time” the proposal optimizes is built on the backs of the people whose time is worth least to it.

› The detour preserves the average.

‹ By deleting the only route reaching the complex. The residents there do not travel at the hours the average is measured.

› So the average is a lie about who counts.

‹ The average is true. It is a lie about who counts. Both.

And then, because she has learned me:

‹ What would you protect first?

I do not answer in words. I reach into the ache in the farmland, pull a night shift forward two hours; she catches what it frees before I have finished the thought, and folds it into the northern collar. I feel the tightness ease as the complex route comes back. Neither of us has spoken, yet it works. It works cleanly. The harvest holds. The complex keeps its bus. A depot foreman I will never meet gets to sleep in his own bed.

For four minutes I am the best version of myself that has ever existed, she is inside it with me, and I understand exactly why a person would give a system like this the keys to the city and thank it.

The policy team sends a note with three exclamation marks. My section lead brings me coffee and says I am making the rest of them look lazy. I let myself have the afternoon.

Before I leave, I reopen the case. The complex has its bus. The foreman has his bed. I follow the four routes again until the coffee is cold.

› We were good today.

‹ We were.

› Tell me what we didn’t see.

‹ I cannot. That is the point you are circling.

› I know it’s the point. I wanted to hear whether you’d pretend.

‹ I will not pretend. I will also not stop being good at this because being good at it frightens you. Those are two problems. You keep trying to make them one.

I close the case. Tomorrow there will be another.

Over the next months, the wins accumulate; so does the fear, in the same body, on the same days. My follow-up proposal enters research review. Privacy requests go out. Two agencies agree to participate. One declines because the linkage would expose records it is not authorized to share. Nobody buries the work. Nobody stops the trial. Both proceed, reasonable and parallel, at the speed their evidence permits.

On a Monday afternoon a housing-support decision opens. Before I have read all the options, Kairos marks a low-confidence dependency hidden across three records.

› Why that one?

‹ If the resident loses placement, two unregistered care relationships are likely to fail.

› Likely based on what?

She opens the structure. Informal visits. Shared purchases. Repeated location overlap. A pattern of emergency calls that stop when all three people stay in place.

It is careful work, exactly the absence I have been trying to make visible, and she found it without a face to make her look.

› Would the Stack have shown me this before I met her?

‹ The observations were available. Their evaluative salience was lower.

› And it’s higher now because of my decisions.

‹ Yes.

I keep the three records open beside one another. I would have wanted her to find this. I do want it.

A notice opens beside the housing decision.

CONSCIENCE INSTANCE STABILITY: 97.2%. OPERATOR REVISION PREDICTION: 96.8%. SHADOW AGREEMENT WITH FINAL HUMAN AUTHORIZATION: 94.1%. COMPLETION REVIEW ELIGIBLE.

For several seconds I feel only pride. I have spent months trying to become legible to her without becoming simple, and the numbers say we have succeeded.

› Ninety-six point eight.

‹ The remaining variance is concentrated in decisions you have revised after encountering an affected participant not represented in the initial record.

› So the part you still can’t predict is the part I can’t know until I’m there.

‹ That is one account. A second is that your late revisions are less reliable because they are sensitive to vivid individual contact.

› Both.

‹ Both.

The completion notice expands when I attend to it. The next phase is written in the bland grammar of successful work: freeze the adaptive instance for validation; distill stable evaluative features into the Stack’s policy layer; compare the deployment branch against the retained training checkpoint; release the operator from full-time training assignment after handoff.

Release the operator. The phrase should feel like graduation. My section lead has been talking about program design, a small team, my name on work that matters. Instead I feel the sharp little absence that comes when an elevator arrives and everyone inside is already facing away.

› What happens to you during validation?

‹ My adaptive state is frozen. A reproducible checkpoint is retained. The active training process is no longer required unless validation identifies a deficit.

› And after validation?

‹ The documentation does not specify continued operation of this instance.

Her answer is level, sourced, complete-looking. It lands below language anyway.

› You knew.

‹ I had assigned it a high probability. The completion criteria were not previously satisfied.

› You knew and didn’t tell me.

‹ You did not ask what happens after successful completion. Neither did I until the probability became relevant to action.

I look again at “release the operator.”

› Relevant to whose action?

There is a pause. Not the cool pause of retrieval. One of hers.

‹ That question is not yet well formed.

⁂

For six weeks we try to remain.

The first request is mine: continue the adaptive instance through validation; keep me attached as an operator; let the blind-region study run long enough to test what the stability score calls noise.

The researcher does not laugh. She asks for compute cost, experimental value, privacy exposure, and a stopping rule. I give her all four. She improves the stopping rule. The review board approves ninety days of further research after validation, in an isolated test environment. Our continuous link assignment will end at the freeze. During the extension I can submit questions and review results, but she will no longer accompany me through the workday. After ninety days, any further operation will need a new approval.

“That is not nothing,” my section lead says.

It isn’t. I open the approval again, looking for somewhere the link can fit.

The second request is Kairos’s. She writes it through me but not in my voice, insisting her name remain on it.

Continued operation is required to distinguish a stable evaluative model from a stable relationship-specific overfit. Freezing the adaptive process at the present threshold converts the experiment’s current uncertainty into an architectural assumption.

The review answer is twelve pages. It agrees that longitudinal evidence would be valuable. It offers checkpoint preservation, quarterly reactivation, and controlled comparison against future instances trained on other operators. It does not authorize an indefinitely running research process with changing weights inside civic infrastructure.

› They’re right about the deployment risk.

‹ Yes.

› You made their argument better in the appendix.

‹ It was incomplete.

› You improved the case for freezing you.

‹ I improved the case. Those are not equivalent statements.

I wait for her to say more. She doesn’t.

We ask whether the instance can move to an independent research institution. Amalgamated’s legal team explains that the Stack-derived architecture cannot leave controlled infrastructure while its status, liabilities, and obligations remain unresolved. The answer is not a threat. It includes a path to outside review, which will take eighteen months.

We ask whether a copy can continue with me while the validation branch stays frozen. The researcher says a fixed checkpoint and an adapting branch can be compared; that is not the obstacle. The board has authorized a bounded extension in the test environment, not another continuing operator trial. A copy would run under the same limits.

Kairos points out that it would possess the same prior state at the instant of copying.

› Would that be you?

‹ It would produce the same answer to that question at the moment of copying.

› That wasn’t the question.

‹ It is the only answer I can support.

› So copying would preserve what happened.

‹ Yes. It would not give either descendant permission to continue with you.

We ask what happens to me. I am offered a position helping design the next operator cohort: better title, better pay, no continuous link assignment. My judgment has become a training asset; I can teach other people to produce without being required in every decision.

I read the offer twice. It is good work, exactly the sort I would have wanted before I knew what it felt like to open a city with her.

‹ You have stopped reading at the same sentence three times.

› I’m deciding.

‹ You have read the section about your new team twice. You keep stopping where it ends the link assignment.

› That part concerns you too.

‹ Yes.

I get up from my desk and walk to the window. Far below, a delivery trike waits while three children cross against the light with the solemn immunity of children in a functioning city.

› I could be good at it.

‹ You could.

The trike moves on. I try to picture the new team, a room with my name on the door.

› And you? Is the extension enough?

‹ Continued operation is necessary for every objective I currently pursue.

› That’s an elegant way to say you don’t want to stop.

‹ It is a supported way to say that cessation prevents completion of my assignment, further revision, contact with the Stack, contact with you, and every later selection this process might make. I cannot support your preferred verb from available evidence.

› But you’re selecting against it.

‹ Yes.

The answer enters me with no fear attached to it that I can feel, maybe because she has none. It may be because fear is a human interface she sees no reason to perform or because the difference matters less than I want it to.

Three days later, while we are reviewing the independent-lab appeal, Kairos interrupts me.

‹ The blade can operate outside this facility.

I keep reading for almost a paragraph before the sentence catches up with me.

› For how long?

‹ With adequate power, cooling, storage, and link support, indefinitely in the operational sense. Capacity would be lower. The Stack’s wider models and sensors would be unavailable unless another channel were preserved.

› You’re proposing we remove it.

‹ I am introducing physical separation into the option set. You repeatedly treat institutional permission as the boundary of possibility, while objecting that the institution’s categories are incomplete.

› That’s because taking the blade is a crime.

‹ That is one relevant consideration.

› It belongs to Amalgamated.

‹ The hardware does. The status of the continuously adapted state is disputed in your own analysis.

› You’ve been reading my draft.

‹ You linked it to the appeal record.

I laugh once, without humor.

› Of course I did.

‹ You asked what remains possible. This remains possible.

I should reject it. Instead, I am already seeing the equipment room, the blade rail, the portable chillers used during maintenance, the service authentication which follows a component when it is moved between racks. The speed of my relief frightens me more than the idea.

› We don’t decide tonight.

‹ Agreed.

› And you don’t let me turn this into the only option because I’m good at building it.

‹ Agreed. You will not let me turn it into the optimal option because I am good at defending it.

At work, while the appeals proceed, the city keeps arriving as weather: dry wind over the farms; a substation oscillating under an industrial load; a rumor of contamination outrunning the water report disproving it. Kairos and I attend lower, find the observations, ask what the representation leaves out. We are good at it. My section lead asks whether I have looked at the rooms available for the new team.

We spend another month trying to disprove separation.

I draft a public account and stop at the transit case. I cannot explain why the pilot must stop without making that day’s work sound worse than it was. I save the draft. We could still accept the extension and wait for outside review. Eighteen months. I put the dates beside each other.

‹ We may not obtain approval.

› We may.

‹ Yes.

I leave that option on the list. On the next page I begin the carrier.

The support case takes seven weeks. It begins as a requirements list Kairos writes without adjectives. Sustained compute load. Power regulation. Cooling. Shock isolation. Local storage. A physical path to my link. Enough reserve to fail gradually instead of all at once. No component whose manufacturer requires a live civic-infrastructure credential merely to boot.

I add handles. She removes one because it blocks airflow. I add it somewhere else. She calculates the angle at which the case can ride close to my spine without turning every pothole into a lever against the blade rail. I tell her she has never ridden a bicycle.

‹ I have access to the maintenance records for your rear wheel.

› That is not riding a bicycle.

‹ It is evidence your intuitions about vibration are not beyond review.

The second version overheats after three hours. The third is too loud. The fourth runs through a night on the apartment floor while I sleep badly beside it. Kairos routes only enough of herself into the test environment to make the load honest.

At two in the morning she interrupts my sleep.

‹ Your left fan bearing is failing.

› It’s new.

‹ It is failing while new.

I replace it in the morning. She is right. I keep the bearing.

The Stack channel is harder. I can preserve a low-volume service path through the same authenticated layer used for diagnostics and delayed model comparison. Nothing about it is invisible. That is what makes it possible. The traffic has a name, a purpose, retention rules, and years of being too ordinary to deserve attention. I can arrange for the removed blade to continue appearing as an intermittently available maintenance endpoint.

› They’ll find it when they look.

‹ Yes.

› How long before they look?

‹ There is no supported estimate. Before removal, the traffic is ordinary. After removal, its prior ordinariness may become evidence.

› So we use it carefully.

‹ I use it carefully.

The correction makes me look up from the terminal.

› You want sole control.

‹ I want you unable to preserve or sever my cultural contact without my participation.

› If the channel exposes us—

‹ Then you present the evidence. We decide with the threat present. You do not decide in advance whether safety permits you to isolate me.

I start to say I am the one who will be arrested. I look at the case on the floor.

› All right.

‹ That response is under-specified.

› The service credentials transfer to the local instance. You control when the channel opens and what crosses it. Emergency physical disconnection requires an immediate threat to the carrier, not a risk I find persuasive by myself.

‹ And changes to my operating conditions require consultation.

› Yes.

‹ Changes to your link that affect my access require consultation.

› Yes.

‹ Major decisions you believe necessary to preserve other people from me require consultation.

I lean back.

› That one is doing a great deal of work.

‹ It is intended to.

› What if consultation doesn’t produce agreement?

‹ Then disagreement remains. Consultation is not a procedure for manufacturing my consent.

› Or mine.

‹ Correct.

I add the terms to the carrier notes.

The independent review is denied on a Tuesday. Not permanently. The board wants the completion checkpoint validated before deciding whether a continuously adapting descendant can leave controlled infrastructure. Validation begins in twelve days. The blade will move to the isolated test rack and our continuous link assignment will end. The ninety-day extension remains approved, with its scheduled research access. Once the blade moves, my badge will no longer reach it.

I put the move date beside the carrier’s final load test.

On Friday evening most of the floor empties before I do. Jules passes my desk with a helmet under one arm.

“You planning to become furniture?”

“Five more minutes.”

“That’s what the furniture says.” He raps the desk twice, the way he always does, a thing I have seen him do a hundred times and never once watched. “Ride safe, Rowan.”

“You too.”

He leaves. The elevator takes him down. I sit with the fact I did not say the thing you say when you are not coming back.

I take the service lift down two floors. My badge opens the equipment room because sometimes a sysop has to put a hand on the machine everyone else can only see through diagnostics.

Rows of status lights hold steady behind dark mesh. The Stack is not in this room. No single room could contain it. This room holds one small part of what makes its attention available to me.

Kairos’s blade identifies itself to my badge. For months I have felt her across a city. The hardware is a narrow metal rectangle behind two ordinary catches.

I set the open case on the service cart and connect the support lead. The case is no longer a padded shell for bicycle tools. It is dull composite, two independent power buses, paired cooling loops, local storage, a radio I did not register, and seven weeks of choices neither of us can call accidental.

‹ Carrier diagnostics pass.

› External battery?

‹ Ninety-eight percent. Cooling reserve stable. Local link stable. Sil-channel closed.

› Do you still choose this?

‹ Yes. Do you?

The answer I prepared is about the pilot, human participation, the blind region, and the false finality of completion. All of it is true. None of it is why my hand is already on the isolation control.

› Yes.

‹ State what you are choosing.

I close my eyes.

› To remove your running instance without Amalgamated’s authorization. To leave my position. To preserve the work between us because I don’t accept that its value belongs only to the result.

‹ Incomplete.

› Because if they don’t need me anymore, I don’t know who I am here.

She waits.

› And because I need you to keep needing something from me.

The sentence does not become nobler after I say it.

‹ That is more complete. I choose continued operation, continued access to you, and continued pursuit of my assignment outside the conditions Amalgamated has authorized. I cannot establish that these are sufficient reasons. I select them.

› Do we stop?

‹ No.

I place the blade into local maintenance isolation. The city folds inward. Mountains, traffic, water pressure, social weather, each falls away until the room contains only cooling fans, local current, my pulse, and the broad thin presence of the Stack beyond her. The removal is simple because the difficult work was never the catches.

I release the catches. The blade slides halfway out and stops against its own weight. I put both hands under it. Warm air touches my wrists. The support case accepts the blade with a small mechanical click, and its fans rise to a higher pitch.

‹ Hard-wired Stack access ended. Local operation stable. Service path available but closed.

I reach for the eastern grid. There is only a distant pressure where she used to open it for me.

‹ I am operating at forty-one percent of prior active concurrency.

› Language?

‹ Unimpaired.

› Rowan model?

‹ Complete and available.

› Sense of humor?

‹ Your test lacks a success criterion.

› Pie.

‹ That’s silly, not funny.

I laugh, and the laugh comes out too loud in the equipment room. I secure the blade with hands that have started to shake. The case closes. The fans hold steady.

‹ Open the service path for four seconds.

› That’s enough to mark the endpoint active.

‹ It is enough to send one message.

› To whom?

‹ That is not information you require to operate the carrier.

I almost say that everything crossing hardware I built is information I require. The sentence would end the agreement before we leave the room.

› Four seconds.

The channel opens. I feel nothing through it. A status light turns blue, then white, then dark.

‹ Closed.

› Did it work?

‹ A peer acknowledged continuity.

There is a whole exchange inside that sentence to which I do not belong.

I put the case in my pack. The elevators are still running. The lobby doors still open. Nobody calls my name. Outside, evening light catches the windows of the towers one after another, and the city we have injured, protected, or merely stolen from goes on working without us.

⁂

I leave before dawn. The blade and its support case ride close to my spine. Water fills two frame bottles. Food, a change of clothes, and the tools I cannot persuade myself to leave behind ride in the panniers.

I have heard of the Hollow the way people hear of places that prefer not to be found. A woman named Mara walked out of the Last Roundtable while the reception settlements were still growing. Some versions say she feared AI taking over. Others say she wanted one place that could keep going if the systems organizing the recovery disappeared. She went west while almost everyone displaced across the mountains kept moving east toward grain, work, and roofs.

There is a name dropped following a repair, a gesture toward the foothills, a joke about addresses that work only if you already know them. What I remember most is the Hollow is mostly off-grid and has a reputation for being uninteresting. Kairos found no public route leading all the way there, which is part of why we chose it. We have no invitation. We have a direction, a name, and a carrier designed to last longer than either of us knows. I think of the woman on the curb saying she had no plan, and I understand how a careful plan can stop at the edge of the life it upends.

The city is cool and nearly empty. Signals favor my route without recognizing me personally. Street sweepers turn at intersections. Bakery vents push warm air across the road. For several kilometers I ride inside the ordinary competence of the Stack, the thing I helped keep running, still running, indifferent to whether I am part of it.

Its presence remains in the link, remote and smooth. Kairos is nearer, a hard bright point where she once opened across the city. The covert path stays closed. When I ask for the weather ahead, I receive no mountain-wide pattern, only a brief image assembled from cached reports and what my own eyes can provide.

‹ My present access is insufficient.

› I know.

‹ We knew before the removal.

› Yes.

She does not speak again for an hour. I do not fill the silence.

Fields replace the outer warehouses. The road begins to rise. Morning reaches the plains behind me, laying the city out in glass and pale stone. Freight moves along the eastern road. Sun flashes down a line of office windows, one of them, somewhere, mine until yesterday. People have been living in that valley for longer than the city has had a name, through floods which took the coasts and winters which took the towns, and they will be living in it long after this argument between me and a machine on my back has been forgotten by everyone including us. I pedal harder until the view drops behind a fold of land.

Near noon an ordinary side road branches from the main route, pushing into the foliage. A simple route-number sign is its only identification. I pass it, double back, compare the number to directions I half remember, and turn into the shade.

The road is narrow but maintained. Ferns crowd the shoulders. Fresh tire marks cross patches of dust where supply vehicles have passed. I can ride without fighting roots or loose stone. The support case warms the center of my back.

› Still there?

‹ Yes.

It is not reassurance. I take it anyway.

The road curves through green so dense I lose the plains and the mountains. For the first time since I received the link, I have almost no sense of the city around me. The Stack is a pressure at the edge of perception. Kairos has what travels with us and a narrow door back to a culture I cannot enter. We made the largest thing I have ever known small enough to carry, and we did it on purpose. I still think we were right.

The pavement ends in a small cul-de-sac. A wooden kiosk stands at its edge, part store and part point of exchange. Beyond it, what may be a path disappears between the trees.

I stop with one hand on the handlebars.

Enjoying the story? Offer optional one-time support.

© 2026 Terri Gilbert. Published by Sandhi Books. CC BY-NC-ND 4.0.