Lian's Proposal
In which our protagonist accepts a student formally, and is unexpectedly moved by it.
Lian formally became his apprentice on the morning of day two of the aquifer project, and the way she did it was, in a small way, a kind of declaration of war against every assumption Kenji had about how teenagers ask for things.
She did not ask. She arrived at the drilling site at dawn, in a clean apprentice's robe she had clearly pressed the night before, with a small leather notebook, a satchel of components, and an expression of such determined seriousness that the foreman of the volunteer crew, a man twice her age, stepped out of her way without being asked.
"I have decided," she said.
"Decided what?"
"To be your apprentice. Formally. With a contract. The academy requires it if I am to study under a master who is not registered with them."
Kenji, who had been holding a half-eaten piece of bread and was not, in the dry language of the system in his head, in any way prepared to be consulted, said: "I am not registered with the academy."
"I know. That is the point. The academy does not teach what you teach. If I want to learn it, I have to leave the academy and apprentice to you instead. The contract is a way of making that legitimate."
She held out a piece of paper. Kenji looked at it. It was a beautifully written apprenticeship contract, in the formal style of the academy, with blank spaces for names, terms, and obligations. Lian had clearly been working on it for a while. The handwriting was careful. The clauses were specific. The compensation was set at a rate that suggested Lian had done more research than most of Kenji's old job candidates.
"Tell me what this means," Kenji said, "in plain language."
"It means I am your student. You teach me. I learn. The academy does not own me anymore. I do. And you do, a little. For the term of the contract, which I propose as three years."
"Three years," Kenji repeated.
"It is a standard term. I checked."
He looked at her. Seventeen years old, academy-trained, smart enough to find a strange mage in a strange town and decide, on her own, that what he knew was worth leaving the institution for. Brave enough to show up at a drilling site in a clean robe and hand him a contract before he had finished his breakfast. He thought about his own seventeen-year-old self, sitting in a high school classroom in Tokyo, deciding that he wanted to be a programmer, and how that decision had shaped the rest of his life.
[Compiler query: should the developer accept this contract?]
[Compiler note: trust assessment pending. Recommend: gather more data before agreeing to long-term obligation.]
[Compiler note: this is the third contract the developer has been offered in this world. None of them have been standard.]
The system was, in a small way, protecting him. The system was, in the driest possible language, asking if he had read the fine print.
"Okay," he said. "Three years. But I have conditions."
Lian's face fell slightly. "What conditions?"
"First, you keep your logic notebook. You document everything. We do not learn by rote. We learn by writing things down and looking at them again."
"I already do that."
"Good. Second, when you are better than me at something, you tell me. I am not a master. I am a programmer who happened to be isekai'd. I do not know everything."
"That is two conditions. Is there a third?"
"Yes. The third condition is that you go home and rest. You have been up since before dawn, you have a contract in your hand, and we have a drilling site to run. I cannot have my apprentice fainting on day one."
Lian smiled. It was the first time Kenji had seen her smile without the nervous edge of a person who was not sure if she was being taken seriously. It was a real smile, the kind that came from being seen and understood, and it made her look, for a moment, exactly her age.
"I accept," she said.
"Good. Now go home. Come back after lunch. Bring a hard hat."
She went. Kenji watched her leave, and felt, very quietly, the weight of being responsible for another person's education. It was a familiar weight. He had been a tech lead once. He had trained junior engineers. He knew what it was like to have someone's career in his hands.
He also knew, from experience, that the best thing he could do was treat the apprentice as a colleague who was still learning, not a subordinate who was waiting to be told what to do. So he did.
By the end of day two, Lian was running the spell calibration for the drilling team. By the end of day three, she had caught a flaw in the spell's stability parameters that would have caused a minor collapse on day four. By the end of day four, the engineers were deferring to her on spell-related questions, which was not something Kenji had expected and was very satisfying to watch.
He had, in other words, hired a colleague. The system had noticed. The system, in the dry language of a debug overlay that has seen junior developers before, was, in a small way, ahead of him.
[Skill calibration: 100% within tolerance]
[Stability parameter flaw: caught by apprentice at 18:42 local time]
[Compiler note: without the apprentice, the spell would have collapsed at 14:00 tomorrow.]
[Compiler note: the project is on schedule because of the apprentice. The developer is, in a small way, learning.]
The project was on schedule because of her. The aquifer was saving the town because of her. The town was alive because of her. And she had been an apprentice for less than a week, and she was, in the dry language of the system, already more useful than most of the engineers he had hired in his old life.
She was, he realized, going to be better than him at this. Not yet. Not by a long way. But the trajectory was clear, the way a trajectory is clear when you have watched enough of them, and he was going to have to step back, in time, the way his own mentor had stepped back, and let her take the lead.
It was, he thought, exactly the right kind of problem to have.
The flaw she had caught was, in the driest possible language, a bug. A line in the spell definition that should have been 0.87 and was, in the original draft Kenji had written at three in the morning, 0.78. Nine hundredths of a difference. The kind of difference that does not show up in the first few iterations of testing, but does show up, very reliably, on the day the spell is supposed to do its real work, when the mana load is at peak and the parameters are at limit and the entire system is being asked to perform in production.
[Compiler note: the apprentice caught a 0.09 deviation. The system approves.]
[Compiler note: the developer is, in a small way, learning to delegate.]
The system was, in a small way, a teacher. The system was, in a small way, ahead of him. And Lian, who had caught the deviation by reading the spell definition out loud the way some people read poetry, was going to keep catching them, in subjects Kenji had not yet written the spell definitions for, in languages Kenji had not yet learned, in systems Kenji had not yet imagined.
He was going to need her, in ways he could not see yet, when the documentation he had not yet written became the curriculum of a school that did not yet exist, in a country that did not yet know it needed one. He did not know that. He knew only that the well was filling, the town was alive, and his apprentice had caught a bug he would have shipped.
That night, he sat in his room at the guild hall, with Pip orbiting his head and the contract in his pocket, and he thought about the through-line. The phrase that had become, somehow, the spine of his life in this world. Any sufficiently well-defined problem is solvable.
Lian was, he decided, going to be the one who wrote the next chapter. He was going to be the one who made sure she had the room to do it.
Pip pulsed, soft, in a tone that was, in a small way, ahead of him. The pulse felt like: "Good choice."
Kenji sent back, in the language he and Pip had built together: "Yeah. I think so too."
Outside, the well ran. The town slept. And somewhere to the south, in a small grey tent, the cultist was still writing, and the notebook was filling, and the word at the top of the page was not just Oakhaven anymore. The word was now, in the careful handwriting of a person who had been told to watch, the apprentice.