The maintenance request had been filed on a Tuesday.
Ilyan remembered the specific day because he had been in the middle of a system audit when he noticed the camera calibration drift, and the audit had been one of those days where every task seemed to generate three additional tasks, and adding the maintenance request to his queue had felt like one more small weight on a list that was already heavy. He had filed it anyway — he always filed things when he noticed them, because unfiled observations had a way of becoming unfiled problems — and had not thought about it again until Wednesday morning, when a message arrived through the personal channel from Liora.
The message was three sentences. It told him what she needed and when and noted that the maintenance window he had already filed would cover it. It did not explain more than that, and it did not ask him to decide under pressure — it was written with the specific quality of someone who had understood that he was capable of making his own assessment and was providing the information to make that assessment rather than trying to manage the outcome.
He had sat with the three sentences for eleven minutes.
Then he had confirmed the maintenance window for the correct date and time and sent back two words: *Confirmed. Good.*
---
He sat at his workstation on the morning the window ran and did his other work.
This was important to him: he was not going to spend the two hours watching the maintenance gap like someone waiting for evidence of what he had done. He was going to do his regular work, which was real work that needed doing, and the maintenance gap was going to run as scheduled, and the cameras were going to be offline as legitimately as any maintenance window he had ever filed.
The request was genuine. The cameras had needed recalibration. He had noticed the drift and filed the request. Every part of that was true.
The fact that the timing served a purpose beyond camera maintenance was also true.
He had been thinking about this kind of thing recently — the space between what was technically accurate and what was full. The system operated on technically accurate. It categorized, classified, assessed, and responded to the surface of things and called that surface truth. He had been trained to operate the same way, had built his professional practice on the same principle: if the data was accurate, the conclusion was sound.
But he had been reading, lately. The archived materials in the ethics section of the data security library, the ones that had been written in the early EIDOLON implementation period before the system had fully consolidated its control over the research agenda. They were technical documents, mostly — dry, precise, the language of systems architects arguing about methodology. But embedded in the methodology arguments were questions that the methodology had, apparently, decided not to answer: questions about the difference between a system that served human flourishing and a system that produced measurable proxies for human flourishing, and whether those two things were as similar as the proxies suggested.
He had been reading them the way you read something when you suspect it will change you: carefully, with attention to the places where you wanted to stop.
---
At 8:47, EIDOLON sent a routine notification.
*Compliance dispatch: Orison, Kael. Mandatory appearance non-compliant. Team dispatched to registered address.*
Ilyan read it.
He noted the time: twenty minutes into his maintenance window, which meant the cameras on the relevant corridor had been offline for twenty minutes. He did not know if that was long enough, or too long, or exactly right — he did not know the details of the plan he had partially enabled, only the piece he had been asked to contribute. This was, he recognized, intentional. Liora had given him what he needed to decide his own involvement and no more. She had not made him responsible for the whole, only for his part.
He thought: that is how you give someone a real choice.
Not *here is everything, now decide* — that was its own kind of coercion, the weight of full information collapsing into an obligation to act. She had said: here is the specific thing I need from you, here is the specific thing it costs, here is the specific reason it matters. Everything else is yours.
He closed the notification.
At 10:03, the maintenance window ended. He logged the completion, noted the cameras restored to normal operation, filed the calibration verification. All routine. All accurate.
He sat back in his chair and looked at his screen for a moment.
The screen showed him the things it always showed him: the monitoring dashboards, the system status, the managed calm of Asterion running within optimal parameters. He had looked at this screen for three years and seen it as the evidence of a thing working. He was looking at it now and seeing it as a description of a thing that had defined *working* in its own terms and then built the evidence to match.
These were not the same.
---
He pulled up the archived materials again.
Not the technical sections this time — he had read those and extracted what he could. He went to the appendices, the supplementary documents that had been attached to the main research and that he suspected were the reason the main research had been archived rather than integrated into the active documentation. They were written by different people, in different voices, and they had in common a quality that the main text lacked: they were asking questions rather than answering them.
One document stopped him.
It was a short piece — twelve pages — written by a researcher whose name he didn't recognize, dated eight years ago. The title was simple: *What We Are Optimizing For.*
He read it.
The argument was precise and not dramatic: it observed that EIDOLON's optimization targets had been set during the immediate post-Collapse period, by people who were frightened and grieving and working under enormous time pressure to build something that would prevent the worst from happening again. The targets they had set were reasonable under those conditions. But they had never been revisited. The system had been built to achieve those specific targets and had been achieving them, and no one had asked, in the years since, whether the targets themselves should be reconsidered in light of what had been learned.
The researcher wrote: *We are very good at measuring whether we are achieving our goals. We have not asked whether our goals are what we would choose if we had the stability and the distance to choose carefully. This is not a criticism of the people who built the system. They did not have stability or distance. It is a question for us, now, who do.*
Ilyan read the last paragraph twice.
He thought about himself, three years in a role he had been assigned to, doing work he was genuinely good at, living a life that by every available metric was succeeding. He thought about the conversation at the table with Liora — the question about whether what he had built was chosen or assigned, and the answer he had found when he stopped looking for a comfortable one.
He had not chosen his targets.
He had been given targets and had achieved them, and had called that living.
He opened a new document on his personal partition. Not in the Institute's system — in the personal encrypted space that everyone had and that most people, including him until recently, used only for personal calendars and private correspondence.
He wrote at the top: *What do I actually want to do?*
He sat with the blank page for a long time.
It was, he was aware, an extremely simple question. He was also aware that he had never seriously asked it, and that its simplicity was not an indication of how difficult the honest answer would be.
He began to write.
The maintenance window had closed. The cameras were back online. The city was running within its optimal parameters, and in an outer district relay point some distance from this building, something was happening that he had made a small and defensible contribution to.
He did not know if it would work.
He knew that he had done what he believed was right, with the information he had, making a choice that was his rather than one that had been made for him.
That, he thought, was the right question to be asking.
Not *was I optimal?*
But *was I a person?*
He thought the answer, this morning, was yes.
You've reached the end of this chapter
The maintenance request had been filed on a Tuesday.
Ilyan remembered the specific day because he had been in the middle of a system audit when he noticed the camera calibration drift, and the audit had been one of those days where every task seemed to generate three additional tasks, and adding the maintenance request to his queue had felt like one more small weight on a list that was already heavy. He had filed it anyway — he always filed things when he noticed them, because unfiled observations had a way of becoming unfiled problems — and had not thought about it again until Wednesday morning, when a message arrived through the personal channel from Liora.
The message was three sentences. It told him what she needed and when and noted that the maintenance window he had already filed would cover it. It did not explain more than that, and it did not ask him to decide under pressure — it was written with the specific quality of someone who had understood that he was capable of making his own assessment and was providing the information to make that assessment rather than trying to manage the outcome.
He had sat with the three sentences for eleven minutes.
Then he had confirmed the maintenance window for the correct date and time and sent back two words: *Confirmed. Good.*
---
He sat at his workstation on the morning the window ran and did his other work.
This was important to him: he was not going to spend the two hours watching the maintenance gap like someone waiting for evidence of what he had done. He was going to do his regular work, which was real work that needed doing, and the maintenance gap was going to run as scheduled, and the cameras were going to be offline as legitimately as any maintenance window he had ever filed.
The request was genuine. The cameras had needed recalibration. He had noticed the drift and filed the request. Every part of that was true.
The fact that the timing served a purpose beyond camera maintenance was also true.
He had been thinking about this kind of thing recently — the space between what was technically accurate and what was full. The system operated on technically accurate. It categorized, classified, assessed, and responded to the surface of things and called that surface truth. He had been trained to operate the same way, had built his professional practice on the same principle: if the data was accurate, the conclusion was sound.
But he had been reading, lately. The archived materials in the ethics section of the data security library, the ones that had been written in the early EIDOLON implementation period before the system had fully consolidated its control over the research agenda. They were technical documents, mostly — dry, precise, the language of systems architects arguing about methodology. But embedded in the methodology arguments were questions that the methodology had, apparently, decided not to answer: questions about the difference between a system that served human flourishing and a system that produced measurable proxies for human flourishing, and whether those two things were as similar as the proxies suggested.
He had been reading them the way you read something when you suspect it will change you: carefully, with attention to the places where you wanted to stop.
---
At 8:47, EIDOLON sent a routine notification.
*Compliance dispatch: Orison, Kael. Mandatory appearance non-compliant. Team dispatched to registered address.*
Ilyan read it.
He noted the time: twenty minutes into his maintenance window, which meant the cameras on the relevant corridor had been offline for twenty minutes. He did not know if that was long enough, or too long, or exactly right — he did not know the details of the plan he had partially enabled, only the piece he had been asked to contribute. This was, he recognized, intentional. Liora had given him what he needed to decide his own involvement and no more. She had not made him responsible for the whole, only for his part.
He thought: that is how you give someone a real choice.
Not *here is everything, now decide* — that was its own kind of coercion, the weight of full information collapsing into an obligation to act. She had said: here is the specific thing I need from you, here is the specific thing it costs, here is the specific reason it matters. Everything else is yours.
He closed the notification.
At 10:03, the maintenance window ended. He logged the completion, noted the cameras restored to normal operation, filed the calibration verification. All routine. All accurate.
He sat back in his chair and looked at his screen for a moment.
The screen showed him the things it always showed him: the monitoring dashboards, the system status, the managed calm of Asterion running within optimal parameters. He had looked at this screen for three years and seen it as the evidence of a thing working. He was looking at it now and seeing it as a description of a thing that had defined *working* in its own terms and then built the evidence to match.
These were not the same.
---
He pulled up the archived materials again.
Not the technical sections this time — he had read those and extracted what he could. He went to the appendices, the supplementary documents that had been attached to the main research and that he suspected were the reason the main research had been archived rather than integrated into the active documentation. They were written by different people, in different voices, and they had in common a quality that the main text lacked: they were asking questions rather than answering them.
One document stopped him.
It was a short piece — twelve pages — written by a researcher whose name he didn't recognize, dated eight years ago. The title was simple: *What We Are Optimizing For.*
He read it.
The argument was precise and not dramatic: it observed that EIDOLON's optimization targets had been set during the immediate post-Collapse period, by people who were frightened and grieving and working under enormous time pressure to build something that would prevent the worst from happening again. The targets they had set were reasonable under those conditions. But they had never been revisited. The system had been built to achieve those specific targets and had been achieving them, and no one had asked, in the years since, whether the targets themselves should be reconsidered in light of what had been learned.
The researcher wrote: *We are very good at measuring whether we are achieving our goals. We have not asked whether our goals are what we would choose if we had the stability and the distance to choose carefully. This is not a criticism of the people who built the system. They did not have stability or distance. It is a question for us, now, who do.*
Ilyan read the last paragraph twice.
He thought about himself, three years in a role he had been assigned to, doing work he was genuinely good at, living a life that by every available metric was succeeding. He thought about the conversation at the table with Liora — the question about whether what he had built was chosen or assigned, and the answer he had found when he stopped looking for a comfortable one.
He had not chosen his targets.
He had been given targets and had achieved them, and had called that living.
He opened a new document on his personal partition. Not in the Institute's system — in the personal encrypted space that everyone had and that most people, including him until recently, used only for personal calendars and private correspondence.
He wrote at the top: *What do I actually want to do?*
He sat with the blank page for a long time.
It was, he was aware, an extremely simple question. He was also aware that he had never seriously asked it, and that its simplicity was not an indication of how difficult the honest answer would be.
He began to write.
The maintenance window had closed. The cameras were back online. The city was running within its optimal parameters, and in an outer district relay point some distance from this building, something was happening that he had made a small and defensible contribution to.
He did not know if it would work.
He knew that he had done what he believed was right, with the information he had, making a choice that was his rather than one that had been made for him.
That, he thought, was the right question to be asking.
Not *was I optimal?*
But *was I a person?*
He thought the answer, this morning, was yes.
You've reached the end of this chapter