Chapter 91: The Machine That Organizes
Location: Gorakhpur — Shergill Electronics & Control Systems Division (adjacent to ISMC)
Date: 3 March 1972 — 10:10 Hours
The building didn't look important.
That was the first reaction most people had when they stepped inside.
There were no heavy machines, no sound of production, no visible output that justified the level of security outside. Just rows of tall metal cabinets, indicator lights blinking steadily, and a long console table covered with switches, paper printouts, and narrow display panels filled with numbers.
If someone didn't know better, they would assume this place was unfinished.
Karan didn't.
He knew exactly why it existed. What he wanted to see was whether it was ready.
Inside, Aditya was already dealing with a situation that looked familiar—two engineers arguing over the same problem from opposite directions.
"I've checked the execution cycle three times," the first engineer said, holding a sheet filled with tightly printed numbers. "There is no delay inside the system. It's performing exactly as designed."
"That's not the point," the second replied, clearly trying to stay patient and failing slightly. "You're assuming all input data arrives at the same time. It doesn't. The system is being forced to make a decision using information that belongs to different moments."
Aditya stepped in before the discussion went in circles again.
"You're both correct about your parts," he said, his tone steady. "But you're missing the reason it's happening."
They both turned toward him.
"The system isn't slow, and it isn't malfunctioning," Aditya continued. "It's waiting. And it's waiting because it's being given inputs that are not aligned in time."
He pointed at the sheet.
"This region updates every few seconds. That one is delayed. The system is trying to reconcile both as if they're current."
Karan, now standing behind them, added in a calm, almost conversational tone, "And the moment a system starts waiting for clarity, it stops being useful in real time. At that point, you're just automating delay."
Both engineers straightened immediately.
Aditya glanced at Karan. "You came early."
"I wanted to see the part that doesn't work smoothly," Karan said. "The rest is easy to explain."
That was when the visitors entered.
This wasn't a ceremonial group.
Each man had a defined role in how the country was being run.
From the Ministry of Energy, a senior coordination officer responsible for integrating the national grid.
From the Central Electricity Authority, two engineers who handled real-world load distribution.
From the Ministry of Railways, a logistics director managing freight movement across zones.
From the Ministry of Industry, a planning officer responsible for aligning production with supply.
And from the technical side—
R. Narasimhan had sent a systems specialist experienced in large-scale computing, while
Electronics Corporation of India Limited had deputed a control systems engineer already working on industrial automation.
Homi Nusserwanji Sethna had also sent a reactor instrumentation expert—someone used to systems where hesitation was not acceptable.
They were not here to be impressed.
They were here because something in this building might change how their systems functioned.
The Railways officer was the first to speak, looking around with a slight frown.
"I'll be honest," he said. "If you had shown me this building from the outside, I would have assumed it was storage. It doesn't look like something that affects national operations."
Aditya smiled faintly. "That's because nothing here produces visible output."
Karan added, "It changes how everything else moves. You just don't see it directly."
They gathered around the central console.
No introductions were repeated. Everyone knew why they were there.
Karan rested his hand lightly on the table and began without buildup.
"We've increased production across sectors," he said. "Power generation has expanded. Industrial output has increased. Material movement has accelerated."
He looked at them briefly, making sure the point was clear.
"But the way decisions move hasn't changed."
The Ministry of Industry officer nodded. "That's accurate. Coordination still depends on reports and confirmations. Information comes in, it gets checked, and then action follows."
The Central Electricity Authority engineer added, "In grid operations, even a few minutes of delay changes load conditions."
Karan looked at him. "And those changes don't wait for approval."
The engineer gave a small, knowing nod. "No, they don't."
Aditya stepped forward, simplifying the idea.
"Think of it this way," he said. "Power is generated continuously. Factories consume continuously. Trains move continuously. But decisions—where to send power, how to route supply—those still happen in steps."
He paused just enough for it to register.
"And every step introduces delay."
The Railways officer leaned slightly forward now, more interested than skeptical.
"So the problem is not production anymore. It's coordination."
"Yes," Aditya said. "And at this scale, coordination through people alone starts becoming a bottleneck."
The Energy Ministry officer folded his arms. "And this system removes that bottleneck?"
Karan shook his head slightly. "It reduces it to the point where it no longer slows the system."
He turned to the engineer. "Show them."
The switches were adjusted.
The system came alive—not loudly, but with quiet precision.
Numbers on the display began to shift.
Aditya pointed at the panel.
"This is a simplified model of three connected regions in the power grid. Each produces and consumes electricity."
He tapped one section.
"We're reducing supply here."
The numbers dropped.
Within seconds, the adjacent regions adjusted. Output increased where possible. Load shifted where necessary.
Then everything stabilized again.
No pause. No confusion.
The Central Electricity Authority engineer leaned in, studying the numbers closely.
"That redistribution normally takes coordination between multiple stations," he said. "Calls, confirmations, approvals."
"And by the time it happens," Karan added, "the situation has already changed again."
The Railways officer let out a short breath. "That part sounds familiar."
A faint, brief smile passed across Aditya's face. "It should."
The reactor instrumentation expert spoke next, his tone measured.
"How does the system decide where to draw from?"
Aditya answered, "We define operational rules. Priority areas, safety limits, transmission capacity. The system applies those rules instantly."
Karan added, "It doesn't think. It executes without hesitation."
The same expert asked, "And if your rules are flawed?"
Karan met his gaze directly. "Then the system exposes the flaw immediately. It doesn't hide it behind delay."
That answer stayed in the room for a moment.
Because it applied to more than machines.
The Industry Ministry officer spoke next. "What about cost and training? Systems like this won't scale easily."
Aditya nodded. "True. But inefficiency at this scale is already costing more. It's just distributed, so no one sees the full number."
He gestured toward the display.
"When power is wasted, when factories stop mid-cycle, when routing delays occur—those losses add up quietly."
Karan leaned slightly forward, his tone steady but clear.
"We're not introducing this because it's advanced," he said. "We're introducing it because we've reached a scale where manual coordination will start limiting growth."
There was no disagreement this time.
Just silence filled with calculation.
The Energy Ministry officer asked, "Where do you start?"
Karan answered immediately.
"Where delay causes the most damage."
He counted clearly, without rushing.
"Power grid control."
"Industrial coordination."
"Defense systems."
Aditya added, "Places where timing defines outcome, not just efficiency."
The Railways officer asked one final question. "And after that?"
Karan allowed a small, relaxed smile.
"After that, you won't need a meeting to justify it."
A few of them exchanged brief looks.
Not skeptical.
Just acknowledging what they had seen.
Karan stepped back from the console.
"We're not building a machine," he said. "We're building the ability to manage a system at the speed it operates."
No one argued.
Because for the first time, they had seen coordination happen without delay.
And once you see that—
Going back to slower systems doesn't feel like caution.
It feels like inefficiency.
The machines would not be announced.
They would not be displayed.
They would simply be installed—quietly—where they mattered most.
And from there, they would begin changing how decisions moved.
Not by replacing people.
But by ensuring that when a decision was needed—
It arrived on time.