Chapter 178: INS VIRAAT
15 January 1975
Severomorsk, Kola Peninsula — Northern Fleet Headquarters, Soviet Union
(controversial chpter but you have to understand ,sometimes you have to pray for someone success to win yourself ,thats why geopolitics is chess)
The Kola Peninsula in January was a specific kind of brutal.
Not the dramatic brutality of a storm — the steady, institutional brutality of an environment that had decided human beings were tolerated here on probation, at the environment's discretion, subject to immediate revocation if they forgot where they were. Minus twenty-two Celsius when the aircraft landed. The sun making its brief, unconvincing appearance between ten and two, doing nothing useful with the time. The cold coming from every direction simultaneously — from the frozen ground, from the frozen air, from the wind off the Barents, from the specific thermal quality of a landscape where nothing was warm and nothing was insulated and the only thing between a human body and the environment was what the human body's owners had thought to put on them.
Karan had been told what to wear.
He had ignored approximately half of it. He was acknowledging this in the privacy of the car's back seat with the specific silence of a man who would not say he was wrong but had revised his assessment of the advisory.
He looked out the window instead.
The Kola Bay. The anchorage. The Northern Fleet at rest — destroyers, cruisers, submarine tenders, replenishment ships, the specific sight of a superpower's naval investment arranged in their berths. Each vessel the product of an industrial and scientific apparatus that had been running at full capacity for thirty years, building toward a specific vision of what the Soviet Union needed to be in the world.
He had been reading about Gorshkov for three years.
Not casually. With the systematic attention he brought to things that mattered — the attention that produced genuine understanding rather than familiarity with the surface of a subject. He had read Sea Power of the State four times. He had read the translated excerpts of Gorshkov's internal papers that RAW's network had obtained. He had read the Politburo session transcripts from November 1974 — six weeks ago, when the Project Orel cancellation had been deferred for the third time.
He understood what Gorshkov was facing.
He understood it the way you understood things when you had spent three years learning the shape of a problem.
The car stopped.
The headquarters building was Soviet military functional — architecture as institutional statement, no ornament, no aspiration beyond function. The reception protocol was brief: identification, anteroom with Lenin's portrait, a glass of tea.
He waited.
He drank the tea.
He thought about nothing. This was his preparation — not reviewing arguments but clearing space, so that when the conversation began the thinking could follow what the other person said rather than what he had been expecting them to say.
The door opened.
Admiral of the Fleet Sergei Georgievich Gorshkov came into the conference room the way men came into rooms they had built their careers inside — not as a visitor, as the person to whom the room belonged.
Seventy-four years old. Medium height, compact, the physical economy of a career sailor. Four gold stars on deep navy blue worn with the relationship to uniform that comes after fifty years — not costume, not performance, identity.
He looked at Karan.
Not the standard assessment look — the look of a man who had been thinking about this meeting for a long time and was verifying something he had already calculated.
Karan looked back.
"Mr. Shergill," Gorshkov said. The naval officer interpreter stood at the room's side with the practiced invisibility of someone who had learned to be the transmission mechanism of a conversation without being in it. "You requested this meeting. What does Shergill Industries want from the Soviet Navy?"
Direct. No preamble. This was the form of the man — Karan had read enough about him to know it. Gorshkov had built a navy by forcing decisions past the people who preferred to defer them. He opened conversations the same way.
"Project Orel," Karan said. "Specifically: the programme's survival past March."
Gorshkov was still.
"Sit," he said.
They both sat — not across a formal table, two chairs facing each other, the configuration of a conversation rather than a negotiation. For now.
"You know about the December session," Gorshkov said.
"The third deferral in eighteen months," Karan said. "The Planning Ministry's position. The budget trajectory."
"The Planning Ministry," Gorshkov said, "has been arguing that the programme exceeds what the current budget cycle can absorb. This is arithmetically correct. The programme costs what it costs."
"Yes," Karan said.
"And you have a solution to this arithmetic," Gorshkov said.
"I have a proposal," Karan said.
Gorshkov looked at him. "Then make it."
Karan opened the case he had carried from the aircraft. He produced a document — twelve pages, Russian and English in parallel columns. He placed it on the table.
He said nothing.
He waited.
Gorshkov picked it up. He read it the way Karan read important documents — completely, from the beginning, without skipping to the conclusions. The interpreter translated quietly. The room was silent except for the distant sounds of the naval base.
He read the first page.
The second.
His expression remained entirely controlled. But there were things. A slight increase in the stillness of the hands. A quality of attention that was different on page four from what it had been on page one.
He read all twelve pages.
He set the document down.
He looked at Karan.
"The Bharat Urja Mahasagar Corporation," he said.
"The commercial vehicle through which the funding flows," Karan said.
"Full programme funding for Project Orel," Gorshkov said. "Milestone-verified disbursements through Vnesheconombank."
"Yes."
"In exchange for — this." He placed one hand on the document. "Tell me the exchange in your own words. Not the document's words."
Karan looked at him.
"Nuclear marine propulsion technology," he said. "The complete VM-4 engineering package. Catapult systems — design, installation, operation. The Orel blueprints. One hundred Indian workers embedded at Severodvinsk for the construction programme's duration. And a second carrier hull — built in Soviet yards to Indian specifications, incorporated into the Orel programme — that India receives as the INS Viraat."
He paused.
"India wants the Viraat in the water by 1980," he said.
The room was quiet.
Gorshkov looked at him for a long moment.
"Five years," he said.
"Five years," Karan said.
"Severodvinsk has never built a hull of this class in five years," Gorshkov said.
"Severodvinsk has never had a programme that was simultaneously funded from two directions and had a hundred additional workers," Karan said.
Gorshkov set the document down.
He stood.
He walked to the window. He looked at the Kola Bay — the ships, the unfrozen water, the grey light of the January afternoon.
When he turned, his expression had not changed. But the quality of his attention had shifted.
"Mr. Shergill," he said. "You are proposing to fund the Soviet Navy's most strategically significant programme in exchange for technology transfer to India. This is not a commercial transaction. This is a strategic arrangement dressed in commercial clothes."
"Yes," Karan said.
"The political apparatus of the Soviet Union does not conduct strategic arrangements dressed in commercial clothes without specific political clearances at the highest level," Gorshkov said.
"I know," Karan said. "The proposal goes to the General Secretary through your office. The political clearance is your problem, not mine. My problem is getting the arrangement accepted by the person in this room who can take it to the General Secretary."
Gorshkov looked at him.
"You are quite direct," he said.
"I am told this about myself," Karan said.
A pause.
"What," Gorshkov said, "does Shergill Industries manufacture that makes this exchange possible? What do you have that I don't already have better versions of from my own industry?"
This was the real opening question. The document established the terms. This question established whether the terms were real.
Karan answered it.
He told Gorshkov about the ISMC semiconductor process. Not the architectural performance — the fabrication process itself. The 3-micron node that had processed the nuclear test instrumentation data in ninety-one seconds. The specific chip production capability that ISMC had been running in production since October 1973.
Gorshkov interrupted once: "Our semiconductor programme at Zelenograd."
"Your semiconductor programme at Zelenograd produces components at approximately eight to ten microns," Karan said. "This is not an insult. This is the current state of the Soviet programme. The ISMC process is 3 microns. The difference in processing density is not incremental. It is generational."
Gorshkov was quiet.
"You are claiming," he said, "that an Indian company is producing semiconductor components at a fabrication node that our intelligence assessment says does not exist commercially anywhere in 1975."
"Your intelligence assessment is correct that it doesn't exist commercially," Karan said. "It was developed privately, for our own production requirements, and it has been in production since late 1973."
Gorshkov looked at him.
"What does your own production require it for?" he said.
"The aircraft radar," Karan said. "The fire control system. The nuclear test instrumentation. The things that required computational speed that commercially available components couldn't provide."
"You built the components because nothing available was sufficient," Gorshkov said.
"Yes," Karan said.
Gorshkov absorbed this.
"And the carrier combat management system," he said. "What you are proposing to provide."
"The Ganesh-class mission computing architecture," Karan said. "The same processing approach that ran the nuclear test instrumentation data, applied to the carrier's combat direction requirement. Fire control data from the ship's sensors, weapons assignment, communication with the air wing, fleet coordination. The processing speed allows simultaneous data from more sources with less latency."
He paused.
"The carrier's combat management system processes radar returns, sonar contact reports, satellite data, air wing communication, and external fleet communication simultaneously," he said. "The bottleneck in current carrier combat management is processing speed — the latency between sensor input and decision output. The Ganesh architecture reduces that latency significantly."
Gorshkov stood at the window.
He said: "Our naval computing teams have been arguing with the Planning Ministry for four years about the inadequacy of current combat management processing speeds. The argument has not produced additional funding."
"The ISMC chips for the Orel's combat management system are part of the arrangement," Karan said. "The processing speed argument becomes irrelevant because the problem is solved."
"And the ship's radar," Gorshkov said. He turned from the window. "Your document mentions radar technology transfer. What specifically?"
This was the part of the conversation Karan had prepared for most carefully.
Not because he expected Gorshkov to be easy about it. Because he expected Gorshkov to be brutal about it, and brutal negotiations required the most preparation.
"The carrier's surveillance radar system," Karan said. "What I am proposing to transfer."
"Specifically," Gorshkov said. He returned to his chair. He sat. This was the posture change of a man who had moved from the walking-around phase of evaluating a proposal to the sitting-and-negotiating phase of actually engaging with it. "What I want to know, and what the document is vague about, is whether the radar technology transfer includes the signal processing architecture that produced your aircraft radar's reported combat performance."
Karan looked at him.
"The reported combat performance of the S-27's radar," he said, "is documented by both sides of the 1973 war. The Egyptians and the Israelis reported the same engagement ranges. It is not reported — it is verified."
"Then the signal processing architecture," Gorshkov said, "is the most significant electronic warfare development produced by any non-superpower in the past decade. And you are proposing to transfer it to us."
"I am proposing to transfer the naval carrier surveillance radar architecture," Karan said. "Which is derived from the same processing approach, adapted for the carrier's maritime surveillance mission."
Gorshkov looked at him steadily.
"Let me be direct," Gorshkov said. "What I want is the full signal processing methodology. Not a version adapted for ships. The underlying architecture. The specific approach to parallel target processing that allows the engagement ranges your aircraft achieve."
"I know what you want," Karan said.
"Then tell me whether I get it," Gorshkov said.
A silence.
"No," Karan said.
Gorshkov's expression didn't change. But the quality of the room changed.
"Explain," he said.
"The full signal processing methodology is the irreplaceable core of every radar and computing system Shergill Electronics produces," Karan said. "Once transferred, I cannot control its subsequent movement. Your intelligence apparatus has its own relationships. Its own interpretations of what can and cannot be shared. I am not questioning your integrity. I am stating a structural fact about institutional information flow."
Gorshkov's voice was very level.
"You are telling me," he said, "that you are proposing an arrangement in which India receives nuclear marine propulsion technology from the Soviet Union, and in exchange you are offering me a partial version of what I am asking for."
"I am offering you the carrier surveillance radar architecture," Karan said. "Complete. Fully functional. The best maritime surveillance system any carrier in the world will have when the Orel and the Viraat are built. It will track more surface contacts at greater range with better discrimination than any system your Navy currently operates." He paused. "What I am not offering is the airborne intercept performance that the aircraft radar achieves."
"Why is that distinction operative?" Gorshkov said.
"Because the carrier's radar does not perform airborne intercept," Karan said. "Your carrier's air defense is performed by the aircraft on the carrier's deck. The carrier's own radar does surface search, threat detection at range, and fleet coordination. It does not perform the airborne intercept function. Giving you the airborne intercept algorithm for a system that doesn't use it solves no problem you have."
Gorshkov looked at him.
"You are making a technical argument," he said, "to avoid making a political one."
"Both arguments are valid," Karan said.
"The technical argument is correct," Gorshkov said. "The carrier's radar does not perform airborne intercept. The naval search radar does not need the airborne intercept algorithm." He paused. "However. The Soviet Navy has aircraft. Those aircraft have radars. The algorithm that makes your carrier aircraft radar perform as it does — that algorithm is of value in the aircraft application even if we agree it has no application in the ship's sensor suite."
"Yes," Karan said. "I know this."
"So," Gorshkov said, "the technical argument is a partial answer. The full answer requires the political one."
"The full answer," Karan said, "is that the airborne intercept algorithm is the reason that every aircraft Shergill Aviation builds will outperform its threat environment for the next fifteen years. Transferring it changes that. This is a strategic calculation, not a commercial one."
Gorshkov stood again.
He walked back to the window. He stood there for a long moment.
When he turned, his voice was different. Colder.
"Mr. Shergill," he said. "Let me tell you something about what you are proposing. You are coming to Severomorsk to offer me a commercial arrangement. The commercial arrangement funds a programme that I have been fighting for for thirty years. In exchange, you want nuclear propulsion technology — the most sensitive naval technology in the Soviet inventory. You want complete carrier construction knowledge. You want a hull built in our yards. You want a hundred of your workers embedded in our most sensitive shipyard."
He paused.
"And in exchange for these things — which represent a transfer of capability to India that the American government will spend the next twenty years trying to prevent — you are offering me a partial version of the technology that makes the exchange worth making."
Karan said: "The exchange worth making for me is what I've described. The question is whether it is the exchange worth making for you."
Gorshkov's eyes were flat.
"Tell me why I accept it," he said.
"Because the alternative is the March session cancels Orel," Karan said. "And in the March session without this arrangement, the budget argument wins because there is no counter to it. The strategic case — which you have won three times — does not address the budget argument. The BUMC funding addresses the budget argument. Without the BUMC funding, you are arguing strategy against mathematics. Strategy loses that argument in peacetime Politburo sessions."
He paused.
"With the BUMC funding," he said, "you are presenting a programme that is funded from outside the Planning Ministry's budget constraints. The Politburo's objection is removed. You argue strategy against no mathematics at all. You win."
Gorshkov was quiet.
"This is accurate," he said.
"Yes," Karan said.
"And Grechko," Gorshkov said. Marshal Grechko — the Defence Minister, the programme's most consistent opponent. "He will argue that sharing nuclear propulsion with a non-Warsaw Pact state sets a precedent."
"Grechko's argument is correct on the precedent question," Karan said. "The answer to him is not that the precedent doesn't exist. The answer is that India established the relevant precedent in May 1974 by detonating a nuclear device independently. India is already a nuclear state. The question is whether India's nuclear and strategic development proceeds with Soviet technical partnership or without it. Without it, India continues to build independently. With it, India builds in a direction that is at minimum non-hostile and at best strategically aligned."
He paused.
"The specific direction," he said, "depends on what India receives. Nuclear propulsion for a carrier is nuclear propulsion oriented toward maritime power projection. This is a strategic direction that does not threaten Soviet interests. It is a strategic direction that complicates American interests in the Indian Ocean. Grechko knows the difference."
Gorshkov was still.
"And the workers at Severodvinsk," he said. "One hundred Indians in a Soviet shipyard."
"Limited to carrier construction areas," Karan said. "No access to submarine construction. No access to weapons development. No access to intelligence facilities. The FSB — the Second Chief Directorate — specifies the boundaries. Each worker individually approved through Soviet security clearance. Any worker who fails the clearance is replaced."
"The KGB," Gorshkov said. He meant the correct organisation for this period.
"The KGB specifies and enforces the boundaries," Karan said. "I am not asking you to compromise your submarine programme for India's benefit. I am asking you to allow Indian workers to learn carrier construction alongside Soviet workers. These are categorically different things and the security apparatus can manage the distinction."
Gorshkov walked back to his chair.
He did not sit immediately. He stood behind it. He looked at Karan across the chair's back.
"The carrier surveillance radar," he said. "Complete. Everything except the airborne intercept algorithm."
"Complete," Karan said. "The processing architecture, the antenna design, the signal management software, the sea clutter rejection algorithms, the surface target discrimination, the over-the-horizon performance parameters. Everything the carrier's mission requires."
"And the combat management system."
"Complete. Both hulls — Orel and Viraat."
"And the propulsion."
"The VM-4 complete engineering package," Karan said. "Every document, every specification, every operational parameter, every maintenance procedure. The people at Vizag who build and maintain the Viraat's reactors will have the full documentation."
Gorshkov sat.
He said: "I am going to tell you what I am going to do, and then I am going to tell you what I want in return for doing it."
Karan was quiet.
"I am going to take this arrangement to the General Secretary," Gorshkov said. "I am going to present it as a commercial arrangement that solves the programme's funding problem while generating a strategic partnership with India. I am going to argue for the nuclear transfer on the grounds I have described. I am going to make the case that the arrangement proceeds." He paused. "I will do this because the alternative is Project Orel dies in March and everything I have built toward for thirty years dies with it. Not for five years. For a generation."
He looked at Karan with the flatness of a man stating a condition.
"In return," he said, "I want the airborne intercept algorithm."
Karan had been waiting for this.
He had known since he designed the arrangement that this moment would come. The negotiation that had just happened — the walk through the terms, the positions established, the partial refusal — was the negotiation before the negotiation. The real negotiation was this.
He said: "Tell me why."
Gorshkov looked at him. "You know why."
"Tell me your version," Karan said. "I want to hear it."
Gorshkov was quiet for a moment. Then:
"The Soviet Navy's aircraft," he said. "The MiG-23 naval variants. The Su-17M naval modification programme. These aircraft have capable airframes and poor radar performance relative to their Western equivalents. The processing approach that produces the engagement ranges your aircraft have achieved — if that approach is applicable to Soviet naval aircraft radar, the performance gap closes."
"That is accurate," Karan said.
"The performance gap is a strategic liability," Gorshkov said. "In the North Atlantic scenario — where Soviet naval aviation must contest American carrier air groups — the performance gap is a tactical disadvantage that has been accumulating for years. The processing architecture that produced your aircraft's performance closes that gap."
He paused.
"This is the real exchange," Gorshkov said. "Nuclear propulsion and a carrier hull — these are extraordinary. They are also things that India needs from us specifically and that we can withhold. The signal processing architecture is something we need from you specifically and that you can withhold. This is the point of parity in the negotiation."
"Yes," Karan said.
"So," Gorshkov said. "The algorithm."
Karan was quiet for a long moment.
He thought about what he had decided before he came to Severomorsk.
He had decided this. He had decided it because the analysis was honest: the airborne intercept algorithm in Soviet hands was a security risk of specific character. It would reach Soviet naval aviation. It would eventually reach Soviet ground-based air defense. The question of whether it would reach adversary hands beyond that — through intelligence channels, through the specific operational relationships of the Warsaw Pact — was not a question he could answer with confidence.
He had also decided that the Viraat by 1980 required giving Gorshkov something that Gorshkov actually needed. Not something useful. Something necessary.
He said: "I will give you the architecture, not the implementation."
Gorshkov was quiet.
"Explain the distinction," he said.
"The processing architecture — the specific methodology, the mathematical framework, the design principles — that transfers," Karan said. "The specific software implementation that runs on ISMC chips — the actual code, the specific optimisations that make our hardware perform — that does not transfer."
"The architecture without the implementation," Gorshkov said.
"The architecture is what allows your engineers to build toward the performance," Karan said. "Your engineers are excellent. With the architecture as the framework, your engineers can produce an implementation suited to Soviet hardware. It will not perform at the same level as our implementation on our hardware immediately. But the development path is clear. The fundamental breakthrough — the parallel processing approach that the Soviet computing programme has not yet arrived at — is transferred."
Gorshkov said: "This gives us the knowledge to build, not the thing itself."
"Yes," Karan said. "Which is what you actually need. You need the knowledge to build. You do not need my specific product — you need to understand the approach so your engineers can build your version of it."
"How long," Gorshkov said, "before Soviet engineers can produce a working implementation from the architecture you transfer?"
"Three to five years, depending on whether the fabrication process is advanced simultaneously," Karan said. "The architecture without the hardware progress is limited. The chip fabrication transfer and the architecture transfer together — three years to a working implementation at reduced performance. Five years to matching performance, assuming the Zelenograd programme successfully applies the 3-micron process."
Gorshkov absorbed this.
"You have calculated this," he said.
"Yes," Karan said.
"You have calculated how long it takes for the Soviet programme to produce an implementation of what you are transferring," Gorshkov said. "And you have decided that this timeline is acceptable."
"I have decided," Karan said, "that three to five years is sufficient time for the Viraat to be built and operational and for India's air wing to have established itself at sea before Soviet naval aviation achieves comparable performance."
Gorshkov looked at him.
There was a pause of a specific quality — the pause of a negotiator encountering the full dimension of the counterparty's preparation.
"You are twenty-four years old," Gorshkov said.
"Yes," Karan said.
"And you have calculated the timeline of Soviet radar development against the operational deployment of the Indian carrier," Gorshkov said.
"I have calculated what I need to give you to get what India needs by when India needs it," Karan said. "That calculation required modelling your development timeline. So I modelled it."
Gorshkov was very still.
"The architecture and the chip fabrication process," he said.
"Yes," Karan said.
"Both complete," Gorshkov said. "The architecture — the full mathematical framework, the processing approach, the design principles."
"Yes."
"And the carrier surveillance radar. Complete."
"Yes."
"And the combat management system. Complete."
"Yes."
"And you want the Viraat by 1980."
"Yes."
"That is an extraordinary demand," Gorshkov said.
"The funding makes it achievable," Karan said. "Severodvinsk has the capacity. The question is whether the programme is funded at the level that allows parallel construction on both hulls simultaneously. The BUMC funding structure supports parallel construction. Without parallel construction, 1980 is not achievable. With it, it is aggressive but achievable."
"Aggressive," Gorshkov said.
"By months, not years," Karan said. "The risk is in the fitting-out phase. The hull construction timeline is achievable. The aircraft systems installation, the reactor commissioning, the aviation systems — these are the schedule risks."
"The hundred workers," Gorshkov said. "In the fitting-out phase specifically."
"The workers are in every phase," Karan said. "Hull, propulsion, aviation systems. Specifically trained for the carrier application — not general shipyard workers, specialists in the relevant disciplines. Their presence reduces the schedule risk because the labour constraint on fitting-out is addressed."
Gorshkov was quiet.
He stood.
He walked to the window. He stood there for a long time — longer than the previous window moments, which had been assessment pauses. This was a decision pause.
When he turned, his expression was the expression of a man who has decided something and is now stating it.
"The arrangement," he said.
"Yes," Karan said.
"I accept the terms as modified," he said. "The radar architecture and chip fabrication — complete. The surveillance radar — complete. The combat management — complete. The nuclear propulsion — complete. The catapult systems — complete. The Orel blueprints. One hundred workers. The Viraat hull to Indian specification." He paused. "The target date of 1980 is accepted as the target. I commit to making it the programme's construction goal. I do not guarantee it against Soviet bureaucratic interference that is outside my control."
"Understood," Karan said.
"In exchange," Gorshkov said, "the BUMC funding — full programme amount, milestone structure, through Vnesheconombank."
"Yes."
"The architecture of the signal processing methodology," he said. "Complete. The mathematical framework."
"Yes," Karan said. "Complete."
Gorshkov looked at him.
"If the architecture is complete," he said, "and then Soviet engineers will produce an implementation within the timeline you have modelled."
"Yes," Karan said.
"You have accepted this because by the time they do, the Viraat is operational and India has established the carrier capability," Gorshkov said. "The strategic window is yours. The technology transfer is delayed by your timeline calculation — not by secrecy."
"Yes," Karan said.
A silence.
Gorshkov said: "This is the most sophisticated piece of technology negotiation I have conducted in thirty years of Soviet defence procurement."
He said it without warmth. As a technical assessment.
"The arrangement serves both sides completely," Karan said.
"It does," Gorshkov said. "Which is the most suspicious thing about it."
"The suspicion is appropriate," Karan said. "Both sides should verify every element of the arrangement independently before the documents are signed. I would be concerned if you were not suspicious."
Gorshkov looked at him.
"Tell me what you want the ship to be," Gorshkov said.
He said it differently from the way he had said anything else in the conversation — not as a negotiator, as an engineer. The negotiation was complete. Now there was something more interesting.
Karan produced a second document from his case. This one was not commercial — it was technical. Diagrams, specifications, the specific language of ship design.
He placed it on the table.
"The Viraat is eighty-five thousand tonnes displacement," he said. "The Orel specification is approximately ninety thousand. The reduction comes from removing the cruiser armament."
"The SAM batteries, the anti-ship missiles," Gorshkov said.
"Everything that is not aviation," Karan said. "Every tonne of displacement that is allocated to weapons systems duplicating what the air wing and the escort provide is a tonne not allocated to aircraft fuel, aircraft maintenance facilities, or aircraft."
"The Orel specification includes independent surface warfare capability," Gorshkov said. "In the Soviet operational concept, the carrier is part of a battle group where the carrier itself contributes to the group's air defense."
"The Indian carrier operates in a different threat environment," Karan said. "The Arabian Sea and the Bay of Bengal do not present the same air threat density as the North Atlantic scenario. The escort configuration for the Viraat's task group provides the surface defense. The air wing provides the air defense. The carrier provides nothing except aviation."
"This is the American design philosophy," Gorshkov said.
"It is the correct design philosophy for a carrier," Karan said. "The Americans learned this. They built the Essex class with heavy guns and removed them because the guns were wasted displacement. The Viraat begins with the correct conclusion rather than working backward from experience."
Gorshkov was quiet.
"The flight deck angle," he said. "Your document specifies twelve degrees."
"The Orel specification is eight degrees," Karan said. "At eight degrees, the angled deck is sufficient to prevent interference between catapult operations and arrested recovery. At twelve degrees, the separation is more generous. For a carrier where the air wing is developing its carrier qualification — where pilots are learning deck operations — the wider angle provides more margin."
He paused.
"The Indian Navy's carrier aviation programme begins with the Viraat," he said. "The crews learning arrested landings on the Viraat are learning on the Viraat because there is no other way to learn. The margin for error in the initial years must be more generous than the margin required by experienced air wings."
Gorshkov studied the diagram.
"The sponsor structure at twelve degrees," he said. "This requires modification to the Orel hull form at the aft flight deck section."
"Yes," Karan said. "The structural modification is defined in section three of the document. The hull below the flight deck sponsor is reinforced to support the different angle. The modification affects approximately three thousand tonnes of structural steel in the aft section. The rest of the hull is Orel-standard."
"Three catapults," Gorshkov said. He was reading the specification. "Two on the angled deck, one on the bow."
"Two on the angled deck for simultaneous launch operations during recovery," Karan said. "The bow catapult for surge capacity. Three-catapult operations allow the carrier to sustain a higher launch rate during high-intensity strike operations."
"The steam system for three catapults," Gorshkov said. "The accumulator capacity. This is a significant addition to the ship's utility steam requirement."
"The document addresses this in section five," Karan said. "The steam system design is shared with the Orel — both carriers benefit from the engineering work on three-catapult steam supply. The modification is the accumulator sizing and the distribution piping. Not a fundamental redesign."
Gorshkov looked at the propulsion section.
"Two VM-4 reactors," he said.
"Same configuration as the Orel," Karan said.
"The propulsion documentation transfer," Gorshkov said. "This is the element that requires the General Secretary's personal signature. There is no mechanism to transfer this without it."
"I know," Karan said.
Gorshkov absorbed this.
"Yes," he said. "This is how it must be stated."
He turned back to the specification.
"The hangar," he said. "Sixty-aircraft designed capacity. Your document says the initial air wing will be smaller."
"The Viraat will not have sixty aircraft when it commissions in 1980," Karan said. "India's carrier aviation programme is beginning. The first years will see a smaller air wing building toward capacity. The hangar, the catapults, the arresting gear — these are designed for sixty aircraft at full operating tempo. When India's air wing has sixty aircraft qualified for carrier operations, the ship is ready for them."
"Full combat load," Karan said. "Unlike ski-jump launch, which forces a weight penalty."
Gorshkov studied the document.
"The island," he said. "Your specification reduces the island size significantly relative to Orel."
"The Orel island carries command and control capacity appropriate for a ship designed as the flag of a carrier battle group in contested waters," Karan said. "The Viraat is not designed as a fleet flagship. The island is sized for aviation direction and ship operations. The space freed by the smaller island is usable deck area."
"The aviation direction capability," Gorshkov said. "The Viraat's island must support carrier-controlled approach for recovery operations in poor visibility."
"Section seven," Karan said. "The approach radar and the CCA equipment — both in the island structure. The command function is reduced; the aviation control function is preserved."
Gorshkov closed the specification document.
He looked at Karan.
"1980," he said.
"1980," Karan said.
"Severodvinsk has delivered major hulls on this timeline before," Gorshkov said. "Not carrier class. The cruiser programme — the Kirov — has had compressed timelines. The organisational structure for parallel construction exists."
"The BUMC funding provides the budget for parallel construction on both hulls simultaneously," Karan said. "Orel and Viraat on the same slipway schedule. The Viraat's commercial funding does not compete with the Orel's budget allocation — it supplements it."
"The Planning Ministry," Gorshkov said. "They will want to understand why parallel construction of a foreign-funded hull serves Soviet interests."
"The hull is built in Soviet yards by Soviet workers," Karan said. "The technology transfer fills gaps in Soviet capability. The commercial funding reduces the budget burden on the overall programme. The strategic benefit is a partner relationship with India rather than a client relationship. The Planning Ministry's interest is served by all four of these."
Gorshkov was quiet.
"You have an answer to every objection," he said.
"I have been preparing this arrangement for long time," Karan said. "Every objection that is predictable has an answer. If there are objections I have not prepared, we will address them in March."
"The Politburo's Planning Ministry economists have been using upfront cost comparison," Gorshkov said. "Catapult is more expensive to build, therefore ski-jump is preferred."
"The lifecycle analysis shows the full cost over the hull's operating life," Karan said. "Including the operational efficiency penalty of ski-jump operations, and the eventual modification or replacement cost when the ski-jump hull cannot operate the next generation of aircraft. Over forty years, the catapult hull is substantially cheaper."
"This is the argument I have been unable to make because the data has not been assembled," Gorshkov said.
"I have assembled it," Karan said. "Using American, British, and French carrier programme data. Publicly available sources. Your economists can verify every number independently."
Gorshkov looked at him.
"You went to Severomorsk," he said, "with an argument for my Politburo presentation already assembled."
"I went to Severomorsk," Karan said, "with everything needed to get a yes."
Gorshkov poured the tea himself.
This was different from the earlier service — a gesture of privacy rather than protocol. He poured it because the next part of the conversation was the kind that required the attendant not to be in the room.
He handed a glass to Karan.
He sat back.
"The Indian Navy," he said. "What it becomes with this carrier."
"A different navy from what it currently is," Karan said.
"Obviously," Gorshkov said. "I mean specifically. The Viraat operational in 1980 — what changes?"
"India becomes able to project air power into the western Arabian Sea at range," Karan said. "Specifically, the capacity to sustain air operations over the Gulf approaches, over the Strait of Hormuz if required, over the waters relevant to India's petroleum supply lines."
"The Gulf," Gorshkov said.
"The Arabian Sea approaches to the Gulf," Karan said. The supply line matters. A carrier that can operate in the western Arabian Sea is a carrier that can contest any attempt to restrict India's access to that supply line."
"Any attempt by whom," Gorshkov said.
"By anyone who decides India's access to Gulf petroleum can be used as a pressure instrument," Karan said.
Gorshkov was quiet.
"The Bay of Bengal," he said.
"The eastern maritime approach to India," Karan said. "The Strait of Malacca. The access routes through which Indian Ocean trade moves to East Asia. As China's maritime interests develop in the coming decades, the Bay of Bengal becomes a contested space. India's presence in that space requires the capacity to operate at range."
"You are describing a three-decade planning horizon," Gorshkov said.
"The ship that commissions in 1980 operates until 2020," Karan said. "The planning horizon for the carrier programme is the ship's operational life, not the year it enters service."
Gorshkov said: "And the Soviet Navy's position in this picture."
Karan looked at him.
"The Soviet Navy cannot be everywhere," he said.
"No navy can be everywhere," Karan said. "The American Navy approaches this through alliance structure — NATO, the Pacific alliances, the Gulf partnerships. Each partner covers a portion of the maritime space so the American Navy can concentrate in the decisive theatres." He paused. "An Indian Navy that covers the Indian Ocean is an Indian Navy that covers the Indian Ocean on India's terms, not on Soviet terms. This is the important distinction. Not a Soviet client covering the space on Soviet direction. A partner with independent interests that happen to align."
"Aligned how," Gorshkov said.
"India's maritime interests and Soviet maritime interests do not conflict in the Indian Ocean," Karan said. "India's interest is preventing any single external power from dominating the Indian Ocean trade routes. The Soviet interest is preventing American dominance in the Indian Ocean. These are not identical interests, but they point in the same direction."
Gorshkov said: "The American Seventh Fleet's position in the Bay of Bengal."
"The 1971 deployment," Karan said. "The Enterprise battle group. India understands what that deployment meant. An India with a carrier in the Indian Ocean by 1980 has a different answer to a deployment of that kind than India without a carrier."
Gorshkov was quiet.
"Not the same answer," he said. "The Viraat alone is not equivalent to an American carrier battle group."
"No," Karan said. "But the Viraat with its air wing changes the calculation. The calculation the Americans made in 1971 was: India cannot respond. That calculation changes with a carrier. Not to: India can defeat us. To: India's response costs more than we expected."
"Deterrence," Gorshkov said.
"Deterrence," Karan said. "Not capability parity. Cost imposition."
Gorshkov stood.
He walked to the window.
He stood there looking at the Kola Bay for a long time — longer than any previous window pause. This was a different quality of looking. He was not assessing or calculating. He was — Karan thought — experiencing something.
Gorshkov turned.
"I want to ask you something," he said. "Not about the arrangement."
Karan waited.
"Thirty years," Gorshkov said. "Thirty years I have been arguing for the carrier that Project Orel is designed to be. Not against the institutional preference for submarines, which I understand and respect — submarines are the correct priority for a navy defending Soviet territory in the North Atlantic. Against the institutional preference for half measures. For cruisers with aircraft. For ski-jump carriers that cannot operate full-capability aircraft. For everything that looks like a carrier from a distance and is not a carrier when you need it to be one."
He paused.
"You read the papers," he said. "You understand the argument. You have come here with a proposal that saves the argument by solving the problem I could not solve." He looked at Karan directly. "Why? What does Shergill Industries actually want from this arrangement?"
Karan said: "The Viraat. The nuclear propulsion. The catapult knowledge. The construction experience. These are what India needs."
"You could get these from the Americans," Gorshkov said. "At a price — political, diplomatic — but you could build toward American carrier technology over time. You are here instead. Why?"
Karan looked at him.
"The Americans," he said, "would structure the technology transfer so that India's carrier capability is dependent on continued American cooperation. Their standard approach — the technology requires support, spare parts, upgrade pathways that run through American sources. The capability is real but the dependency is also real. India has spent forty years acquiring equipment on those terms. The dependency has been a constraint at every moment of strategic decision."
He paused.
"The Soviet arrangement," he said, "provides complete technology. The propulsion documentation is complete. The catapult documentation is complete. The Viraat is built in Soviet yards with Indian workers who learn the construction from inside it. When the Viraat commissions, India can maintain it, modify it, and operate it without requiring Soviet cooperation for ongoing support."
"The same independence you have built in your aerospace programme," Gorshkov said.
"Yes," Karan said.
"You are applying the same principle to the naval programme," Gorshkov said. "Build it completely or don't build it."
"If India builds a carrier that requires permanent American or Soviet technical support for operation, India has built a carrier with a dependence switch that the supplier controls," Karan said. "The moment India needs to use the carrier in a situation the supplier finds inconvenient, the switch becomes a constraint. India's experience with this pattern is sufficient."
Gorshkov was quiet.
"This is why," he said slowly, "you are transferring the signal processing architecture to us rather than the implementation."
Karan looked at him.
"We transfer the knowledge to build," Karan said. "Not the product itself. The knowledge to build produces independence. The product itself produces dependency."
"You are applying," Gorshkov said, "the same principle to what you are giving me as to what you are receiving."
"Yes," Karan said.
Gorshkov sat down.
"You have built an arrangement," he said, "in which both sides acquire independence."
"Both sides acquire what they need," Karan said. "What both sides need, in this case, is the capacity to build rather than the specific product."
Gorshkov looked at the window.
The light outside was going — it was after two, and the four hours of functional daylight were ending. The ships in the anchorage were developing the specific quality of large dark shapes in failing light.
He said: "The Viraat commissions in 1980. India's carrier aviation programme begins. The Indian Ocean situation changes." He paused. "In 1985, when the Orel is fully operational and India's carrier has been at sea for five years — what is the strategic picture?"
"The Indian Ocean has two carrier-capable navies instead of one," Karan said. "The American Pacific and Indian Ocean posture must account for the Indian presence in a way it currently does not need to account for. The Soviet presence in the Indian Ocean — through Vladivostok and the Pacific Fleet — is supplemented by an Indian presence that does not require Soviet support." He paused. "The American calculation about the Indian Ocean becomes more complex."
"More complex in our favour," Gorshkov said.
"More complex in India's favour," Karan said. "Which tends to align with more complex in the Soviet favour in the specific theatre. Not everywhere. In the Indian Ocean specifically."
Gorshkov was quiet.
"The General Secretary," he said, "will want to know whether the arrangement creates an Indian partner or an Indian competitor."
"The Indian Ocean is not a theatre of Soviet-Indian competition," Karan said. "The Soviet Navy's primary competitive focus is the North Atlantic and the Pacific. India's maritime focus is the Indian Ocean. The theatres do not overlap in a way that creates competition."
"For now," Gorshkov said.
"For the planning horizon of this arrangement," Karan said. "Twenty years. Beyond twenty years, the world is different in ways I cannot predict and neither can you."
Gorshkov said: "An honest answer."
"The alternative is a diplomatic answer," Karan said. "I am not here to give you diplomatic answers."
Gorshkov almost smiled.
Gorshkov poured a second glass of tea.
He said: "The formal documents. Timeline."
"Two weeks — the complete financial proposal and milestone structure for the Vnesheconombank account, and the lifecycle cost analysis for your Politburo presentation," Karan said. "Simultaneously — the Vizag worker list, names and specialisations, for the KGB security screening."
"How many names?" Gorshkov said.
"One hundred and twelve," Karan said. "I have included twelve additional names to provide the KGB with the clearance pool they need to select one hundred approved workers. If more than twelve are declined, I provide additional names."
"The skills distribution," Gorshkov said.
"Propulsion system technicians — twelve. Hull plate fabricators — twenty. Pipe fitters for the nuclear system circuits — eight. Aviation systems specialists — fifteen. Electrical installation workers — twenty. Arresting gear and catapult installation specialists — ten. Radar and electronics installation — eight. The remaining nine are general trades — scaffolding, crane operation, logistics." He paused. "The distribution is in the worker list. The propulsion technicians are the most critical category — they need to understand the VM-4 installation from the inside."
"Twelve propulsion technicians," Gorshkov said.
"Twelve is sufficient to constitute institutional knowledge when they return to Vizag," Karan said. "Enough people that the knowledge is distributed rather than concentrated in two or three individuals. If two or three people hold all the knowledge, the programme is vulnerable to losing those people."
"The knowledge distribution argument," Gorshkov said. "You think about this in terms of programme resilience."
"I think about every programme in terms of what happens if the three most important people are unavailable," Karan said. "Single points of failure are eliminated in system design. They should be eliminated in knowledge design also."
Gorshkov absorbed this.
"The joint technical committee," he said.
"Monthly meetings during construction," Karan said. "Two Indian representatives — a propulsion engineer and an aviation systems engineer — with standing access to the construction programme. Not KGB-restricted — working technical access, within the security boundaries."
"Severodvinsk's security arrangements," Gorshkov said, "will require these representatives to be credentialed and monitored. The credentialing process takes three months."
"Start it now," Karan said. "The two representatives I am nominating are identified in the worker list. If they are credentialed early, the committee is operational from the first month of construction."
Gorshkov said: "You have anticipated the credentialing timeline."
"I assumed three months," Karan said. "If it is longer, the committee starts later. Either way, the nomination is in the list."
Gorshkov looked at the diagram of the Viraat's flight deck angle.
He said, without looking up: "The S-27N. The carrier variant of your aircraft. Full combat load off the catapult."
"Full combat load," Karan said. "Not the weight penalty of ski-jump launch. Every weapon at full fuel."
"The range advantage of full fuel," Gorshkov said.
"The strike radius extends to the full capability of the aircraft," Karan said. "The catapult is why the carrier aircraft is not a compromise. Without the catapult, the aircraft that operates off the carrier is less capable than the aircraft that operates from the land. With the catapult, the aircraft is the aircraft."
Gorshkov set down the diagram.
"What you are describing," he said, "is the fundamental argument I have been making to the Soviet Navy for thirty years. The carrier is only a carrier if it can launch aircraft at full capability. Everything else is a ship with aircraft on it."
"Yes," Karan said.
"The Kiev class," Gorshkov said, "is a ship with aircraft on it."
"Yes," Karan said.
Gorshkov was quiet.
"The Orel," he said.
"The Orel is a carrier," Karan said.
"Yes," Gorshkov said. "It is."
A pause.
He picked up the financial proposal document.
He held it without looking at it.
He said: "Mr. Shergill. In thirty years of Soviet naval development, I have not been in a room where the person across from me fully understood the argument and came with a solution to the problem rather than a negotiating position."
"I came with a negotiating position also," Karan said.
"You came with a solution," Gorshkov said. "The negotiating position was incidental. The solution was primary." He paused. "This is unusual."
"I spent two years building the solution," Karan said. "It would have been wasteful to spend that time and then come with a position rather than the thing itself."
Gorshkov stood.
He walked to the small table.
He extended his hand.
Karan stood.
He shook it.
The handshake was not the assessment handshake of the meeting's beginning. It was the handshake of an agreement — the specific grip of a man who was committing to something he understood.
"We have an arrangement," Gorshkov said. "In principle. The General Secretary approves the nuclear transfer. The Politburo approves the programme continuation. The formal documents follow."
"Yes," Karan said.
"Be prepared for specific technical questions from the Planning Ministry economists," Gorshkov said. "They are not fools. They will have read the document before the session."
"I will be prepared," Karan said.
Gorshkov looked at him.
"You are confident," he said.
"I am prepared," Karan said. "Confidence is a different thing."
Gorshkov said: "The distinction is correct."
He let go of the handshake.
"The INS Viraat," he said.
"The INS Viraat," Karan said.
"1980," Gorshkov said.
"1980," Karan said.
Gorshkov walked him to the door.
At the door, he stopped.
"One question," he said. "Not a negotiation question."
"Ask it," Karan said.
"Project Orel," Gorshkov said. "When you read the specification — the technical specification, the design documentation — what do you see?"
Karan looked at him.
He thought about the question. Not the answer he would give in a presentation. The actual answer.
"I see," he said, "a ship that has been designed correctly. Not optimally for every mission — no ship is optimal for every mission. Correctly for the mission it is designed for. The catapults are correct. The angled deck is correct. The nuclear propulsion is correct. The design decisions reflect an understanding of what a carrier must be rather than a compromise toward what a carrier can be built as." He paused. "I see the work of an engineer who spent thirty years building toward the correct answer and who has, in this design, produced the correct answer."
Gorshkov was quiet.
"And why are you funding it," he said.
"Because it is the right ship," Karan said. "And because funding the right ship when it is about to be cancelled for the wrong reasons is the correct response to the right ship almost being cancelled for the wrong reasons."
Gorshkov looked at him for a long moment.
"The right ship," he said.
"Yes," Karan said.
"The Viraat is also the right ship," Gorshkov said.
"The Viraat is the right ship for India," Karan said. "The same engineering principles. Different specification. Same correctness."
Gorshkov nodded.
He opened the door.
Karan walked out.
The car on the coastal road. The same grey dying light. The Kola Bay outside the window.
He sat.
He did not review the negotiation. The negotiation was complete and what was complete did not need reviewing. He thought about what it produced.
Nuclear marine propulsion — the complete VM-4 engineering package. The catapult systems. The Orel blueprints. One hundred workers at Severodvinsk learning carrier construction from inside it. The INS Viraat — India's carrier, built in Soviet yards to an Indian specification, to be operational by 1980.
The signal processing architecture — the full mathematical framework, transferred to Gorshkov's radar engineers. The implementation not transferred. The knowledge to build versus the product itself.
He thought about the chain that had produced this moment.
The ISMC chips had given him something worth trading. The Bombay High had given him the commercial foundation. The S-27's combat performance had established India's technological credibility. The nuclear test had established India's strategic independence. Each had been necessary. Each had raised the value of what India had to offer until the offer was worth what India needed in return.
He thought about the Viraat.
The officers who would command her were young lieutenants now, learning their trade on the ageing Vikrant. They would be commanders and captains by 1980. They would have what the generation before them had been promised and never received.
He thought about the Indian Ocean.
The specific quality of an ocean named for a country that could not project power onto it. The anomaly of that — India's ocean, India without a real carrier in it. The Vikrant doing what it could, which was less than what was needed, known to be less by everyone who used it.
Not after 1980.
He opened his notebook.
He wrote: January 15, 1975. Severomorsk. The arrangement is agreed. Project Orel proceeds. The Viraat will be built.
He looked at what he had written.
Then he wrote: The negotiation went where it needed to go. The architecture transfers — not the implementation. Gorshkov will have Soviet engineers working on the Soviet implementation within three years. By the time they have a working system, the Viraat will have been at sea for two years. The window is sufficient.
He paused.
1980. The INS Viraat commissions. India becomes able to project air power into the western Arabian Sea. The Bay of Bengal. The approaches to the Strait of Malacca. The specific spaces where India's interests require presence and India has not had the instrument for presence.
He paused again.
Gorshkov has been right about carriers since before I was born. The thing he has been right about will be built. Both versions of it — the Soviet one and the Indian one. This is the correct outcome.
He closed the notebook.
Below the aircraft — the transport was climbing out of the Severomorsk airfield, the Kola Bay falling away under the wings — the ships of the Northern Fleet arranged themselves in their anchorage patterns, the frigates and destroyers and submarine tenders and, in the far corner of the bay, the space marked on the charts as the construction slip — the space where Project Orel would be laid down, where beside it the INS Viraat would take shape over the next five years, hull by hull, frame by frame, until the two ships that Gorshkov had spent thirty years trying to build and that Karan had spent two years making possible slid down the ways into the Kola Bay and prepared to go to sea.
The aircraft banked.
The bay disappeared.
The Barents was ahead — the grey water stretching south toward Norway and then toward warmer latitudes and eventually toward the Arabian Sea and the Bay of Bengal and the Indian Ocean that had no country's name to itself yet but that, by 1980, would have India in it in a way that changed what India's name meant.
He closed his eyes.
He did not sleep.
He was already thinking about the March Politburo session and what Grechko would say and what the answer would need to be.
The work did not pause.
It never did.
End of Chapter 178
(india cannot make its first aircraft carrier wthout any experience in 3 or 5 years ,also this orel class carrier is gonna panic usa)
Project Orel / INS Viraat — Agreement Summary, 15 January 1975
Parties:
Shergill Industries / BUMC — Karan Shergill
Soviet Northern Fleet — Admiral of the Fleet S.G. Gorshkov
What India Provides:
Full programme funding for Project Orel through Vnesheconombank project account, milestone-verified disbursements. Signal processing architecture — complete mathematical framework and design principles (NOT the specific software implementation). Carrier surveillance radar system — complete hardware and maritime-mission software. Ganesh-class mission computing for combat management — both Orel and Viraat.
What the Soviet Navy Provides:
VM-4 nuclear marine propulsion — complete engineering documentation, all specifications, maintenance and operational procedures. Steam catapult systems — full design, installation, operational procedures. Project Orel complete blueprints and design documentation. One additional carrier hull — built to Viraat specification at Severodvinsk, incorporated into Orel programme. Construction access — 100 Indian workers embedded at Severodvinsk, carrier construction areas only, for construction duration.
Architecture vs. Implementation — The Core Negotiation:
Gorshkov demanded the full signal processing methodology including airborne intercept algorithm. Final agreement: full mathematical architecture and design principles transfer. Soviet engineers build their own implementation from the architecture. India retains its specific implementation. Soviet radar development timeline: 3-5 years from architecture transfer to working system. Viraat operational: 1980. Window in India's favour: 2+ years.
INS Viraat Specification:
Displacement: 85,000 tonnes. No cruiser armament. Three steam catapults. 12-degree angled deck. Two VM-4 reactors. Hangar designed for 60-aircraft operating tempo. CATOBAR — full catapult-assisted takeoff and barrier arrested recovery. Target commissioning: 1980.
Next Steps:
Financial proposal and lifecycle cost analysis: 2 weeks. Vizag worker list (112 names, KGB screening): 10 days. March Politburo session: Gorshkov presents, Karan available for technical questions. Expected approval: April-May 1975. Construction commencement: Q3 1975. INS Viraat commissioning: 1980.