CHAPTER 15 : The Testing Ground
Nekoma Gymnasium — June 7th, Saturday, 9:30 AM
Tama High School's starting lineup crossed the net in dark green jerseys, and Arisu's meta-knowledge sorted them into categories before the warm-up volleys ended.
Setter: right-handed, prefers high sets to the outside, telegraphs quick sets with a hip rotation. Ace: zone four specialist, hits cross seventy percent of the time but switches to line when frustrated. Middle: tall, slow transition, relies on quick tempo sets to compensate. Libero: solid but predictable — always covers zone six, leaves zone one soft.
Canon data, confirmed in the three warm-up rallies he'd watched from the bench while the teams loosened up. Tama High was a school the anime had shown in exactly one background panel during a tournament bracket montage — minor enough to be forgettable, significant enough to have a real team with real players and real patterns.
Nekomata tapped his clipboard. "Misaki. You're starting."
Not "you're subbing in for the back row." Not "defensive rotation." Starting. Full rotation. First whistle to last.
"Yes, sir."
First time starting an official practice match. Not a scrimmage. Not a tournament sub. Starting. The whole court, the whole game, the whole responsibility.
[Zone Architect] Match detected. Court Dominion active. Zone radius: 6 meters. Dual rules available. MS: 40/40. Advisory: sustain budget recommended — dual activation drains ~4 MS per cycle.]
He stepped onto the court and felt the zone expand from his feet — the now-familiar pulse of Court Dominion mapping the space, the floor lines glowing faint blue in his awareness, the net height registering as a data point rather than an obstacle. Six meters of controlled territory. Enough to cover the back row and most of the mid-court during defensive rotations.
"Dual activation. Contact Highlight plus Bounce Preview."
The command was mental, silent, invisible. Two data streams spun up simultaneously — Contact Highlight painting each ball contact in spectral blue, Bounce Preview projecting a landing marker 0.8 seconds before impact. The combination was the defensive equivalent of playing a game with the answer key open: he could see where the ball was going before it arrived, and he could see where every player was positioned relative to that landing zone.
The receiving proficiency that had been crawling upward through weeks of dual brain sessions with Kenma and Yaku's grudging corrections had crossed forty percent three days ago. The Bounce Preview unlock had come with it — a Tier 1 ability that turned every incoming spike into a math problem with the answer written in ghost light above the court.
[Zone Architect] Bounce Preview active. Landing projection: 0.8s pre-impact. Accuracy: 72% (proficiency-dependent). MS: 36/40.]
Seventy-two percent accuracy. Not perfect. Roughly three out of four projections will be correct. The fourth will be wrong, and wrong Bounce Preview data is worse than no data because I'll commit to a position that's empty.
Budget: four MS per activation cycle. At dual-rule sustained use, I have approximately thirty to thirty-five minutes before the tank hits advisory levels. A set runs twenty to twenty-five minutes. That means I can run full dual activation for one set comfortably. The second set will require rationing.
The whistle blew.
The first set belonged to Nekoma in a way that made the scoreboard feel redundant.
Tama's ace loaded a cross from position four — the seventy-percent tendency — and Arisu's Contact Highlight tracked the arm swing while Bounce Preview painted the landing zone in blue. The call came before the spike: "YAKU, CROSS, ZONE FIVE!"
Yaku was already moving. The dig was clean. Kenma set Yamamoto. Kill.
Three points later, Tama's setter tried a quick to the middle. Bounce Preview flickered — 0.8 seconds of warning, the landing marker shifting mid-flight as the ball changed trajectory. Arisu adjusted the call: "LEV, STRAIGHT DOWN! CENTER!"
Lev's block went up in the right place at roughly the right time, which for Lev was a masterpiece of coordination. The spike deflected off his fingertips and dropped on Tama's side.
Point after point, the defensive positioning tightened into a grid that left Tama's hitters spiking into bodies instead of floor. Every attack met a receiver who was already there, a blocker who was already jumping, a coverage player who'd shifted before the play developed. The dual brain operated in stereo — Arisu calling the defense, Kenma adjusting the offense, the two systems interlocking so seamlessly that the team moved like a single organism with twelve limbs and two processors.
Tama's coach called a timeout at 12-5.
From the bench, Arisu could see the coach gesturing at a whiteboard, drawing arrows, trying to explain to his players why their attacks kept finding occupied zones. The explanation was simple: Nekoma's first-year defensive coordinator was running a system that tracked ball trajectories and player positions in real time, supported by a Zone Architect interface that shouldn't exist.
The explanation the coach would arrive at was different: "They're well-coached. Focus on execution."
The cover story is the same one that's been working since the first practice match — good coaching, good chemistry, smart positioning. It's plausible because it's partially true. Kenma and I ARE developing real chemistry. The calls ARE based on real court reading that I'd be making even without the system. The system just makes them faster and more accurate.
The problem is that "faster and more accurate" eventually exceeds what coaching and chemistry can explain.
First set: 25-16. Nekoma in thirty-two minutes of play.
[Zone Architect] Set 1 complete. MS: 18/40. Dual-rule sustained use: 32 minutes. Efficiency within projected range.]
Eighteen. Twenty-two MS spent in one set. The budget said I'd have thirty-five minutes of sustainable use. I've used thirty-two and I'm at eighteen — which means the second set starts with less than half tank.
Option one: dual rules again, crash around the twenty-minute mark, play the last five minutes on fundamentals. Option two: single rule for the full set, maintain base-level system support without the crash. Option three: burst activation — dual rules for critical points, off for safe leads.
Option three. The scalpel approach. Dual rules when the margin is tight, conservation when it isn't.
Second set. Arisu ran single-rule for the first rotation — Contact Highlight only, letting his natural court reading handle the positioning calls while the system tracked ball trajectory. The calls were good. Not first-set good. The gap between dual-screen precision and single-screen approximation was the gap between a surgeon's scalpel and a good kitchen knife: both cut, but only one could find the specific vein.
Tama adjusted. Their ace switched to line shots — probably the coach's halftime directive, an attempt to exploit the zone Nekoma's defense had been softest in during the first set. The adjustment was predictable. Arisu had meta-knowledge of Tama's coaching style, which favored simple tactical switches over complex strategic overhauls.
At 8-6 Nekoma, Arisu activated dual rules. Contact Highlight plus Bounce Preview. The data streams merged and the court snapped back into high-definition tactical awareness.
"YAMAMOTO, LINE! HE'S SWITCHING AGAIN!"
The call saved a point. Then two more. Tama's ace, increasingly frustrated with line shots that kept finding blockers, reverted to cross — exactly the tendency Arisu had catalogued from canon and confirmed in the first set.
[Zone Architect] MS: 14/40. Dual-rule drain accelerating. Advisory: deactivate non-essential rules.]
He stayed on dual. One more rotation. The margin was 16-10 and widening, but the data quality was degrading — Bounce Preview's landing markers had started to jitter, the projections arriving with a flicker that meant the accuracy was dropping below the seventy-two percent baseline.
At 18-12, the Bounce Preview painted a landing zone in position one. Arisu called it: "SHIBAYAMA, HOLD RIGHT! ZONE ONE!"
The spike went zone five. Opposite corner. Shibayama was out of position because Arisu's glitched data had sent him there, and the ball hit the floor between three players who were all in the wrong place because the defensive coordinator's system had told them to be.
Point, Tama.
"AGAIN!" Tama's bench erupted. Their ace, grinning for the first time all match, loaded another approach.
The next spike found the same gap. And the next. Three straight points through the zone Arisu's bad calls had opened.
Yaku covered the third spike with an emergency dig that required him to fully extend and crash his hip into the floor — the kind of save he hadn't needed to make in the first set because Arisu's calls had eliminated the need. The dig went up. Kenma set. Nekoma scored. But Yaku's eyes found Arisu across the court, and the message was clear without words.
"You went quiet."
Not quiet. Worse. I went wrong. The data degraded below useful accuracy and I kept using it because the habit of trusting the system is stronger than the judgment to know when the system is lying.
[Zone Architect] MS: 8/40. Critical threshold. Zone rule accuracy compromised. Recommend: full deactivation.]
He killed both rules. The data streams collapsed. The court went silent — not actually silent, still full of shoes and shouts and ball impacts, but silent in the way that mattered. No blue trajectories. No ghost markers. No positional snapshots. Just eyes and ears and the twenty-four percent of receiving proficiency that existed independent of the Zone Architect System.
Fundamentals. Just fundamentals. The body that's been training for two months, doing the work, building the proficiency points one at a time. Show me what you've got.
The last ten points of the set played without system support. Arisu's calls came slower — half a second later than the dual-rule precision, sometimes a full second. Good enough. Not great. Yaku made two more emergency saves that wouldn't have been necessary if Arisu's awareness hadn't dropped from omniscient to merely competent. Kuroo's blocks compensated for the positioning errors by sheer athleticism and the captain's instinct for reading hitters.
25-20 Nekoma. Match won. But the second set had told a different story than the first.
Post-match. Bench.
Arisu sat with his water bottle pressed against his forehead and the headache building behind his eyes — not a migraine, not yet, but the specific low-grade throb that came from pushing MS to the basement and asking his brain to function on fumes. His legs felt heavy. His stomach growled loud enough that Lev, passing by, dropped a rice ball in his lap without comment.
The first-set Arisu was devastating. The second-set Arisu was a liability for six consecutive points. The difference isn't skill — it's resource management. I ran the engine too hard in set one, had nothing left for set two, and the drop-off was visible to everyone on the court.
Yaku knows. He covered my gaps three times and his expression said everything his words didn't. Nekomata watched from the bench with the same half-lidded squint he uses when he's filing observations for later. Kenma adjusted his sets in the second set to compensate for my reduced defensive coverage — I could see him recalibrating in real time, routing attacks away from the zones I'd left exposed.
They adapted. They covered. They won despite my second-set crash.
But I can't keep putting them in a position where they need to cover for me.
He opened his notebook. The pen moved with the deliberate precision of someone documenting a failure they intended to never repeat.
Dual rules sustainable for ~25 minutes of active play. After that, dead weight.
Below that, in smaller writing:
Solutions: 1) Burst activation (dual on critical points, single otherwise). 2) Increase MS pool (Level 7+ grants +5 MS). 3) Improve fundamentals so system crash doesn't equal defensive collapse. 4) All of the above.
He circled option four.
The headache pulsed. He ate Lev's rice ball. Drank the rest of his water. His serving hand — the one that had hit two thousand deliberate serves since the tournament — rested on his knee, and the calluses on the palm heel were thick enough now that the skin didn't sting when he pressed it against the hard edge of the bench.
Back in the first tournament, the MS budget was the same problem at a smaller scale — forty MS, competitive drain, empty by the end of one rotation. Now it's forty MS with dual rules, empty by the end of one set. The pool size hasn't changed since Level 5. But at Level 7—
[Zone Architect] Level 6 progression: 82%. Level 7 threshold approaching. Milestone reward preview: Future Branches (1 branch, 60% accuracy, 8 MS per activation).]
The notification had been pulsing in the dream interface for three nights. Future Branches. Predictive modeling — the ability to see a ghostly projection of the next two and a half seconds of play. One branch. Sixty percent accuracy. Eight MS per use.
Eight MS. That's a fifth of my current pool for a single prediction that's wrong forty percent of the time. Expensive, unreliable, and potentially game-changing.
Like everything the system offers. The question is never whether the tool is worth having. The question is whether I can afford to use it.
He closed the notebook. The headache was fading. His body ached in the familiar places — forearms, shoulder, lower back — and in new places that the full-match intensity had awakened. The muscles along his ribs protested when he twisted to put the notebook in his bag. His feet, inside two pairs of socks because the body still consumed cotton at a rate that suggested a personal vendetta, were hot and damp and ready to be free.
Across the gym, Kenma was packing his bag with the unhurried precision of someone who allocated exactly the necessary energy to each task and not a joule more. He glanced at Arisu. The glance lasted half a second. In that half-second, Arisu saw the assessment — Kenma's eyes tracking the water bottle against the forehead, the posture, the fatigue — and the conclusion.
He knows the second set was different. He adjusted for it. He didn't ask why. Kenma doesn't ask — he observes, hypothesizes, and tests. The question isn't whether he noticed. The question is what he filed.
The team filtered out of the gym. Nekomata's office light clicked off. The scoreboard still showed 25-16, 25-20 — two clean wins that looked comfortable from the outside and felt like a stress test from the inside.
Arisu shouldered his bag. The headache had settled to a whisper. His brain, running on the dregs of MS and the protein bar he'd eaten between sets, turned over one more calculation before he left the gym.
Level 7 is close. Future Branches is close. And the MS pool needs to be bigger before either of those tools becomes useful in a match that lasts more than thirty minutes.
The math doesn't lie. The tank is the bottleneck. Everything else — the reads, the calls, the dual brain, the fundamentals — is infrastructure. Without fuel, the infrastructure sits dark.
His phone buzzed. Kenma.
Your calls in set 2 degraded after minute 28. Data or fatigue?
Arisu stared at the message. Kenma had timed it. Kenma had noticed the exact minute the quality dropped and measured the duration. Kenma was building a model of Arisu's performance curve the way he'd build a model of any system — inputs, outputs, degradation rate.
Fatigue. Working on it.
Mm. Noted.
Two words. Filed. Added to the growing catalogue of observations that Kenma Kozume was assembling about a teammate whose capabilities had a shelf life that didn't match any normal athletic explanation.
Arisu pocketed his phone and walked home. The notebook in his bag held the math. The dream interface held the preview. And somewhere between Level 6 and Level 7, the system was preparing to offer him a tool that could see the future — if he could afford the price.
Want more? The story continues on Patreon!
If you can't wait for the weekly release, you can grab +10, +15, or +20 chapters ahead of time on my Patreon page. Your support helps me keep this System running!
Read ahead here: [ patreon.com/system_enjoyer ]