Chương 105: CHAPTER ONE HUNDRED AND FIVE: OSEI REPORTS

Amanda Osei — the signal operations specialist that Price had found in the outer district six months ago — came to the council in June with the heliograph network's first comprehensive operational assessment. She had been building the assessment since her arrival, with the systematic approach of someone who had spent a career analyzing communications infrastructure. The document was thirty-one pages, which was not the longest document the council had received but was among the most technically dense.

She presented it standing, at the head of the table, with the composed authority of someone who had found her function in the organization and was occupying it fully.

"The current network," she said, "performs at approximately seventy percent of its theoretical optimal. The gap is in three areas: relay timing, weather redundancy, and the codebook's efficiency at scale."

"Explain the codebook efficiency," Jin said. He was sitting forward — the specific posture of someone who had built a system and is hearing an assessment of it.

"The current codebook was designed for the network's original scale," Osei said.

"At the time it was designed, you had eleven relay stations and twelve active users. You now have thirty-seven stations and sixty-one active users." She paused.

"The codebook's bit efficiency — the amount of information that can be transmitted per signal unit — decreases as the number of users increases and the variety of information types increases. You're transmitting at the same rate as two years ago, but the information load has increased significantly."

"What's the solution?" Jin said.

"A new codebook," she said.

"Designed for the current scale and anticipated future scale. I've drafted one." She put a second document on the table — twelve pages, organized with the precision of someone who had been thinking about codebook design for the past six months and had arrived at something she was confident in.

"The new codebook increases the bit efficiency by approximately forty percent. It also addresses the weather redundancy through a secondary signal register designed specifically for adverse conditions — lower information density, but functional in conditions where the primary system is not." This story has been unlawfully obtained without the author's consent. Report any appearances on Amazon. Jin picked up the document and began reading it immediately, which was its own form of acknowledgment.

"The relay timing," Marcus said.

"What's the gap there?"

"The relay operators — the local contacts who aren't part of our organization — have variable response times," Osei said.

"The variance is manageable in normal conditions but becomes a problem when speed is critical." She paused.

"The solution is training. Not advanced training — basic training in the timing protocol. I've designed a half-day training session that can be conducted at each relay point on the next maintenance cycle."

"Timeline for the full implementation?" Marcus said.

"The codebook can be distributed through the maintenance cycle in four months," Osei said.

"The relay training runs parallel — same maintenance visits. The total implementation window is four months from authorization."

"Authorized," Marcus said.

"Work with Jin on the implementation schedule." Jin, still reading the codebook document, raised his hand briefly in acknowledgment without looking up. After the session, Jin came to Marcus in the corridor.

"The codebook," he said.

"Yes," Marcus said.

"It's better than mine," Jin said. He said it with the flat honesty of a professional making an accurate assessment of work that exceeded their own.

"Significantly better in three areas. I wouldn't have arrived at the bit efficiency improvement — I would have built around the constraint rather than addressing it."

"Osei is good," Marcus said.

"She's exceptional," Jin said.

"The specific domain — communications architecture at scale — is exactly what this network needs right now and exactly what I don't have deep expertise in." He paused.

"I built the network. She's going to make it work at scale."

"The division of function," Marcus said.

"Yes," Jin said.

"I collect. She transmits. Neither is sufficient without the other." Marcus thought about what Danny had said about the facilitator's role — the one that scales. The network was scaling, and what made it scale was not any single person's capability but the combination of capabilities that the organization had assembled, each one filling a gap the others couldn't fill.

He went back to the desk and added a note to the organizational chart that Vance maintained: Network: Jin (collection architecture) + Osei (transmission architecture). Both required.