ARC 2: Chapter 9 – Project Zero: The Code
Timeline: September 2004
Location: Future Star Group Headquarters, Lavelle Road – "The Server Room"
Status: Data Integration Phase
The System Interface: The Data Gap
The room used to be a storage closet.
Old legal files, broken chairs, and discarded fax machines had once lived here, gathering dust like forgotten arguments. Now, it was the loudest room in the Future Star Group headquarters.
Two bulky desktop towers—beige, scarred, and state-of-the-art by 2004 standards—hummed aggressively. Their internal fans whined like tired insects, pushing out waves of hot air that clung to the walls. Ethernet cables ran across the floor like veins, feeding into a blinking modem struggling to maintain a stable broadband connection.
Rudra wiped sweat from his forehead and stood in the center of it all.
This was not a cricket ground.
This was not a net session.
This was a battlefield of a different kind.
The System flickered alive in his vision, translucent panels layering over the cramped room.
[SYSTEM OVERVIEW: KNOWLEDGE DISPARITY]
Domain: Competitive Cricket (U-19 Level, 2004)
Available System Knowledge:
– Tactical Meta (2026): COMPLETE
– Opponent Historical Data (2004): 0 bytes
– Player Behavioral Models: INCOMPLETE
User Attributes:
Analytical Skills: LVL 35 (MASTER)
Coding – C++: LVL 12 (PROFESSIONAL)
Core Problem: Foresight without data = Guesswork
Primary Objective: Translate future analytical paradigms into present-day software. Bridge the Data Gap.
Rudra exhaled slowly.
I know how this game will evolve, he thought. But knowing the destination isn't enough. I need a map built from today's terrain.
Without data, his advantages in the U-19 circuit would erode quickly. Talent plateaued. Instincts dulled. Everyone caught up eventually.
Unless you moved faster than the curve itself.
The Executor: Aryan "Zero" Bhatia
A figure hunched over the keyboard barely acknowledged Rudra's presence.
Aryan Bhatia—twenty-two, underpaid, underappreciated, and dangerously intelligent—typed as if the machine might escape if he slowed down. His hair was wild, his eyes bloodshot from too many sleepless nights, his T-shirt wrinkled like he had slept in it for days.
This was the man Rudra had rescued from a collapsing dot-com startup that had run out of money but not ambition.
Rudra had renamed him the moment they met.
Zero.
Because he thought in binary.
Because he started from nothing.
Because everything meaningful would be built on him.
"The server's syncing," Zero muttered, eyes glued to a black screen filled with green text. "Ranji Trophy scorecards. Ball-by-ball logs where available. It's… messy."
"How messy?" Rudra asked.
Zero snorted. "PDFs converted to text. Inconsistent formats. Missing overs. Half the grounds don't even record pitch conditions."
Rudra nodded. He had expected this.
"And you still don't know why we're doing this," Zero continued. "I mean—what am I supposed to extract? Batting averages? Strike rates?"
Rudra walked to the side table and pulled out a folded sheet of paper.
It was a crude MS Paint printout. A rough cricket field diagram, boxes scribbled with notes, arrows pointing in unnatural directions.
"We're not building statistics," Rudra said calmly. "We're building behavior."
Zero finally turned, curiosity cutting through exhaustion.
"Explain."
The Code: Shot-Zones and Fatigue Curves
Rudra picked up a marker and faced the whiteboard.
🧠 INTERNAL LOG: LEGACY MIND [46y]
In five years, IPL franchises will hire analysts before coaches.
In ten, matchups will be planned ball-by-ball.
Right now, nobody is looking.
That's why we win.
"Cricket," Rudra began, drawing a rough batsman silhouette, "isn't random. It only looks that way to people who don't measure it."
He shaded the off-side.
"Shot-Zones. Every batsman has comfort areas. Even the great ones. Under pressure, they default to muscle memory."
He tapped the board.
"The U-19 Mumbai captain—Kulkarni. Sixty percent of his boundaries come between cover and point. When the field's tight, he still goes there."
Zero's fingers hovered over the keyboard.
"So… heatmaps?"
"Yes," Rudra said. "But not static. Dynamic. Filtered by match situation. Required run rate. Bowler type."
Zero's eyes lit up despite himself. "That's doable. Heavy computation, but doable."
Rudra continued.
"Fatigue Curves. Bowlers don't break suddenly. They decline predictably. Speed drops. Length shifts. Control loosens."
He drew a downward sloping graph.
"We track pace against overs, humidity, temperature, workload. The software flags the exact window when a fast bowler is no longer lethal."
Zero leaned back. "You're not just tracking fitness. You're tracking psychology."
Rudra smiled faintly.
"And finally—Pattern Recognition."
He circled the diagram.
"Every bowler has tells. When defending, they go fuller. When attacking, they test the body. We log line-and-length changes based on scoreboard pressure."
Zero exhaled slowly. "You're not predicting the next ball."
"No," Rudra said softly. "We're predicting the bowler."
Silence filled the room.
Then Zero laughed—short, disbelieving, exhilarated.
"You're insane," he said. "And this is the coolest thing I've ever built."
The First Hint of System Meets Reality
Two weeks vanished.
Zero slept on a folding chair. Ate noodles from paper cups. Lived on caffeine and obsession. Rudra balanced training, recovery, and architecture decisions with unnerving calm.
The prototype came alive at 2:47 a.m.
They named it The Oracle.
The interface was crude—gray panels, basic graphs, pixelated field diagrams—but it worked.
Rudra fed in his own net session data.
"Run analysis," he said. "Target: the pacer from Day One."
The machine whirred. Fans screamed.
Lines of output scrolled.
[ANALYSIS COMPLETE]
Target Profile: RAW TALENT
– FAST BOWLER
Fatigue Curve:
– Pace Drop: ~12 kmph after sustained spells (7th over average)
Behavioral Patterns:
– Bodyline deliveries: 80% against injured/younger batsmen
– Post-boundary response: 50% chance of wider, slower delivery
Psychological Marker:
– Aggression spikes when dominance is perceived
– Control decreases after visible resistance
Rudra stared at the screen.
The data confirmed everything his instincts had whispered.
The bowler wasn't unstoppable.
He was readable.
[SKILL PROGRESSION]
Coding – C++: LVL 12 ➝ LVL 15 (PROFESSIONAL)
Analytical Skills: LVL 35 ➝ LVL 36 (MASTER)
New Trait Unlocked: [The Oracle's Eye]
Effect: Enables real-time data overlays and probabilistic insights during matches.
Rudra closed his eyes briefly.
This is it.
This was how the System merged with reality—not as magic, but as infrastructure.
The Algorithm Debate
Rudra didn't keep the software secret.
Not entirely.
He invited the U-19 coaching staff to the lab. Coach Vasudevan arrived skeptical, arms crossed. Major Rathore lingered near the door like he expected the room to insult him.
Rudra demonstrated quietly.
Shot-zones.
Bowler fatigue alerts.
Fielding probability maps.
Coach Vasudevan frowned. "So you want me to trust this over experience?"
Rudra shook his head. "No, Coach. I want to support experience with certainty. This doesn't replace instinct. It removes blind spots."
Major Rathore scoffed. "Cricket is played with heart, not computers."
🎙️ COMMENTARY BOX: KSCA BOARDROOM
Major Rathore:
"This is turning sport into a video game."
Aakash Chopra:
"Or into chess. And chess champions don't complain about thinking."
The room divided itself quietly.
Rudra didn't argue.
Data didn't need approval.
The Emotional Anchor: Janavi's Data
That evening, Rudra brought his laptop into the kitchen.
Janavi was mid-preparation, pots bubbling, spices filling the air.
"Ma," he said casually, "if you shift your delivery timing by fifteen minutes, traffic density drops. You save thirty minutes."
Janavi didn't even look at the screen.
"Traffic doesn't follow your numbers," she said. "People do."
Rudra smiled.
"Fair," he said. "But your nutritional data is flawless. Tier Divine."
She laughed and flicked water at him.
In that moment, Rudra realized something.
Not everything needed optimization.
Some things already ran perfectly.
The Oracle was live.
Project Zero was funded.
The Data Gap was closing.
💰 FSG CAPITAL TICKER [SEPTEMBER 2004]
Tech Division Budget: ₹15 Lakhs allocated
Google IPO: Imminent
Liquidity: Ready
🧠 SYSTEM THOUGHT
Talent wins matches.
Preparation wins tournaments.
Data wins eras.
I am no longer just ahead of my opponents.
I am ahead of the game itself.
Next Chapter:
Arc 2: Chapter 10 – The Small Town Blueprint
(Where Rudra's models identify an unorthodox wicketkeeper in Ranchi—and history quietly shifts.)