Rank III

The notification came at three in the morning.

I was at the kitchen table with the lamp turned low, running the column of numbers I'd been running since supper: resort population, projected food requirement through February, the gap between what Breckett's supply cache covered and what sixty-plus people would need after that, how hungry a well-organized man gets before organized stops being the operative description. The arithmetic wasn't generous. It was one of the reasons I'd known the proposal visits weren't the end of anything.

The System mark on the back of my hand pulsed twice, warm and deliberate, and then the interface unfolded in my peripheral vision with the particular weight of something significant.

[SYSTEM NOTIFICATION]
PARALLEL FORM — PRIMARY HOST: NOLAN LOCKE
RANK ADVANCEMENT: II → III

Rank III threshold achieved through sustained ability deployment, tactical integration, and multi-vector concurrent operation.

Physical baseline update in progress. Allow 8-12 seconds. Caloric deficit will follow.

It started in the spine, the way the first rank-up had started in the muscles — not pain exactly, but a deep structural adjustment, the sensation of something being recalibrated at a level below conscious access. My back straightened without my asking it to. Both hands, the real ones, pressed flat on the table and I sat with it for the eight seconds it took, breathing slowly, feeling each vertebra settle into a marginally improved relationship with the ones adjacent to it. My vision sharpened by a degree I could actually measure: the grain of the table wood came into finer resolution, the lamp flame's edge stopped blurring at the periphery.

Then it was done and I was hungry in a way that the word hungry did not adequately address. I got up and ate cold cornbread and a full mason jar of preserved green beans standing at the counter in the dark, and then I sat back down and opened the full notification.

RANK III — PARALLEL FORM
HOST STATS UPDATE:

Strength: 14 → 17
Endurance: 15 → 19
Reflex Response: 12 → 16
Sensory Acuity: 11 → 15
Parallel Cohesion: 18 → 23

PARALLEL FORM — ABILITY PARAMETER UPDATES:

Operational Range: Extended from 0.3 miles (degraded) to 0.9 miles (full cohesion), 1.4 miles (partial, autopilot-capable).

Sensory Bridge: Now selectable. Host may elect to share specific sensory input (visual, auditory, tactile) between primary and secondary body with conscious control. Default remains independent. Full sensory sharing requires active focus.

Secondary Body Durability: Threshold increased. Damage absorption before function impairment increased by approximately 40%.

KNOWLEDGE POINTS AWARDED: 4

Current KP balance: 4

KP expenditures available: System queries, ability parameter clarification, world-state intelligence (limited).

I sat with the range figure for a moment. Nine-tenths of a mile at full cohesion was a different tactical picture than the quarter-mile threshold I'd been managing around. It meant Poppy could work the entire farm perimeter — all of it, from the north fence to the creek boundary — while I stayed in the house. It meant the resort's back gate was in range from the county road junction if I positioned correctly. It meant the Pilgrim Ridge observation post and the resort itself were reachable from intermediate ground I hadn't previously had to consider.

The sensory bridge was the more interesting development. I'd been sharing visual input with Poppy since the first week — the tuning-two-radios sensation, one signal louder than the other, switching as needed. What the notification described was different: deliberate, selective, real-time. The ability to feel what Poppy felt, not just see what it saw. Or to let Poppy experience my sensory state. The implications ran in several directions at once and I needed to test the actual mechanics before drawing conclusions from a description in a System interface.

Four Knowledge Points. The most I'd had at once. I looked at the balance and thought about what I wanted to know badly enough to spend on.

The first question wrote itself. I'd been sitting with the Encounter notation since it appeared after the rank-up at the rail-trail community, and the two words had been sitting in the lower section of the interface with the patience of something that knew it would eventually be relevant. Encounter: an undefined stress event it will generate or wait for. I hadn't asked because I hadn't been ready to hear the answer clearly. Now the KP were there and the farm was asleep and three in the morning was as good a time as any for information you didn't want to receive with witnesses.

I spent one KP.

[SYSTEM QUERY — 1 KP]
Q: What constitutes an Encounter event for Parallel Form progression? How is it generated?

A: Encounter events are progression-accelerant scenarios calibrated to current ability tier. They may emerge from pre-existing environmental conditions (hostile actors, structural crises, natural threats) or may be introduced by System-generated incursion events into the host's operational proximity. The System does not create the scenario from void; it routes existing incursion events toward hosts whose progression metrics indicate readiness. The Encounter is not punitive. It is selective.

At Rank III, the next Encounter threshold requires a scenario of sufficient scope and duration to produce measurable ability strain under sustained dual-body operation. Single-engagement incidents of the type that advanced Rank II are insufficient.

I read that three times.

The System did not create the scenario from void. It routed existing incursion events toward hosts whose progression metrics indicated readiness. Which meant the creatures coming through the eastern field and the southern perimeter weren't random distribution. Something was moving through the world in patterns that the System understood and influenced, and the System was reading my metrics — whatever those were — and deciding when I was ready for a larger problem, and then ensuring that larger problem arrived.

Not punitive. Selective.

I sat back in the chair. The lamp flame held its small steady shape. Through Poppy's position at the barn corner, the farm was dark and cold and completely quiet, the county road empty in both directions.

The System had been an active participant since the first day, and I'd known that academically — the rank-up mechanics, the KP structure, the progression curve — but there's a version of knowing something that doesn't fully connect until a specific sentence makes it specific. It routes existing incursion events toward hosts whose progression metrics indicate readiness. The events I'd been treating as environmental features of a changed world had a directing intelligence behind their placement. Not full authorship, but curation. Something had looked at my numbers and looked at the available threat inventory and made a match.

I spent the second KP.

[SYSTEM QUERY — 1 KP]
Q: What does the Rank III Encounter require, and what is the projected timeline?

A: Rank III Encounter will involve a threat requiring concurrent dual-body tactical engagement of a duration and intensity sufficient to stress the Parallel Cohesion parameter under real conditions. The scenario must not be resolvable by a single body acting alone.

Timeline: indeterminate. The System routes the appropriate incursion event when calibration conditions are met. Current local mana density: 8.3%. Routing occurs at a density threshold specific to the host's tier. Host should expect an Encounter within the current operational period.

Current operational period is defined as: ongoing.

Ongoing. Within the ongoing operational period, which meant no bracket and no warning other than the fact that I now knew it was coming. The System was telling me this the same way a decent NCO gave you the pre-mission brief: here is the shape of what's coming, not the exact time, because the exact time doesn't help you and the general shape does.

I respected the logic. I didn't enjoy it.

I closed the notification and sat with the remaining two KP and thought about what else I wanted to buy. The sensory bridge mechanic needed a practical explanation — how to activate it, what the cost was in terms of cognitive load, whether it could be used passively or only with deliberate attention. That was worth one KP, and useful before the Encounter rather than after.

[SYSTEM QUERY — 1 KP]
Q: How is the Rank III sensory bridge activated and managed? What are its operational limits?

A: Sensory bridge activation requires brief intentional focus on the specific sense to be shared (visual, auditory, tactile, thermal). Direct the attention inward toward the secondary body's sensory state and intend the bridge. Activation time: 2-4 seconds. Deactivation is immediate.

Cognitive load: Moderate. Full sensory sharing across all channels simultaneously is possible but degrades other executive functions. Selective sharing (e.g., visual only) incurs minimal load.

Operational limits: Sensory bridge accuracy degrades proportionally with distance beyond 0.5 miles. At maximum operational range (1.4 miles), bridge is unreliable. Bridge does not affect autopilot function — secondary body continues assigned parameters during sharing.

Note: The secondary body experiences the primary host's sensory state reciprocally when the bridge is active, unless explicitly suppressed by the host.

That last line stopped me.

Unless explicitly suppressed. The default, when I opened the bridge, was bidirectional. Poppy would experience what I experienced. I'd been thinking of this as a monitoring tool, another angle on the world, and the system was reminding me that the duplicate on the other end of the connection was experiencing something, and that something was now reflexive unless I specifically chose otherwise.

I didn't examine that too closely. I had enough to examine.

One KP left. I thought about it for a long moment and then spent it on the question I'd been deferring since the first rank-up told me the duplicate could theoretically operate for decades.

[SYSTEM QUERY — 1 KP]
Q: Does the secondary body's continued existence affect the primary host's progression, lifespan, or ability function if the primary host is killed?

A: In the event of primary host death, the secondary body enters an indeterminate state. It retains all established operational capacity but loses progression link to the System. It will not rank up. It will not receive further KP or ability updates. It will continue to function indefinitely under the parameters established at the time of primary host death.

The secondary body cannot initiate a new primary host link. It is not transferable.

In the event of secondary body destruction, the primary host experiences temporary ability disruption (estimated 72-96 hours) before the secondary body regenerates.

I read it twice and then closed the interface.

The farm was quiet in the cold. Poppy stood at the barn corner with the patient stillness of something that had been told to stand there and had no other context. The sensory bridge was closed, which meant the duplicate was receiving no input from me — no pressure of my hands on the table, no lamplight, no awareness of the kitchen or the notebook or the knowledge that I'd just learned something about its situation that it wouldn't know unless I opened the bridge and chose to pass it.

A secondary body that loses progression link but continues to function indefinitely. Frozen at whatever parameters existed at the moment of primary host death. Not dead, not free, not advancing. The specific quality of that outcome took a moment to sit with properly.

I was alive and intended to remain so, which made the question academic in the practical sense. But the System had a way of making abstract things concrete on its own schedule, and three in the morning after a rank-up notification was apparently when I did my abstract thinking whether I planned to or not.

I closed the notebook, because there was nothing to add to it that the morning wouldn't clarify.

The Encounter was coming. Within the operational period, which was ongoing. Something the System would route toward me when the local mana density hit whatever threshold corresponded to my tier, and the creatures it would route would require dual-body concurrent engagement that my Cohesion parameter couldn't handle alone. Singular engagement insufficient. Duration and intensity sufficient to create strain. Not resolvable by a single body acting alone.

I looked at the barn corner through Poppy's passive feed, the dark shape of the duplicate in the November cold, and thought about the forty percent durability increase the rank-up had provided, and whether I'd need it.

Thursday was Breckett. The Encounter was afterward, sometime, on the System's schedule. Two different categories of problem on overlapping timelines.

What I was not going to do was tell my mother about the Encounter mechanic.

She'd absorbed the System's existence with the practical equanimity she brought to every changed condition — the same way she'd absorbed the grid going down, the same way she'd absorbed my arrival with two bodies and the explanation of what they were. She updated her model and continued operating. Telling her the System was routing biological threats toward me specifically based on my progression metrics was a different category of information. It was accurate, and it was the kind of accurate that didn't improve her situation to know. She'd ask what could be done about it, and the answer was continue getting better at the ability and be ready, which was what we were already doing, and the loop would close without having added any useful variable.

I made that decision and put it away and didn't revisit it.

The lamp was burning low. I trimmed the wick and sat in the dimmer light and listened to the farm breathe — the creak of the storage barn's north wall in the wind, the distant sound of the creek running below the east field, the rhythmic nothing of a rural property in the deep of the night.

Through the sensory bridge, tentatively, I tried the new mechanic. I focused inward toward the secondary body's sensory state and intended the connection. It took three seconds, closer to the upper end of the System's estimate, and then it opened.

Cold. The barn corner was genuinely cold in a way that my body inside the kitchen wasn't, and the sensation arrived with a specificity I hadn't expected — not a report of cold, but the actual temperature differential, the particular quality of wind on the duplicate's face and the back of its hands, the pressure of gravel under its boots. The night air outside smelled like wet wood and mud and the distant sharpness of the creek. Stars above, the clouds from earlier having thinned, and the county road in both directions empty and pale.

And then, because the bridge was bidirectional by default, Poppy received mine: warmth, the faint smell of lamp oil and woodsmoke and cold cornbread, the grain of the table under my palms, the slight ache in my lower back from three hours in a kitchen chair. The lamplight. The residual pressure of the notebook's spiral binding against my forearm.

I closed the bridge after ten seconds. The duplicate returned to its corner and the cold and the dark, and I sat in the kitchen alone, which was a simpler condition.

The rank notification was still technically open in the lower field of the interface. I let it close.

Four KP spent. One significant ability upgrade. One deeply uncomfortable piece of information about the System's role in my progression. One even more uncomfortable piece of information about what happened to the duplicate in the event of my death, which I was treating as academic and which the System had apparently decided I needed to know anyway.

I turned the lamp down until it was barely a glow and sat in the near-dark and let the night run out at its own pace, the way nights did on farms, quietly and without ceremony.

By five in the morning the kitchen had gone cold enough that I put wood on the stove, and by five-thirty my mother was up and moving in the hall with the particular footstep sequence that meant she'd been awake for a while and was now committing to the day. She came into the kitchen and looked at me and the lamp and the general evidence of a night not spent in the bed, and said nothing about it.

"Rank III," I said.

She filled the kettle. "How's the other one."

"Still standing," I said.

She set the kettle on the stove with the careful placement she gave everything, not gentle exactly, but precise. "You look like you ate something in the night."

"Half the larder."

"Cornbread," she said, looking at the cloth on the counter. "That's what you took."

"It was available."

She looked at me the same way she'd looked at me when I came back from Parris Island, and from Camp Lejeune, and from the two places after that she never fully asked about, the same inventory her hands wanted to run but that she kept in her eyes instead. Whatever she found, she set aside without comment, the way she always did.

"Vera's going to want to know about the range," she said.

"I'll tell her at breakfast," I said.

"She'll want to adjust the patrol circuit."

"She's right that she should," I said.

My mother looked at the kitchen window, which was showing the first gray possibility of dawn, barely a lightening of the dark rather than actual light. The county road was still invisible, the lane end and the reflector post somewhere out there in the early morning black.

"Thursday," she said.

"Yes," I said.

"You're ready."

"For Thursday," I said, because that was the accurate scope of the question.

She understood the limitation without my explaining it. She turned back to the stove and began the morning with the same efficiency she began every morning, and the kitchen warmed slowly around us, and through Poppy's position at the barn corner the first birds were starting their preliminary conversations in the trees along the creek, the tentative back-and-forth of things that had survived the night and were establishing that fact.

I opened the System interface one more time and looked at the Cohesion parameter — 23, up from 18 — and the range figure, and the Encounter notation in the lower field, and then I closed it and got up to help my mother with the morning.

Two days until Thursday. The ability parameters had changed and the threat parameters would change to match them, because the System was not passive and had not been passive since the first day, and the right response to that was the same response it always was: know what you know, plan to what you can plan, and stay functional in the gap between.

Poppy shifted at the barn corner as the light came, one small adjustment of position, the boots on the gravel making almost no sound. The east field was emerging from the dark in long shapes, the fence line, the turned soil of the garden bed, the tree line at the creek bank resolving from a mass into individual trees.

The Encounter was out there somewhere on the System's schedule, routing toward me at a speed I couldn't measure and through terrain I couldn't predict. Not yet. But the range had extended and the durability had increased and the sensory bridge was operational, and the farm stood on familiar ground that I'd known since before I'd known anything else, and the morning was coming whether I was ready for it or not.

I put water on for coffee that wasn't coffee and waited for Vera's footsteps in the hall.