NovelReader · readerNovelReader · readerNovelReader · readerNovelReader · readerNovelReader · readerNovelReader · readerNovelReader · readerNovelReader · readerNovelReader · readerNovelReader · readerNovelReader · readerNovelReader · readerNovelReader · readerNovelReader · readerNovelReader · readerNovelReader · readerNovelReader · readerNovelReader · readerNovelReader · readerNovelReader · readerNovelReader · readerNovelReader · readerNovelReader · readerNovelReader · readerNovelReader · readerNovelReader · readerNovelReader · readerNovelReader · readerNovelReader · readerNovelReader · readerNovelReader · readerNovelReader · readerNovelReader · readerNovelReader · readerNovelReader · readerNovelReader · reader
Reborn Sword Sovereign · Chapter 172
Reborn Sword Sovereign · Chapter 172
Read in
Chapter 172 · 2521 words · 11 min

172: Transitional

January was the new year and February was the spring festival and in between them was the accumulation that the transitional class was building in the session data.

Wenqing sent me the first analysis on January 10.

It was six pages, which was his standard length for things he'd thought about carefully and organized once. The first two pages were data — session logs from December 18 through January 9, tracking the Blade Sovereign transitional class's output signature across different combat contexts. The pattern he'd identified:

The transitional class was not producing different output from the Berserker class in the individual-skill sense. The same skills, the same damage coefficients, the same passive thresholds. The difference was in the aggregate — the way separate skill outputs were combining in the combat log.

"Normal Berserker output," he wrote, "is additive. Skill A + Skill B = A + B. The transitional class's combat log shows a different pattern: Skill A + Skill B = A + B + [x], where [x] is a contextual modifier that doesn't correspond to any documented skill in the Berserker tree or any known class in the game's current release." He'd highlighted the [x] values in three pages of session log excerpts. They appeared consistently, sometimes small, occasionally larger, always following the same correlation pattern.

The modifier wasn't large. Typically 3% to 8% of the combined skill output. But it was consistent across sessions, across different combat contexts, across different formation configurations.

And it was growing.

The January 3rd session showed a 4.2% [x] modifier on average. January 9th showed 5.7%.

*The class is accruing something,* he'd written. *The [x] modifier is the accumulation metric. I don't know the ceiling but the current growth rate suggests it hasn't plateaued. The contextual correlation shows the modifier is higher in formation-context combat than in solo combat — which is consistent with the class's design logic as I understand it from the quest chain data you shared.*

He was tracking the quest chain data. Of course he was. I had sent him a summary of the relevant quest chain structure in November, stripped of the foreknowledge framing, phrased as design logic speculation. He'd taken it seriously, built a model from it, and was now watching the model confirm itself in the data. That was the specific satisfaction of giving Wenqing the right information — he didn't need the full picture to use a piece of it correctly.

At the bottom of the analysis: *If the growth rate is linear, the modifier reaches approximately 100% of combined skill output in 16 weeks from December 18 — approximately April 11. If exponential, earlier. I'll update the model as new data comes in.*

April 11.

The date sat in the planning layer next to the other dates: the CW III registration window in April, the spring seminar schedule, Father's April workshop expansion. All of them running on their own timelines, none of them intersecting in a problematic way. The planning layer wasn't a schedule — it was more like knowing where the walls were in a familiar room. You didn't have to look at them constantly to avoid running into them. You registered them once and moved through the room with that knowledge built into the movement.

***

Suzhou for the spring festival. The same flat, the same canal-street quality of the holiday — the specific mood of Pingjiang Road in the first week of February, when the red lanterns went up and the tourist foot traffic was dense and the shop-front owners navigated the holiday with the practiced ease of people who'd been doing it for decades.

The festival Suzhou was a different city from the ordinary Suzhou — the same streets, the same canal geometry, but with a warmth in the evenings that came from the lanterns and the density of people out at hours they didn't usually occupy. I'd grown up with the spring festival Suzhou. It had its own texture that was separate from the rest of the year, the specific texture of a place that knew how to dress for a particular occasion. The canal at festival time had a different sound than the canal at ordinary time — the foot traffic on the bridges, the lanterns reflecting in the water, the particular acoustic of a city showing its best version of itself to the people who had come to see it.

The guild ran a reduced schedule through the festival week — the three AM sessions continued on the mornings I was in Suzhou, which required the phone's hotspot and the portable setup rather than the campus network. The mobile setup was slower and the interface latency was slightly higher, but the Pioneer's Path had been run on worse connections and the transitional class accrued from session data regardless of the connection quality. Wenqing's January 10 analysis had noted the mobile-session data was statistically indistinguishable from the campus-session data in the modifier accumulation rate.

The modifier was at 14.2% when I arrived in Suzhou January 27.

Father was in the kitchen when I arrived. Not cooking — working on the workshop's instruction manuals at the kitchen table. He'd been developing written documentation since November, building student reference materials for people who wanted to practice at home between sessions. The manuals were in the same format as his accounts: systematic, exact, each instruction numbered and followed by the specific common error it was designed to prevent.

I set my bag down and looked at the table. He hadn't looked up. The manual he was working on was open to a page with a hand-drawn diagram of a fabric fold, annotated in his careful hand — the same hand that had been writing workshop accounts since before I was old enough to read them.

"The water-pattern dyeing manual is nearly complete," he said, not looking up. "I've asked Xiaoyu to review the terminology."

Xiaoyu was reviewing his craft manuals. In addition to the high school coursework and the translation contracts she'd been building since the Osaka certification and the workshop booking management.

"She agreed to do it," I said.

"She suggested it. She said the technical terminology in the dyeing section was imprecise and she could standardize it." He turned a page. "She was correct. The dyeing section was imprecise. The terms I'd been using for thirty years are industry terms that aren't consistent with the standard reference vocabulary. Her standardization makes the manuals compatible with other published resources."

He said this without embarrassment. The terms he'd been using for thirty years — the terms that were correct for the practice as he knew it — were imprecise by a standard he hadn't been measuring against. Xiaoyu had measured against it and found the gap. He'd accepted the measurement. That was how he'd always worked: the standard was the thing, not the pride. It was the same quality that had made him a craftsman worth learning from for three decades — not the pride in what he already knew, but the willingness to sharpen what he knew against a better edge.

The workshop was operating on the November-December booking pattern that Wanqing had correctly projected — the surgeon referral network had filled December, and January had sold out in the first week of the month. Xiaoyu was running the booking system on her own now. Father handled the instruction and the material preparation; Xiaoyu handled the administrative layer and the waitlist management.

"The spring sessions," Father said. "February and March. I've been thinking about adding a second craft."

"The lacquerwork framing."

"Yes. The booking demand suggests a second session type would fill without difficulty. Xiaoyu has been tracking the incoming inquiry data — we've had fourteen unsolicited inquiries about lacquerwork specifically in the past two months."

Fourteen unsolicited inquiries for a service they hadn't advertised. The surgeon referral network, functioning exactly as Wanqing had modeled in October. The network passed specific kinds of information — not just that the workshop existed, but that it was worth a specific kind of inquiry. Lacquerwork was a craft the workshop didn't offer yet. The referral network was already generating demand for it before the offering existed.

"You should add the lacquerwork," I said.

"Yes." He turned a manual page. "I was going to add it regardless. I wanted to tell you about it."

Mother came in from the canal-facing window with the specific economy of motion that meant she'd heard the relevant part of the conversation and was adding to it. "Wanqing called," she said. "She'll be here tomorrow morning. She's bringing something."

"What."

"She didn't say. She said she'd been working on it for three months and she wanted to show Father first." Mother looked at Father. "She said it was about the workshop."

Father looked up from the manual. I watched him process the information — not the content of it, which he had no way to evaluate yet, but the structure: something about the workshop, three months of preparation, she wanted to show him first. He nodded once and went back to the manual.

***

Wanqing arrived Saturday morning with a printed document in a folder. The folder had a tab labeled: *Workshop Development Model — January 2017 Version.*

She'd been working on it since May 2016. Eight months. The October revision had been what she'd mentioned on the balcony on October 1, the night the workshop opened. She'd continued refining it through November and December and the first two weeks of January. Eight months of a model she'd been building in parallel with everything else — the academic seminars, the contract work, the bench sessions, the guild records she read on the shared channel without ever making her knowledge visible on the council.

The document was thirty pages. She presented it to Father at the kitchen table — me sitting across, Mother beside Father, Xiaoyu beside me with her own copy of the draft that Wanqing had sent her two weeks earlier for review.

The presentation took forty-five minutes. She worked through it in the order she'd organized it: the booking demand analysis first, then the referral network pattern, then the pricing tier optimization, then the second-craft addition economics, then the instructor-scaling model — which was where Xiaoyu's name appeared as the projected second instructor — then the three-year revenue projection.

Father listened. He asked nine questions. She answered each one directly, with the source data behind the answer available when he asked where a number had come from. He never asked a question twice. She never repeated herself. The exchange had the quality of a technical review between two people who respected each other's precision and didn't waste either person's time on anything that wasn't exact.

At the end he looked at the final page. The three-year projection was a single graph with three lines: conservative, expected, and upper bound.

"The three-year projection," he said. "The revenue model at the three-year mark."

"At the three-year mark, assuming the referral network grows at the observed rate from the first three months, the workshop's annual revenue exceeds the original shop's annual revenue by approximately 40%."

He was quiet for a moment.

"The original shop that I ran for thirty-two years," he said.

"Yes. The workshop model scales better with quality instruction than the retail model scaled with product sales. The constraint on growth is your available time and energy, not the market demand." She looked at the projection page. "The immunosuppressant fatigue profile — I incorporated Doctor Yan's notes from the December check-in — suggests your available energy will be consistent and not declining in years two and three if the calibration holds at its current level. The session calendar in the model reflects the realistic energy projection, not the best-case one."

She'd incorporated Doctor Yan's clinical notes into the economic projection.

I watched Father's face when she said that. There was something in it — the moment when he understood that she had taken the careful kind of care: not the care that hoped for the best outcome, but the care that accounted for the realistic one and built the plan around it. The kind of care that didn't require anything from him except that he keep doing what he was doing. He looked at her for a moment. He didn't say anything yet. He was still processing.

Father looked at the projection for a long time. The graph. The three lines. The three-year numbers.

"Thank you," he said. He said it the way he said things that were large and required a simple word because the large version would take too long to say correctly.

"The model is accurate as of January," she said. "I'll update it quarterly as new booking data comes in."

She was going to update it quarterly. She had been doing this since May 2016. Tracking the incoming inquiry data, building the pricing analysis, incorporating Doctor Yan's notes, scheduling quarterly updates as a standing item.

I looked at her across the kitchen table.

She looked back at me for a moment — not the corner-smile version, not the expression-management version she used when she was aware of being observed. Just directly, with the specific quality of someone who had done a thing they'd been wanting to do and was glad it had been received the way they hoped. A look that lasted about two seconds and then was replaced by the working expression she wore when the task was still in progress.

"The lacquerwork framing addition," she said, looking back at Father. "I have a note on page 22. The inquiry pattern suggests the demand is somewhat seasonal — spring and autumn peaks, with summer and winter at 60-70% of peak levels. The session calendar should account for that."

They went to page 22.

The kitchen table had been, for the past two years, the place where the plans were made: the fund projections in October 2014, the workshop margin notes in April 2015, the December 2015 kitchen-table workshop sessions where Father had walked Wanqing through the booking model while I was in Hangzhou. Now the growth model, thirty pages, on the same table.

The table was the same table it had always been. The plans on it had changed. And the people at it had changed in the specific way that people changed when the plans they'd made together had worked — not dramatically, not visibly, but in some quality of ease, some loosening of the thing that kept you careful when you weren't yet sure the structure would hold. Father had the ease of someone whose work was being recognized accurately. Wanqing had the ease of someone who'd done the work correctly and knew it. Xiaoyu had the ease of someone seeing her name on the page where she'd expected it would eventually be.

I looked at it for a moment after Father and Wanqing moved to page 22 and Xiaoyu leaned over to follow the lacquerwork seasonality chart.

Three years of planning on this table. The plan had worked. The next plan was being made.

That was the shape of it.

Previous172 / 350Next

Comments (0)

Sign in to comment

No comments yet.