Chương 35: Skill Evolution

Sable listened while he laid it out. The gap outside the city was quiet at this hour. Red was somewhere to his left, standing the way it stood at night, not sleeping, not moving. The city hummed on the other side of the wall — two million registered people and all their registered things, generating the constant low noise of an active System at scale. Out here was different. The old ground didn't generate much.

'Walk me through the definition again,' Sable said.

'[Improvised Solution] — grey rarity, unique, converts environmental elements into usable tools.' He had it memorized.

'The System gave me that skill in my fourth day here because I used terrain to survive a fight instead of a weapon. The skill formalized what I was already doing.'

'And you've been stretching it since.'

'Every time I use it on a System process, I'm treating the process as the environmental element. The tool I'm producing is the read — the information about what the process is doing.' He looked at his hands in the dark, which was something he did when he was thinking.

'But the skill's definition hasn't caught up with how I've been using it. There's a gap between what I do with it and what the System thinks it does.'

'Skills evolve when that gap closes,' Sable said.

'When the usage pattern overrides the original definition.' She paused.

'The question is whether you can close the gap deliberately or whether you have to wait for the System to close it on its own.'

'I'm not waiting for the System to close it,' Kaito said.

'I'm closing it myself.' Red spoke from the dark.

'People who try to direct their own skill evolutions generally get AXIOM's attention.'

'I know.'

'You already have AXIOM's attention,' Red said.

'I'm noting the risk as a formality.' Kaito almost smiled. Almost.

'What I need is a broken process to work with. Something small enough that using the skill on it won't flag immediately. Something the System would expect me to interact with anyway.' He looked at the ground.

'There's one about twelve feet north of where you're standing. There's been a System registration corruption in this patch of ground for — I don't know how long. The original land registration has a gap where two property boundaries were supposed to meet and didn't. AXIOM's tried to reconcile it a dozen times over the years. It can't. The corruption's in the underlying data structure.' Red looked at the ground where he'd indicated.

'That's been there since before the city,' it said.

'I know. Which is why the System has low expectations of me fixing it.' He moved closer to it.

'I'm not fixing it. I'm using the skill on it. I'm pushing the skill toward what I want it to do, and I'm going to do it repeatedly until the usage definition updates.'

'How many times,' Sable said.

'I don't know yet. As many as it takes.' He used [Improvised Solution] on the gap in the land registration. The skill read the corruption and produced a tool — a temporary patch that bridged the data gap for about three seconds before the underlying inconsistency reasserted itself and the bridge collapsed. Standard skill behavior. He'd done this before with similar processes. He did it again. And again. Each time, he pushed the intent of the skill slightly further. Not toward "convert this into a tool."

Toward "fix this." Not permanently. Just — fix it, hold the fix, let the process run clean for the duration of the fix. He thought about what the difference was between a bridge and a repair. A bridge covered the gap. A repair closed it. The skill couldn't close the gap. It wasn't designed for that. But it could hold the bridge.

'You're fighting the skill's original intent,' Sable said, between iterations.

'The System assigned "converts environmental elements into tools" as the definition. You're trying to shift "fixes broken processes" into that slot instead.'

'They're not that different,' Kaito said.

'A fixed process is a tool. It's a process that works instead of one that doesn't.'

'The System doesn't think in analogies,' she said.

'No,' he agreed.

'But skill evolution does. Evolution happens when usage patterns accumulate enough to override the original definition. I'm accumulating the right pattern.' He ran it again.

'How many iterations do you think it takes.'

'I have no reference point. This isn't something that's been done before.'

'Estimate.'

'Fifteen to thirty. If you can hold the intent consistent enough that the System reads the pattern as distinct from the original behavior rather than a variant of it.' A pause.

'The problem is that the System is going to resist the reclassification. AXIOM assigns skill definitions for a reason. If it assigned [Improvised Solution] as "converts environmental elements," it didn't want "fixes System processes" to be an option.' Stolen content alert: this content belongs on Royal Road. Report any occurrences.

'That's not my problem,' Kaito said.

'That's AXIOM's problem.' He pushed. Red settled into the wall. The night moved. Kaito lost track of how many iterations he'd run — twelve, maybe fifteen — when Sable said, 'The skill's internal definition is shifting. I can feel it in how you're using it. The System is noticing the usage pattern.'

'Good,' he said.

'It's going to resist. Skill evolutions that go against AXIOM's assigned direction tend to get flagged.'

'Let it flag.' He ran it again. The bridge held for four seconds this time instead of three. Again. Five seconds. He'd been doing this for two hours. The sky had started going lighter at the edges — the first sun coming up — when something in the skill's values changed. He felt it the way he felt the Iron Cathedral's trap mechanisms: a shift in the underlying values, something clicking into a new configuration. The bridge didn't collapse.

He held the fix and it stayed, and the skill's definition recalculated around what he'd just done. A notification fired. [Skill evolved: [Improvised Solution] → [System Patch]][System Patch — Green Rarity — Unique: Temporarily repair a broken System process within a radius of twenty meters. Duration scales with process severity. Fixed processes revert to base state after duration expires. This skill is not sanctioned.] He read it twice. The last line was new.

He'd never seen "This skill is not sanctioned" on a notification before.

'Sable,' he said.

'I see it.'

'What does "not sanctioned" mean.'

'It means AXIOM didn't approve the evolution. The System generated the skill based on your usage pattern — that process is partly automated — but AXIOM didn't authorize it, and the System logged that discrepancy.' She was quiet for a moment.

'The skill works. You have it.

"Not sanctioned" is the System noting that AXIOM would have preferred it not exist.' He tested it. Used [System Patch] on the land registration gap and held it — held it for twelve seconds before the underlying structure reasserted itself and the patch expired. The difference from [Improvised Solution] was immediate. [Improvised Solution] had produced a tool. [System Patch] produced a repair. The distinction was small but it was real.

The gap didn't just have a bridge over it — it was, for twelve seconds, not a gap. He looked at what he was holding.

'This could work on the pit registration,' he said.

'In theory,' Sable said.

'In practice, the pit's chain is orders of magnitude more complex than a land boundary dispute. The severity is higher, which means the duration would be longer — but the System would also flag a repair to the pit's registration as significant. It's not a forgotten boundary.' She paused.

'Don't use it on the pits yet. Test it on something larger than this first. Work up.'

'Yes.' He ran the patch once more, watching the duration. Thirteen seconds.

'But it's there.'

'It's there,' she agreed.

'Sleep. Then test it bigger. Then the pits.'

'In that order,' he said.

'In that order. Sleep first. You've been up all night and AXIOM's attention is—' And that was when the second notification arrived. Not a System notification. Something different. The bracket format was the same. The text was different in a way he couldn't immediately name — until he looked at the color. Standard notifications were white on dark. The skill evolution had been green. This one was dark blue. A specific, deliberate dark blue that he hadn't seen before and that made something in his chest go quiet.

'Sable,' he said. She didn't answer immediately. That was unusual.

'Sable.'

'I see it.' Her voice was careful. Not afraid — Sable didn't have fear responses in the standard sense — but careful in the way someone was careful when they recognized something significant.

'What color is that.'

'Dark blue,' she said.

'In ten thousand years I have encountered it in System logs exactly once. Eight hundred years ago. AXIOM issued a dark blue notification when it discovered a specific piece of Precursor infrastructure that shouldn't have still been operating.' A pause.

'Dark blue means AXIOM is personally authoring the message. Not the System generating a notification. AXIOM itself, sitting down to write something and send it.' He was very still.

'The System generates notifications automatically,' she continued.

'AXIOM manages the System but doesn't typically author individual messages by hand. It would be like the person who designed a machine choosing to write a personal note instead of letting the machine print one. It only does that when something is significant enough to require its direct attention and a direct response.' She paused.

'You have its direct attention.' He read the notification. [That skill should not exist. Explain.] He looked at those six words for a long time. Red had turned. It was looking at him from the wall. It had read his face, the way it always read his face, and it knew something had changed.

'Is this the part where you lie to it,' Red said.

'Yes,' Kaito said.

'Are you good at lying.' He thought about six years of telling publishers the game was nearly finished when it wasn't, and telling his team the money was fine when it wasn't, and telling himself that it didn't matter whether the game shipped or not when it did.

'I have some practice,' he said.

'The god is not a publisher,' Red said.

'It knows the difference between a lie that addresses the question and a lie that avoids it. Address the question. Give it something real, just not the real thing.' Kaito looked at the notification again. Six words. He had the shape of an answer already — something true about how the skill had evolved, technically accurate, that didn't mention what he'd been planning to use it for. A game developer thing. A studio thing. Give them what they asked for and hide what you're protecting inside the accurate parts.

'I know,' he said to Red. Red turned back to the wall. He looked at the dark blue notification, at those six words, and started thinking about how you said something true enough to believe and false enough to survive when the thing asking was the god that ran the world.