Chapter 180 - Chapter 173: The Gun That Answers Back

Chapter 173: The Gun That Answers Back

9 October 1974 — Shergill Advanced Projects Division, Gorakhpur

The Advanced Projects Division occupied the northwest corner of the Shergill Industries compound, and it had a specific quality that distinguished it from every other building in the complex.

Every other building in the compound had a clear purpose visible from the outside. The Design Bureau had its wind tunnel intake visible from the road. The ISMC facility had its clean room ventilation array on the roof. The steel plant had its smelting stacks. The Defence compound had its proving ground range visible to the east. You could tell what a building was for by looking at it.

The Advanced Projects Division looked like nothing.

A long, low building of brick and reinforced concrete, windows that were smaller than the building's scale required, a single entrance that was not marked with the division's name — only a number, building 7, which was the administrative designation for a building that had been given a neutral identifier specifically because the alternative was a sign that said what was inside, and what was inside was not for signs.

What was inside was the team that had built the Arjuna.

Not the whole team — the Arjuna had required hundreds of people across multiple facilities, the steel division and the propulsion laboratory and the ordnance workshop and the fire control integration group. But the core. The people who had originated the design decisions. The people who had argued about the floor and the armour and the gun and the fire control and the night vision and the hundred other specific things that were now the Arjuna and that would, within fourteen months, be arriving at the Indian Army's armoured formations as the first production vehicles.

The team had not been dissolved after the Arjuna's first flight — the first drive, rather, since tanks drove rather than flew, which was a distinction that Vikram Iyer had made once at a team meeting and that had produced a specific quality of silence that indicated it was funnier to the person who said it than to the people who heard it. The team had been maintained because Karan had a philosophy about teams that had produced results: the team that built something was the team that understood it, and the team that understood it was the team that could make the next thing.

The next thing was why he was calling them to Building 7 on the morning of October 9th.

He arrived at 7 Am(blud not gonna sleep)

The building's entrance had a small anteroom — not a lobby, just the specific transitional space between outside and inside that gave the security system its function. He badged through, walked the corridor, and came to the main conference room at the building's centre.

The conference room was the largest space in the building. It had a full-width table and enough chairs for sixteen and a projection screen at the north end and two whiteboards, one of which was already covered in equations from whatever the previous week's work had been on — Karan read the equations without meaning to and recognised them as trajectory calculations, specifically the trajectory of a large-calibre artillery projectile, which was either a coincidence or a sign that someone in this building had been following the same train of thought he had.

He looked at the equations for a moment.

Then he went to the whiteboard and erased them.

He wanted to start from nothing today.

They arrived between seven and seven-thirty.

Dr. Anand Krishnaswamy came first, because Krishnaswamy always came first — it was a professional habit so consistent that Karan had come to treat his arrival time as a clock calibration rather than a personal choice. He was fifty-two years old, the technical director for the Arjuna's armament systems, a man who had spent thirty years in defence metallurgy and ordnance engineering at DRDO before Karan had recruited him in 1972 with an offer of resources and authority that DRDO could not match. He had the specific quality of a very experienced engineer in a senior role: he was not the most mathematically sophisticated person in any room he entered, and he had long since stopped needing to be, because his value was not in the specific calculation but in the understanding of which calculation mattered.

He looked at the erased whiteboard.

He looked at Karan.

"The trajectory equations," he said.

"I erased them," Karan said.

Krishnaswamy sat down without comment. He had been in enough meetings at this building to understand that Karan's choices at the start of a meeting — what was on the board, what was not, who was in the room before anyone arrived — were the opening statements of the meeting's argument. He filed the erased equations and waited.

Suresh Nair came in at seven-oh-three with a cup of tea and a notebook. He was forty-eight, the technical director for propulsion, and he had been the principal engineer for the Arjuna's SDG-1000 engine — the 1,000-horsepower powerplant that gave the Arjuna its mobility numbers. He was from Kerala, had studied at IIT Madras, and had the specific quality of mechanical engineers from that programme in that era: precision of thinking that had become so habitual it manifested as a kind of economy of movement, as though physical imprecision would compromise the mental precision that was his primary tool.

He saw Krishnaswamy sitting and sat beside him.

Dr. Meenakshi Subramaniam came in at seven-ten. She was forty-four, the lead for armour development, and she had brought the ceramic processing knowledge from her previous work at a materials research institute that had been conducting fundamental ceramics science for industrial applications. What she had contributed to the Arjuna was the specific innovation of the bonding interface between the steel face plate and the ceramic layer — the specific chemistry that made the composite armour behave as a single material under dynamic loading rather than as two materials in contact. This distinction — whether the layers acted together or separately under impact — was the difference between the armour working and the armour failing, and she had solved it.

She was carrying a large coffee and a stack of folders that she put on the table and then looked at, appearing to realise that bringing folders to a meeting whose agenda was unknown was either prescient or absurd and not being sure which.

She put the folders at the end of the table and sat down.

Major (Retired) Balram Singh Mehta came in at seven-fifteen.

He was thirty-seven, which made him young relative to several of the people in the room, but his presence was not young in the way that presence communicated age — it was the presence of someone who had been in serious situations and had not been diminished by them, which was the specific quality that combat experience sometimes produced and sometimes did not, depending on the person. He had been the crew systems lead for the Arjuna — the person who had stood in front of Karan's first drawing in December 1971 and said the floor is wrong and whose requirements had driven the design from that moment. He had also been the person for whom Bewoor had recommended accelerated promotion, which was going through the system and which Mehta had been notified about and had received with the specific expression of someone who was not sure whether he was pleased or simply grateful that the work had been recognised by someone who understood it.

He sat at the table's centre, which was the seat he always took, the spatial habit of someone who had spent years commanding from the centre of formation.

Brigadier (Retired) Harshvardhan Singh came in at seven-twenty. He was sixty-one, the oldest person in the room, a former armoured brigade commander who had been in the Army for thirty-five years before he retired and joined the Advanced Projects Division as the senior operational advisor. His function was to translate between what engineers proposed and what soldiers experienced — to say, from the authority of someone who had commanded armoured formations in two wars, whether what the engineers were building was what the Army actually needed or what the engineers thought the Army needed, which were not always the same thing.

He sat at the table's far end and looked at Karan with the specific look of a man who had been in enough planning rooms to know when the person running the meeting was carrying something significant.

Dilip Bose and Ravi Shankar Pillai came in together at seven twenty-five — Bose the suspension lead, Pillai the engine development engineer, both of them mid-conversation about something that ended at the doorway with the specific efficiency of a conversation whose participants had agreed to continue it later. They took adjacent seats.

Vikram Iyer and Parimal Ghosh came last, at seven twenty-eight, both slightly out of breath, which suggested they had been at the experimental ordnance workshop at the south end of the compound and had walked fast rather than been late. Iyer was thirty-eight, the armament engineering lead who had designed the Shatrujit gun barrel's rifling geometry — or rather its lack thereof, since the Shatrujit was a smoothbore. Ghosh was thirty-four, the newest member of the core team, who had joined from the Indian Institute of Technology's optical engineering programme to work on the thermal imaging component of the Arjuna's night vision system.

All nine of them.

The team that had built India's best tank.

Karan looked at them across the table.

He did not begin immediately. He looked at them the way he began significant meetings — with a moment of complete attention, the specific quality of regard that said: I know who you are and I know what you have done and this conversation is between people who have earned the right to say difficult things to each other.

Then he said: "Thank you for coming on short notice. What I'm about to tell you is classified at a level that does not leave this room. Not to your teams, not to your families, not to anyone in the company who is not in this room. I'm asking for that explicitly and I'm asking you to treat it seriously."

Nobody spoke. Nobody needed to — the statement was received without the clarifying questions that people asked when they were uncertain about what they were agreeing to. These were people who understood classification.

"I received a signals intelligence summary three days ago," Karan said. "The summary was provided through a channel that I am not going to specify. The content is specific and actionable."

He opened his notebook to the page he had written on five days ago.

He looked at it for a moment, not because he needed to read from it, but because writing it down and reading it one more time was the specific preparation he did before saying things that were going to change the work of the people in front of him.

"The United States Army is in advanced stages of contracting for the production of a counter-battery radar system," he said. "The system is designated AN/TPQ-37. It is called a Firefinder."

He paused.

"Tell me what you know about counter-battery radar," he said. He said it to the room generally, but he was looking at Krishnaswamy, because Krishnaswamy was the armament technical director and counter-battery radar was armament territory.

Krishnaswamy set his pen down.

"Counter-battery radar," he said, "is a system that detects the trajectory of an incoming artillery round, computes the trajectory backward, and determines the origin point of the firing battery. The purpose is to locate enemy artillery so that friendly artillery can suppress or destroy it." He paused. "The technical challenge is detection speed and accuracy — you have to detect the projectile in flight, which is milliseconds, and compute the back-azimuth with sufficient accuracy to direct counter-battery fire to the actual battery position rather than a general area." He paused again. "A system that does this reliably changes the tactical character of artillery warfare fundamentally."

"How?" Harshvardhan Singh said. He said it as a general officer's question — not as a request for technical detail but as a request for the operational implication.

"If you have counter-battery radar," Krishnaswamy said, "and your opponent has artillery but not counter-battery radar, you can locate and suppress his artillery every time he fires. He fires once and you know where he is. You fire at him. He fires again and you fire at him again. His battery has a life expectancy measured in minutes after firing." He paused. "A force with counter-battery radar against a force without it is a force that can use its artillery freely and deny the opponent the same freedom."

"Which makes artillery the decisive system in ground combat," Harshvardhan Singh said.

"Correct," Krishnaswamy said. "More decisive than it already is."

"The AN/TPQ-37," Karan said. "The signals summary indicates that China is in negotiation with the United States for the purchase of twelve AN/TPQ-37 systems."

The room was completely silent.

Not the polite silence of people receiving information. The specific silence of experts who have just been told something that their expertise allows them to understand fully and immediately.

Mehta said, very quietly: "Twelve systems."

"Twelve," Karan said. "The acquisition timeline in the summary is eighteen to twenty-four months. The systems would be operational in Chinese Army service within two years."

Harshvardhan Singh had his hands on the table. He was looking at them. He was a former brigade commander who had planned armoured operations in the Himalayan sector and who understood, from that experience, what the terrain between India and China looked like and what artillery meant in that terrain.

He looked up.

"Mr. Shergill," he said. His voice was level with the specific levelness of a very experienced officer processing threat information.

"Sir," Karan said.

"Where would twelve AN/TPQ-37 systems be deployed?" Harshvardhan Singh said. He was asking it as a rhetorical question — the answer was in the question. But he asked it to make the answer explicit.

"The most likely deployment," Karan said, "is the western and eastern operational commands of the People's Liberation Army Ground Force. The units that face India across the Line of Actual Control in the western sector — Aksai Chin and Ladakh — and the eastern sector, Arunachal Pradesh." He paused. "Artillery in mountain terrain is not the same as artillery in plains terrain. In mountain terrain, artillery is frequently the only system that can engage targets at the distances and angles that mountain geography creates. Tanks cannot go where shells can go. Aircraft face weather constraints that artillery does not. In the Himalayan sector, the army that controls the artillery battle controls the battle."

"And a Chinese Army with AN/TPQ-37 Firefinders," Harshvardhan Singh said.

"Can locate every Indian artillery piece that fires," Karan said. "Within minutes of the first round leaving the barrel."

The room was very quiet.

Suresh Nair said: "What is the Firefinder's detection accuracy?"

"The specification is plus or minus fifty metres at ten kilometres range," Karan said. "At twenty kilometres, plus or minus two hundred metres. The accuracy degrades with range, but at the engagement ranges characteristic of the Himalayan sector — where artillery positions are constrained by terrain to specific valleys and ridgelines — fifty metres at ten kilometres is sufficient to direct counter-battery fire to the battery position with lethal effect."

"What is the current Indian Army artillery range?" Meenakshi Subramaniam asked. She said it with the directness of a scientist identifying the precise question that the technical briefing needed to answer.

Karan looked at her.

"The Indian Army's primary artillery piece is the 105mm L70 field gun," he said. "British-designed, produced under licence at the Ordnance Factory. Maximum range of approximately seventeen kilometres. The Indian Army also operates the Soviet BM-21 multiple launch rocket system, with a range of approximately twenty kilometres." He paused. "The Indian Army's maximum effective artillery range, across its current inventory, is twenty kilometres. Against an opponent with counter-battery radar, every Indian artillery battery that fires — at ranges up to twenty kilometres — is locatable within seconds and targetable for counter-battery fire."

"And if the opponent has artillery that reaches beyond twenty kilometres," Harshvardhan Singh said.

"Then the opponent can locate Indian batteries at their maximum range," Karan said, "and engage them with artillery that the Indian batteries cannot reach in return."

"A range asymmetry," Nair said.

"A lethal range asymmetry," Karan said. "In the Himalayan sector, a Chinese battery at twenty-five kilometres from an Indian position can fire on the Indian position from a range the Indian artillery cannot match. The Indian battery fires in response, the Firefinder locates it, Chinese counter-battery fire is directed to it. The Indian battery is suppressed or destroyed. The Chinese battery continues to operate freely."

He paused.

"This is not a theoretical scenario," he said. "This is the operational picture in eighteen to twenty-four months if China acquires and deploys the AN/TPQ-37."

He looked at the room.

"That is the threat," he said. "Now I want to tell you what I am asking you to do about it."

The silence after the threat briefing had the specific quality of a room that was processing something — not emotionally, not politically, but technically. These were engineers and a retired general and a former tank officer. They processed threat information the way they processed any technical specification: by understanding it precisely and then asking what response the specification demanded.

Krishnaswamy broke the silence.

"You are going to ask us to develop artillery," he said.

"Yes," Karan said.

"Self-propelled," Mehta said. Not a question.

"Self-propelled," Karan said. "The response to counter-battery radar is not simply longer range. A battery that fires and is immediately located and engaged has, if it is a towed artillery piece, a survival time measured in minutes — the time it takes to receive incoming fire. If it is a self-propelled artillery system, it fires and moves. It fires from one position, displaces immediately, and is not at the identified position when the counter-battery fire arrives."

"Shoot and scoot," Harshvardhan Singh said. The military term for the tactical doctrine.

"Shoot and scoot," Karan confirmed. "The towed artillery dies after one firing because it cannot move. The self-propelled artillery survives because it moves before the counter-battery fire arrives." He paused. "This is the first requirement: the system must be self-propelled. The second requirement is range."

He turned to the whiteboard.

He picked up the marker.

He drew a simple diagram: a line representing the Line of Actual Control, two positions — one Indian, one Chinese — on either side. Then numbers: distance from the line to the Chinese battery position, distance from the line to the Indian battery position. The geography of a Himalayan engagement was constrained by terrain, and the constraint produced specific numbers.

"In the western Himalayan sector," he said, "Indian army positions along the LAC are typically in valleys and on ridgelines that constrain artillery placement. Chinese positions have similar constraints. The effective engagement geometry — the range at which opposing batteries can engage each other — is driven by the terrain." He marked the numbers. "The requirement is a system that can engage Chinese artillery batteries from Indian positions while remaining outside the effective counter-battery engagement range."

He wrote two numbers on the board.

40 km.

35 km.

"Two systems," he said. "The first: a 155mm self-propelled gun-howitzer with a minimum range of forty kilometres with standard ammunition. Capable of extended range with base-bleed or rocket-assisted projectiles reaching fifty kilometres or beyond." He pointed to the first number. "The second: a lighter self-propelled howitzer, also 155mm, with a minimum range of thirty-five kilometres. This one is for terrain where the heavier system cannot operate — the specifically constrained access routes and firing positions of the eastern sector, Arunachal Pradesh." He pointed to the second number.

He turned to face the room.

"Forty kilometres and thirty-five kilometres," he said. "Both self-propelled. Both 155mm. Both designed for operation in mountain terrain — which means weight constraints that do not apply to plains artillery, because the access routes in the Himalayan sector are not the same as national highways." He paused. "I want both systems in six to nine months."

The room was quiet.

Not the silence of people who were shocked. The silence of people who were converting a requirement into a problem and trying to determine, in real time, whether the problem was solvable.

Mehta said: "Six to nine months."

"Yes," Karan said.

"The Arjuna took three years," Mehta said.

"The Arjuna was a tank," Karan said. "A self-propelled howitzer is not a tank. The armour requirement is protection against small arms and artillery fragments, not defeat of kinetic energy penetrators. The mobility requirement is cross-country in mountain terrain, not the sustained high-speed manoeuvre requirement of a main battle tank. The fire control requirement is different — it is ballistic computation and communication with a fire direction center, not the gunner's sight and stabilisation of the tank's primary weapon." He paused. "The Arjuna was a hard problem. These two systems are also hard problems. They are not the same hard problem."

Krishnaswamy said: "The barrel is the problem. 155mm, forty kilometres range. The pressure requirements at that range — the propellant charge, the barrel length, the chamber geometry — this is not a trivial engineering challenge."

"No," Karan said. "It is not trivial. But it is not novel. The 155mm calibre has been worked extensively by every major artillery power. The FH70 howitzer, the American M198, the French GIAT TR — these systems are in the thirty-kilometre range band with standard ammunition and reach beyond in extended range variants. The technology pathway is established. We are not inventing a new calibre or a new propellant chemistry. We are applying established technology to a specific performance requirement on an aggressive timeline."

"The barrel length for forty kilometres," Vikram Iyer said. He had been quiet since his arrival. He was the armament engineer, the person in the room who had the most specific knowledge of barrel geometry and its relationship to projectile performance. "Forty calibre barrel is approximately six point two metres for 155mm. That is the barrel length required for the pressure integration that produces forty-kilometre range with standard NATO propellant charges." He paused. "Fifty-two calibre — the longer variant — extends the range further. The L52 architecture, which the current European programmes use, gives ranges in the forty-kilometre standard, beyond forty with extended range munitions."

"L52," Karan said.

"L52 is fifty-two calibres," Iyer said. "For 155mm that is approximately eight metres of barrel. It is the longest practical barrel length for a self-propelled system that needs to traverse and be transported." He looked at the whiteboard. "L52 gives us the range. The question is whether we can design and manufacture an L52 barrel in the timeline."

"Tell me the answer," Karan said.

Iyer was quiet for a moment.

"The steel specification for the barrel," he said, "is a high-strength alloy that can withstand sustained firing pressures above four hundred megapascals without fatigue failure or heat deformation. We have the metallurgy from the Arjuna gun programme. The Shatrujit barrel work gave us the capability to produce gun-quality steel. The L52 geometry is larger — the manufacturing challenge is scaling the precision boring and rifling — smoothbore in this case — to an eight-metre barrel without eccentricity errors that accumulate over the length."

"Can we do it?" Karan said.

"Yes," Iyer said. He said it without the qualification that a less confident engineer would have added. He said it the way he said things he had thought through: with the specific flatness of a statement that was both technical judgment and personal commitment.

"In the timeline?" Karan said.

Iyer paused.

"Six months to a first barrel," he said. "Nine months to a barrel that has completed the proof firing programme and is cleared for installation." He paused again. "Nine months is the limit. Not because the engineering is uncertain but because the proof firing programme takes time — you cannot rush the fatigue testing, you can only compress the preparation for the test."

"Nine months," Karan said.

"For the main gun barrel," Iyer said. "The rest of the system—" He looked at the others.

"The chassis," Nair said. He was looking at the ceiling the way engineers looked at the ceiling when they were running the calculation in their heads rather than on paper. "The SDG-1000 engine from the Arjuna — can we use it?"

"The SDG-1000 produces one thousand horsepower," Karan said. "The Arjuna weighs forty-four tonnes. The self-propelled howitzer — the heavy one, the forty-kilometre system — will weigh approximately forty to forty-five tonnes in battle-ready configuration. The power-to-weight ratio from the SDG-1000 in the howitzer chassis is acceptable."

"The suspension," Dilip Bose said. He had been listening with the intensity of a man building a picture piece by piece. "We can use the Arjuna suspension geometry with modifications for the different weight distribution. The howitzer has its weight concentrated differently from the tank — the barrel mass over the front of the chassis rather than centered in the turret ring. The suspension needs rebalancing."

"How long?" Karan said.

"The suspension design adaptation is four months," Bose said. "Based on the Arjuna suspension drawings already in the system. It is not a new suspension, it is an adaptation."

"The turret," Mehta said.

This was the critical word. The turret of a self-propelled howitzer was different in fundamental character from a tank turret — it was an open or semi-open structure that accommodated the long barrel's loading cycle, handled the significant recoil of a large-calibre gun, and provided the crew working space for loading and laying the weapon. It was also the component that had to rotate through 360 degrees, that had to be ballistically protected against artillery fragments, and that had to interface with the fire control system that directed the weapon's aim.

"The turret is the new component," Mehta said. "The chassis we adapt. The engine we adapt. The suspension we adapt. The turret is new."

"The turret is new," Karan agreed.

"What is the recoil?" Iyer said. He was asking Krishnaswamy.

"For a 155mm L52 at maximum charge," Krishnaswamy said, "the recoil force is approximately five to six hundred kilonewtons. The hydropneumatic recoil system needs to manage that energy in a stroke that does not exceed the practical dimensions of the turret — approximately one metre recoil travel." He paused. "The French 155mm AUF1 — the system on which the Caesar is based — uses a similar configuration. Their recoil system specification is in the literature."

"The Caesar is a wheeled system," Mehta said.

"The technology is the same," Krishnaswamy said. "Tracked chassis, wheeled chassis — the recoil management geometry is the same. What changes is the mounting interface."

"The fire control," Parimal Ghosh said.

Everyone looked at him. He was the youngest person at the table and he spoke less frequently than the others, not because he had less to say but because he had learned, in the two years since joining the team, that the most effective way to contribute in this room was to say less with more precision.

"The thermal imaging from the Arjuna programme," he said. "We developed it for the tank commander's sight. For the artillery application, we need something different — not a targeting sight but a flash detector. Counter-battery radar works by detecting the projectile in flight. A flash detector works by detecting the muzzle flash of the enemy gun. It is an earlier detection in the timeline — before the round is in the air — but it is less precise in range calculation." He paused. "We could develop a complementary system — not instead of counter-battery radar but alongside it. When the Indian Army has its own counter-battery radar, the flash detector provides a secondary channel."

"We are building that too?" Mehta said. He said it with the dry quality of a man who had just added a third item to a list that was already demanding.

"No," Karan said. "The counter-battery radar is a separate programme. I mention it because it is the context. The immediate requirement is the artillery systems. The radar comes after."

"The counter-battery radar is a different order of complexity," Krishnaswamy said. "The Firefinder processes phased array radar returns in real time and computes ballistic trajectories. That is a signal processing problem that is—" He looked at Karan. "That is an ISMC problem."

"Yes," Karan said. "And it is on the list. Not for today."

He looked at the room.

"Today," he said, "I need to know if this team can build two self-propelled howitzers in six to nine months. A forty-kilometre system and a thirty-five-kilometre system. Both 155mm. Both designed for mountain terrain operation. Both completely indigenous." He paused. "I need an honest answer. Not an optimistic answer. Not a cautious answer. Honest."

The room was quiet for a long moment.

Harshvardhan Singh spoke first.

"I spent thirty-five years in the Indian Army," he said. He said it in the tone of a man beginning a statement that required the weight of that experience to carry. "I spent thirty-five years watching the Army use other people's artillery. British guns. Soviet guns. The 105mm L70 that has been in service since before some of the people in this room were born. We modernised some things. The BM-21 was a real improvement. But the fundamental situation was always the same: the Army had artillery that it had been given or bought and the artillery defined the ceiling of what the Army could do."

He looked at Karan.

"The threat you've described," he said. "Counter-battery radar in Chinese hands. The range asymmetry. I want to be honest about what that means, because I am the operational advisor in this room and it is my job to say clearly what the operational picture looks like." He paused. "If China deploys AN/TPQ-37 systems in the Himalayan sector and the Indian Army does not have a response — does not have systems that can operate outside the counter-battery engagement range — then Indian artillery is neutralised in the Himalayan theatre. The Indian Army fights the Himalayan war without effective artillery support." He paused again. "That is not a disadvantage. That is a defeat condition. Artillery in mountain warfare is not a supporting arm. It is the primary arm. Without it, the fight is infantry and air, and the terrain heavily favours the defender with artillery against the attacker without it."

The room was very still.

"Can this team build what is needed?" Harshvardhan Singh said. He looked at Krishnaswamy, at Nair, at Iyer, at Mehta. "I am asking directly because I am sixty-one years old and I have seen enough equipment programmes to know that engineers say yes when they mean probably and they say probably when they mean they don't know. I am asking you to tell me which answer this actually is."

Krishnaswamy looked at Iyer.

Iyer looked at Nair.

Nair looked at Mehta.

Mehta looked at Krishnaswamy.

This silent consultation lasted approximately five seconds, which was long enough to be the consultation of people who were taking the question seriously.

Krishnaswamy said: "Yes."

He said it with the same flatness that Iyer had used when he answered Karan's question about the barrel. The flatness of a statement that was technical judgment and personal commitment simultaneously.

"Yes," he said. "With the following conditions. First: the priority classification of this programme must be the same as the Arjuna programme at its most acute phase. Full resource access, no competition from other programmes for personnel and equipment. Second: the design reviews proceed on a compressed timeline — we do not wait for each phase to be complete before beginning the next phase, we accept that some rework will be necessary when later phases produce information that changes earlier decisions. Third: the proof firing programme is not compressed. We do not put a system in front of the Army that has not been proven at the barrel, including fatigue testing. We may compress other timelines. We do not compress the safety-critical testing."

"Agreed," Karan said.

"Fourth," Krishnaswamy said. "The steel division provides the barrel steel specification within three weeks. If the specification requires development work beyond the Arjuna Shatrujit material, that development starts immediately."

"The steel division has been briefed," Karan said.

He said it, and then he paused, because the way he said it was the way he said things he had already arranged — not as planning but as reporting. He had done this before. He had arranged things before he told the team about them, because the arrangements were the precondition for the commitment he was asking for.

"You briefed the steel division before this meeting," Krishnaswamy said.

"Three days ago," Karan said.

"The materials analysis for the barrel specification?"

"Underway," Karan said. "The preliminary material specification will be ready on Friday."

Krishnaswamy looked at him.

"You told us this was a new mission," he said.

"I'm telling you today," Karan said. "The preparation began when I understood the threat. The mission is new. The preparation was not."

Mehta said: "What else has been prepared?"

"The suspension analysis," Karan said. "Bose, the load distribution calculations for the howitzer chassis weight are on your desk. The ISMC ballistic computation team has been tasked to the fire control algorithm. The ordnance workshop has been given the initial chamber geometry specification for the 155mm round development." He looked around the table. "The preparation has been going on for seventy-two hours. This meeting is not the beginning. This meeting is the point at which the team knows what it is building and why."

The room absorbed this.

Mehta said: "Why didn't you tell us three days ago?"

"Because three days ago I was verifying the intelligence," Karan said. "The signals summary came to me on the seventh. I spent two days confirming the source reliability and checking the technical details against open-source literature on the AN/TPQ-37 programme. I confirmed yesterday. I am telling you today."

He looked at Mehta.

"I tell you when I know," he said. "Not when I suspect."

Mehta looked at him for a moment.

"All right," he said.

The technical session began at eight-thirty, after a twenty-minute break in which most of the team went to the corridor and drank tea and had the conversations that needed to happen outside the formal meeting structure — the specific cross-talk of people who had worked together for three years and who were, in this break, converting the shock of the mission briefing into the preliminary working architecture of how it was actually going to be done.

Karan used the break to draw on the whiteboard.

When the team came back, the whiteboard had a structural diagram.

Not a system schematic — an organisation diagram. Two columns, headed SYSTEM A (40km) and SYSTEM B (35km). Below each column, six rows: Barrel/Armament, Propulsion/Chassis, Suspension, Turret/Recoil, Fire Control, Integration.

Beside each row, a name.

The names corresponded to the people in the room.

"This is the programme structure," Karan said, when they were seated. "Each of you owns the technical leadership for your row across both systems. Where the row spans both systems — which is all of them — the technical decisions you make apply to both. The systems share as much architecture as the performance requirements allow." He looked at the diagram. "They share the engine. They share the suspension baseline, modified for weight distribution. They share the barrel calibre. They differ in barrel length — System A at L52, System B at L39, which gives us the range bands without redesigning the fundamental architecture."

"L39 gives thirty-five kilometres?" Ghosh said. He was always checking the numbers.

"L39 at 155mm with maximum standard propellant charge, standard projectile," Iyer said, doing the calculation from memory. "Approximately thirty-three to thirty-five kilometres depending on projectile. The base-bleed variant extends this to approximately forty kilometres."

"So System B reaches thirty-five kilometres with standard ammunition and forty kilometres with base-bleed," Krishnaswamy said.

"Which makes it approximately equivalent to System A's standard range," Nair said.

"The performance overlap is intentional," Karan said. "The systems are not differentiated primarily by range. They are differentiated by weight and platform characteristics. System A is the full-capability system for plains and moderate mountain terrain. System B is the lighter system for severely constrained Himalayan terrain — high-altitude passes, narrow access routes, the operational conditions where the full weight of System A's chassis is not passable." He paused. "System A with maximum protection and armament weighs approximately forty-two to forty-five tonnes. System B targets approximately thirty-three to thirty-six tonnes. The weight difference is the primary operational distinction."

Bose said: "The weight for System B requires a different chassis development from the Arjuna baseline."

"Yes," Karan said. "The Arjuna chassis at forty-four tonnes cannot be lightened to thirty-six tonnes without fundamental redesign. System B requires a new chassis design that accepts the SDG-1000 engine but is a lighter structure."

"That is not an adaptation," Bose said. "That is a new design."

"Yes," Karan said.

"That extends the timeline for System B," Bose said.

"What is your timeline?" Karan said.

Bose thought.

He did not think quickly — Bose was not a quick thinker in the surface sense. He was a thorough thinker, and thoroughness had a pace. He looked at the diagram on the whiteboard. He looked at the engine specification. He looked at the weight target.

"Eight months to a prototype chassis that meets the weight target and passes initial mobility testing," he said. "If the suspension adaptation work from System A informs System B from the beginning — which it will, since System A comes first — the learning transfer reduces the development time."

"Eight months is within the nine-month window," Mehta said.

"With no schedule margin," Bose said. He said it the way engineers said things they needed the decision-maker to hear: clearly, without apology, because the information was accurate and accuracy served everyone better than the comfort of understatement.

"Understood," Karan said.

"I want to talk about the turret," Mehta said. He was looking at the diagram with the expression he wore when he was building something in his head that was not yet in any document.

"Talk," Karan said.

Mehta stood up. He went to the whiteboard and picked up a marker. He drew beside Karan's diagram — not overlapping it but adjacent, in the space that remained on the board. He drew a cross-section of a turret.

"The turret for a self-propelled howitzer is not a tank turret," he said. "I want to make sure everyone in this room understands this specifically because we all came from the Arjuna programme and the Arjuna turret is our frame of reference." He drew the comparison. "The Arjuna turret is a closed steel structure, primarily designed to protect the crew from kinetic energy penetrators and shaped charges. The turret rotates 360 degrees. The crew operates inside it under armour protection. The gun fires through a mantlet that is designed to maintain the armour envelope."

He drew the howitzer turret beside it.

"The howitzer turret is different in every one of those characteristics. It is semi-open at the rear for loading access — 155mm rounds are large and heavy, a fully enclosed loading system adds weight and complexity that a self-propelled artillery system does not need. The crew operates in a protected working space but not under the same armour standard as the tank — artillery fragments, small arms, that is the threat protection level. The recoil is the design driver, not the armour."

He looked at Krishnaswamy.

"The recoil system," he said. "What is the stroke and the force?"

"As I said — approximately five to six hundred kilonewtons, one-metre stroke," Krishnaswamy said. "The hydropneumatic recoil cylinder length is approximately 1.4 metres including the buffer system. This is mounted above the breech in the conventional two-cradle architecture."

"The breech height," Mehta said. He was drawing as he spoke. "If the breech is at the standard loading height — approximately 1.4 to 1.6 metres from the turret floor — the loader can stand and operate the breech without mechanical assistance for the round charge. The projectile itself is approximately forty-three to forty-five kilograms for 155mm. This is at the limit of manual handling for sustained fire."

"The FH70 uses a semi-automatic loading assist," Iyer said. "A mechanical tray that supports the projectile during ramming. The ramming itself is power-assisted but the handling from the ready rack to the tray is manual."

"Are we implementing a loading assist?" Mehta said. He looked at Karan.

"What do you recommend?" Karan said.

"In mountain terrain, sustained firing rates matter less than accuracy and survivability," Mehta said. "The shoot-and-scoot doctrine requires the system to fire a specific number of rounds, displace, and move. The sustained fire rate is not the primary performance driver — the survival time per firing position is." He paused. "Manual loading is simpler, lighter, less to maintain and repair. For the Himalayan doctrine, I recommend manual loading with an ergonomic round handling solution rather than a mechanical loading system."

"The round handling solution," Meenakshi Subramaniam said. She had been quiet for most of the technical discussion, which was consistent with her discipline — she was the armour specialist, not the armament engineer, and she had been building her contribution in silence. "The crew working in the turret. The ammunition storage. The interface between the ammunition magazine and the crew handling the round. This is a crew systems problem."

"It is a crew systems problem," Mehta agreed. He said it with the specific respect of one specialist acknowledging another's territory.

"I want to be involved in the turret interior layout from the beginning," Meenakshi said. "Not from the first design review. From the first sketch." She looked at Karan. "On the Arjuna, the turret interior was redesigned three times because the crew ergonomics were an afterthought in the early design. The loading position, the sight position, the commander's reach to the controls — each revision added time and cost." She looked at Mehta. "I am not criticising the Arjuna process. I am saying that for this timeline, we cannot afford to iterate on the interior layout."

"Agreed," Mehta said. He said it immediately, without the brief pause of a man considering whether to agree. He had learned, on the Arjuna programme, the cost of the iterations that had been necessary because the initial layout had not incorporated crew ergonomics from the beginning. He was not going to make the same mistake.

"The interior layout meeting," Karan said. "Three days. Thursday. Meenakshi and Mehta lead it. I want a preliminary layout by end of Thursday."

"Three days," Meenakshi said.

"Three days," Karan confirmed.

She looked at her folders — the stack she had brought and put at the end of the table. She opened the top one. It contained drawings.

"I brought the Arjuna turret interior as-built drawings," she said. "Not as the starting point. As the reference for what we are not repeating."

Mehta almost smiled.

At ten-thirty, the technical working session paused for the second break.

Karan went to the window.

The Gorakhpur morning outside was doing what October Gorakhpur mornings did — the specific quality of October light in the Gangetic plain, past the rains, the air dry and clear, the sky a blue that was different from the monsoon sky and from the summer sky and was specifically the October sky, the sky of the beginning of the cool season that made the compound's workers walk differently, with slightly more energy, as though the air itself was carrying something that the summer air had been too heavy to carry.

He thought about the AN/TPQ-37.

He thought about twelve systems in Chinese hands, deployed along the LAC, able to locate every Indian artillery piece that fired within seconds of the first round leaving the barrel.

He thought about what the Indian Army would do in the Himalayan sector when it could not use its artillery.

He thought about what the Himalayan sector looked like without artillery support — the specific terrain of Ladakh, the high-altitude plateaus and narrow valleys, the passes where mountain infantry fought with nothing but their own firepower and the ground they stood on. The Indian Army's mountain infantry was among the best in the world at that kind of fighting. They had earned that reputation in the 1962 war and in the 1965 and 1971 conflicts and in the sustained forward presence that the LAC required.

But mountain infantry without artillery was mountain infantry dependent on direct fire weapons and short-range support, and direct fire weapons and short-range support were adequate for defending ground and inadequate for the kind of engagement that denied the enemy the initiative.

He thought about what it meant that China was acquiring this system.

The US-China relationship had been warming since Kissinger's opening in 1971. Ford was deepening it. The AN/TPQ-37 sale was the specific kind of technology transfer that a warming relationship produced — dual-use military technology provided to China as both a commercial transaction and a strategic signal. The strategic signal was: the United States and China have a shared interest in a stable security environment, and this technology serves that interest.

The signal was aimed at the Soviet Union.

But the system would be pointed at India.

He turned from the window.

Ravi Shankar Pillai was at the whiteboard, having made notes during the break that he was now reviewing. He was the engine development engineer — his concern was the SDG-1000's performance in the howitzer application and specifically in the high-altitude environment of the Himalayan sector.

"The SDG-1000 at altitude," Karan said. He had been watching Pillai's notes and could read the topic from the structure of what was written.

"The engine loses approximately three percent power per thousand metres of altitude above sea level," Pillai said. "At five thousand metres — which is the operating altitude in parts of the western Himalayan sector — the SDG-1000 produces approximately eight hundred and fifty horsepower." He paused. "This is still sufficient for the chassis weight of System A at forty-five tonnes on the terrain we're designing for. But the thermal management at altitude is different. The air is thinner, the cooling is less effective for a given airflow, the engine runs hotter."

"Can we manage it?" Karan said.

"Yes," Pillai said. "The cooling system design needs to be specified for altitude operation from the beginning rather than as an afterthought. The intercooler geometry, the radiator size, the thermostat settings. If we design for altitude operation from the start, the SDG-1000 performs acceptably at five thousand metres." He paused. "If we design for sea level and adjust — which is what usually happens in Indian defence programmes because they are designed for plains warfare and then asked to operate in the mountains — we get the problems we saw with other systems."

"Design for altitude from the beginning," Karan said.

"From the first sketch," Pillai said.

"Yes," Karan said. He wrote it on the whiteboard. Not as a note — as a requirement. It went on the requirements list that was accumulating as the morning progressed.

The requirements list was not a formal document. It was the whiteboard version of the conversation the team was having — the specific things that were being established as non-negotiable, the things that would define what the systems were before the engineering began.

REQUIREMENTS — BOTH SYSTEMS:

Self-propelled, tracked 155mm calibre Indigenous components, no imported parts in production specification Mountain terrain operation: altitude up to 5,000m, access route width constraints Engine designed for altitude from initial specification Crew ergonomics integrated from first sketch (Meenakshi/Mehta) Manual loading with ergonomic round handling Proof firing programme: not compressed Mine protection: V-hull geometry (System A: same standard as Arjuna; System B: minimum military specification) Fire control: ballistic computer, direct and indirect fire modes, GPS integration capability

He had written the last line — GPS integration capability — and paused, because the room had registered it.

"GPS," Krishnaswamy said.

"The American GPS programme is in development," Karan said. "Initial operational capability is projected within the decade. The system we build today will be in service in 1980 and beyond. I want the fire control architecture to be GPS-capable when GPS is available."

"We cannot integrate GPS if it doesn't exist yet," Ghosh said.

"We can design the fire control architecture to accept a GPS input module when it exists," Karan said. "The integration point — the data interface, the processing capacity, the display capability — these can be designed in without the GPS unit itself. When the unit is available, it plugs in."

Ghosh thought about this.

"A position fix input," he said. "Any source. Currently manual survey, eventually GPS. The fire control processes the position data regardless of source."

"Exactly," Karan said.

Ghosh made a note.

At eleven o'clock, Harshvardhan Singh asked to speak.

He had been the operational advisor throughout the morning — listening more than speaking, which was his characterised role, the voice of operational experience in a room of technical expertise. When he asked to speak, the room gave him the specific quality of attention that it gave him, which was the attention of people who understood that his contribution was different in kind from their own.

"I want to talk about doctrine," he said.

He stood, which was unusual — the others had conducted their contributions seated. He stood and went to the whiteboard and looked at what had been written on it through the morning.

"The shoot-and-scoot doctrine," he said. "We've named it this morning several times. I want to be precise about what it requires because the doctrine drives the design in ways that have not yet been fully articulated."

He looked at the room.

"Shoot and scoot," he said. "A self-propelled artillery battery receives a fire mission. It moves to a firing position. It fires the mission — in the standard fire plan, this is three to six rounds per gun in a battery of six guns. It displaces immediately after firing and moves to an alternate position before the counter-battery fire can arrive."

He paused.

"The time discipline," he said. "The system must be ready to fire within two minutes of reaching the firing position. It must complete the displacement — move from the firing position — within ninety seconds of firing the last round. The counter-battery fire will arrive within two to five minutes of the first round fired. The system must not be at the firing position when it arrives."

He looked at the requirements list on the whiteboard.

"Ready to fire in two minutes," he said. "This requires the barrel to travel — the process of moving the barrel from its transport configuration to its firing elevation — to complete in under ninety seconds. The levelling system — the hydraulic jacks that stabilise the chassis for firing — must deploy in under sixty seconds. The fire control alignment to the fire plan target — the initial computation — must complete in under thirty seconds."

He wrote these numbers on the whiteboard.

Barrel travel: 90 seconds Levelling: 60 seconds Fire control alignment: 30 seconds Total ready-to-fire time: 180 seconds (2 minutes)

"Displacement in ninety seconds," he continued. "This requires the levelling jacks to retract in under thirty seconds. The barrel to return to transport position in under forty seconds. The engine to be in drive before the last jack is fully retracted."

Retract jacks: 30 seconds Barrel travel to transport: 40 seconds Total displacement time: 90 seconds (1.5 minutes)

He stepped back from the whiteboard.

"These are not arbitrary numbers," he said. "They are derived from the counter-battery fire timeline. The AN/TPQ-37 detects and computes in under sixty seconds from the first round. The counter-battery fire order is issued within ninety seconds. Rounds are in the air at two minutes. They arrive at two to five minutes depending on range." He looked at the team. "If our system is at the firing position when the rounds arrive, it is destroyed. The doctrine only works if the timing works. The timing only works if the system is designed for it from the beginning."

He looked at Bose.

"The levelling system," he said. "The hydraulic jacks. Sixty seconds to full level."

Bose made a note.

"The barrel travel," he said, looking at Iyer. "The drive mechanism that moves the barrel from transport to fire elevation. Ninety seconds."

Iyer made a note.

"The fire control initialisation," he said, looking at Ghosh. "Thirty seconds from first switch-on to first fire solution."

Ghosh made a note.

Harshvardhan Singh looked at Karan.

"The system exists in the specification," he said. "I want it to exist in the design. I am asking the team to treat these time requirements as hard requirements — as hard as the range requirement, as hard as the armour protection requirement — because if they are soft requirements, they will be softened in design tradeoffs and the doctrine will not work."

"They are hard requirements," Karan said.

"Then I want them on the list," Harshvardhan Singh said.

Karan added them to the whiteboard list.

Harshvardhan Singh returned to his seat.

The room was quiet for a moment.

Mehta said: "Brig. Singh."

"Yes," Harshvardhan Singh said.

"The thirty-five-year career," Mehta said. "The mountain campaigns. You've seen Indian artillery fail to support the infantry it was supposed to support."

"More than once," Harshvardhan Singh said.

"Because of equipment limitations," Mehta said.

"Because of equipment limitations and because of doctrine that did not match the terrain," Harshvardhan Singh said. "The two are connected. When the equipment cannot do what the terrain requires, the doctrine degrades to what the equipment can manage. The equipment defines the ceiling of the doctrine." He paused. "What this programme is doing is raising the ceiling."

"And if we raise the ceiling," Mehta said.

"The doctrine can be what it needs to be instead of what it can afford to be," Harshvardhan Singh said. "The mountain infantry will have artillery that can reach the enemy battery positions and survive the response. The commander will issue fire missions knowing that the battery will still be there for the next mission. The campaign will unfold differently." He paused. "I spent thirty-five years working within ceilings. I am sixty-one years old and I am in this room because I want to spend whatever time I have left helping to remove them."

The room was very quiet.

Karan looked at him.

"Then let's remove them," he said.

The working session after the lunch break was different in character from the morning's session.

The morning had been the problem — the threat, the requirements, the mission. The afternoon was the response — the specific engineering of how it was going to be built.

Iyer took the main position at the whiteboard for the barrel section.

"L52 barrel for System A," he said. "I am going to walk through the design architecture and I want interruptions when anyone sees a problem."

The room gave him the specific quality of attention that working engineers gave a technical presentation — active, critical, looking for the problems rather than endorsing the solution.

"The barrel blank," he said. "High-strength gun steel, the specification that comes from the Shatrujit programme but with a different geometry. The Shatrujit is 120mm smoothbore at a shorter length — L44 effectively, though we didn't use that designation. The 155mm L52 is longer, larger bore, and requires a larger breech ring that manages the higher chamber pressure." He drew on the whiteboard. "The chamber volume for 155mm at maximum propellant charge is approximately six thousand cubic centimetres. The breech ring design — the structure that seals the cartridge case and transfers the firing impulse to the barrel — has to manage the peak chamber pressure of approximately four hundred megapascals reliably for a minimum of one thousand rounds before requiring inspection."

"One thousand rounds before inspection," Krishnaswamy said. "Is that the fatigue life requirement?"

"The requirement in the system specification is eight thousand rounds to barrel replacement," Iyer said. "One thousand rounds to inspection is the interim check. The inspection protocol clears the barrel for continued service if within specification, replaces if not."

"Eight thousand rounds," Krishnaswamy said. He was doing the operational arithmetic. "At typical artillery utilisation in the Indian Army — a major exercise or sustained engagement uses approximately two hundred rounds per gun per day — eight thousand rounds is forty days of sustained operation."

"Which is a long engagement at that intensity," Harshvardhan Singh said. "The 1971 war lasted fourteen days. The operational life is adequate."

"The breech mechanism," Iyer continued. "We are using a vertical sliding breech block rather than the interrupted thread design used in most Western 155mm systems. The vertical slide is faster — the opening and loading cycle is approximately two seconds faster per round — and it is simpler to maintain in field conditions."

"The FH70 uses an interrupted thread," Krishnaswamy said.

"The FH70 prioritised reliability in extreme cold," Iyer said. "The interrupted thread is more tolerant of contamination in the thread engagement surfaces. The vertical slide is faster but requires cleaner engagement surfaces." He paused. "For the mountain terrain application, we need the speed — the fire rate is a factor in the shoot-and-scoot doctrine. We accept the maintenance discipline requirement for the vertical slide."

"The ammunition," Meenakshi Subramaniam said. She was looking at the board. "The round weight. Manual loading."

"43.5 kilograms for the standard HE projectile," Iyer said. "The propellant charge — a standard modular artillery charge — is approximately twelve to fifteen kilograms depending on zone. The total round weight to load position is approximately fifty-six kilograms."

"No human being loads fifty-six kilograms manually at sustained rate," Mehta said.

"No," Iyer agreed. "The round handling assists the projectile separately from the propellant. The projectile is loaded using a ramming assist — a spring-powered tray that the loader positions the round on and which completes the ramming into the chamber with a push handle. The propellant charges are loaded separately, by hand, directly into the breech. The loader handles approximately fifteen kilograms manually per round for the propellant."

Mehta thought about this.

"The round rack," he said. "Where are the ready rounds stored?"

"On the turret platform," Iyer said. "Six rounds in the ready rack, accessible from the loading position without the loader changing stance. The remainder — the standard ammunition complement is twenty-two ready rounds on the vehicle plus additional in the hull ammunition bay — requires replenishment from the hull during a sustained fire mission."

"The replenishment procedure," Mehta said. "Hull to ready rack. Time and crew requirement."

"One crew member, approximately forty-five seconds per round," Iyer said. "The hull ammunition bay has a hatch that opens to the turret platform. The round is brought up through the hatch and positioned in the ready rack."

"During a fire mission?" Mehta said.

"The third crew member — the System A crew is four: commander, driver, gunner, loader — the third crew member can replenish the ready rack while the loader is loading," Iyer said. "The fourth crew member is the commander, who is directing the mission."

"Four crew," Mehta said. "I want to revisit the crew composition." He looked at Karan.

"Tell me," Karan said.

"In the Arjuna, we have four crew: commander, gunner, loader, driver," Mehta said. "In the self-propelled howitzer, the role distribution is different. The commander directs the fire mission and manages communication with the fire direction center. The driver drives and operates the levelling system. The gunner lays the weapon and operates the fire control. The loader loads the weapon and replenishes." He paused. "The division of tasks is workable in a four-person crew. What I want to know is whether the mountain terrain application creates situations where the crew is insufficient."

Harshvardhan Singh said: "In mountain operations, the crew may need to provide its own security. Artillery batteries in the Himalayan sector operate without dedicated security elements in some scenarios — the terrain is too constrained for the standard combined arms structure. The crew may be required to defend the system while simultaneously operating it."

"Four crew, self-defence and operation simultaneously," Mehta said.

"This is the T-155 architecture — a fifth crew member for the turret loader-security role," Krishnaswamy said. He was referring to the Turkish self-propelled howitzer that used this crew configuration. "Five crew adds weight and volume."

"The alternative is better automation," Ghosh said.

The room looked at him.

"If the fire control automation reduces the gunner's workload sufficiently," he said, "the commander can perform fire control functions when the fire mission is not at maximum rate. The crew can be four with enhanced automation rather than five with manual procedures." He paused. "The ballistic computer I am designing for this system can automate the fire solution computation, the fuze setting, the propellant zone selection. The gunner's task is to confirm the solution and execute the layering — pointing the barrel at the computed azimuth and elevation. If the computation is automated, the gunner's active time per round is reduced from approximately twenty seconds to approximately eight seconds."

"Which frees the commander for other tasks during the firing cycle," Mehta said.

"Yes," Ghosh said.

Karan was looking at the whiteboard, specifically at the time requirements that Harshvardhan Singh had written.

Ready-to-fire time: 180 seconds. Displacement time: 90 seconds.

"The automation of the fire solution computation," he said. "What is the computation time from data input to solution output?"

"With the ISMC processors," Ghosh said, "under one second. The meteorological correction, the charge selection, the fuze timing — under one second from input to solution."

"Under one second," Harshvardhan Singh said.

"Yes," Ghosh said. "The ballistic computation is not the time constraint in the ready-to-fire timeline. The levelling and barrel travel are the time constraints."

"Which puts the focus back on the hydraulic systems," Bose said.

"Yes," Karan said. He looked at Bose. "Sixty seconds for full levelling."

"I heard," Bose said. "It is aggressive but achievable. The levelling jack cylinder size and the hydraulic pump flow rate determine the levelling time. Larger cylinders and a higher-flow pump give faster levelling but add weight." He paused. "I am looking for the weight-optimised solution that meets sixty seconds."

"What is the current state of that analysis?" Karan said.

"Preliminary," Bose said. "The analysis I found on my desk this morning gives me a sixty-five-second levelling time with the initial architecture. Five seconds above target." He paused. "I need a Friday morning to close the five seconds."

"Friday morning," Karan said.

"Friday morning," Bose confirmed.

At three in the afternoon, the formal session reconvened for what Karan had described in the morning as "the requirements closure."

He stood at the whiteboard.

The whiteboard was full.

He looked at it.

"We have been in this room for seven hours," he said. "In seven hours, we have moved from the threat briefing to preliminary design decisions on the barrel, the chassis, the turret interior, the crew configuration, the levelling system, the fire control architecture, and the shoot-and-scoot time discipline. This is the fastest I have seen this team move from problem to solution framework."

He paused.

"I want to say something before we go through the requirements closure," he said. "About why this programme matters in the way it matters."

The room waited.

"The Arjuna," he said, "was a programme that took three years and produced the best tank in Asia. The team in this room built it. The team knows what it cost — not in money, in everything else. The missed evenings, the extended field tests, the specific frustration of components that did not work and had to be rebuilt, the specific satisfaction of components that worked exactly as designed." He looked at them one by one. "The Arjuna was for the crew. The V-hull was for the crew. Every hour of this team's work was so that the soldiers who sit in that tank come home."

He paused.

"This programme is for the soldiers on the other side of the artillery," he said. "The infantry soldier at a Himalayan forward post who looks at the ridgeline where the Chinese position is and knows that artillery can reach it if the artillery is available. The artillery crew that fires a mission and displaces and does not die because the system moved before the counter-battery fire arrived." He paused. "The AN/TPQ-37 in Chinese hands does not kill soldiers directly. It kills soldiers by removing the artillery support that keeps them alive. Taking away a soldier's artillery and leaving them in mountain terrain facing an armed adversary is killing them by subtraction."

He looked at the room.

"What we are building is the subtraction back," he said. "The artillery that operates outside the counter-battery engagement range, that fires and moves and survives, that gives the mountain infantry its support regardless of what detection system the enemy has." He paused. "This is not abstract. In eighteen to twenty-four months, twelve AN/TPQ-37 systems arrive in Chinese service. In the same timeframe, I want India to have a self-propelled artillery capability that makes those systems irrelevant to our artillery's operational freedom."

He turned to the whiteboard.

"Requirements closure," he said.

He read through the list that had accumulated across the day.

System A: 155mm, L52 barrel, 40km range, 42-45 tonnes, tracked, SDG-1000 engine, four crew, automatic fire control, 180 seconds ready-to-fire, 90 seconds displacement, V-hull mine protection, mountain terrain operation at altitude.

System B: 155mm, L39 barrel, 35km range standard/40km base-bleed, 33-36 tonnes, lighter chassis, SDG-1000 engine, four crew, shared fire control architecture with System A, same time disciplines, reduced armour specification, high-altitude operation.

Both systems: 100 percent indigenous components, no imported parts in production specification. GPS-ready fire control architecture. Proof firing programme not compressed.

He looked at the team.

"Is there anything missing?" he said.

Harshvardhan Singh said: "The communication system."

Karan looked at him.

"The fire control system computes the solution," the Brigadier said. "The command and control system — the communication between the battery and the fire direction center, between the battery and the forward observer who is calling the fire mission — this is the other half of the artillery system. The gun that fires accurately is not useful if the communication to direct it is poor."

"The communication is separate from this programme," Karan said. "The communication systems are under development in the signals division. I will ensure the two programmes interface correctly." He looked at the whiteboard. "The fire control system interface to the communication system — what data format?"

"Standard artillery fire control message," Ghosh said. "Target coordinates, charge selection, fuze timing, observer correction. I will specify the data format and share it with the signals division."

"This week," Karan said.

"This week," Ghosh confirmed.

"Anything else?" Karan said.

Mehta said: "The spare parts standard."

Everyone looked at him.

"The Arjuna's spare parts," he said. "Everything is produced in Gorakhpur. No imported parts in the production specification and no imported parts in the field maintenance package. I want the same standard for both howitzer systems." He looked at Karan. "Every part that can break in the field — every part that the crew needs to be able to replace under fire — needs to be available from domestic supply. The mountain terrain is the most logistically constrained operational environment the Indian Army faces. A system that requires a foreign part that takes six weeks to arrive is a system that will be mission-non-capable for six weeks in the middle of a campaign."

"Understood and agreed," Karan said. "The spare parts standard is the same as the Arjuna programme. I will make this explicit in the programme requirements document."

"Good," Mehta said.

"Anything else?" Karan said.

The room was quiet.

"Then let me tell you about the programme milestones," Karan said.

He wrote on the whiteboard.

PROGRAMME MILESTONES — SYSTEM A:

Month 1 (October 1974): Barrel specification complete, material procurement initiated, turret interior layout complete.

Month 2 (November 1974): Barrel blank manufactured, initial machining begun. Chassis design complete to preliminary level. Suspension adaptation design complete.

Month 3 (December 1974): Barrel mid-body machined, bore geometry established. Chassis fabrication begun. Recoil system design complete.

Month 4 (January 1975): Barrel complete. Proof firing — 50 rounds, all charges, all elevations. Chassis assembly begun. Turret fabrication begun.

Month 5 (February 1975): Barrel proof firing complete (if passed). Full turret assembly. Engine installation to chassis.

Month 6 (March 1975): System A integrated — barrel installed to turret, turret mounted to chassis. Fire control installation and integration. First drive test.

Month 7 (April 1975): First firing on range. Shoot-and-scoot doctrine testing. Time discipline verification.

Month 8 (May 1975): Evaluation firing programme — range verification, accuracy testing, crew training assessment.

Month 9 (June 1975): System A programme complete. Presentation to Army for formal evaluation.

He wrote the same structure for System B, offset by two months — System B's lighter chassis required the new design development that Bose had identified, which added the two-month difference.

He stood back.

"June 1975 for System A," he said. "August 1975 for System B."

He looked at the room.

"Eight months and ten months," he said. "Not six to nine months for both."

"The proof firing programme," Iyer said. "Month four to five. That is the immovable part. If the barrel proof programme goes clean — no failures, all specifications met — we are on this timeline. If we have a failure that requires barrel redesign, we add time."

"What is the probability of a clean proof programme?" Karan asked.

Iyer thought.

"The Shatrujit barrel programme was clean," he said. "We have the metallurgy right. The machining processes are known. The 155mm geometry is larger but not qualitatively different in the fabrication challenge." He paused. "Seventy percent probability of a clean first proof firing programme."

"And the thirty percent?"

"An additional four to six weeks to identify and resolve the failure mode," Iyer said. "October 1975 worst case for System A."

"October 1975 as the absolute worst case is still within the window before the AN/TPQ-37 reaches Chinese service," Karan said. "The intelligence timeline says eighteen to twenty-four months from now. Twenty-four months from October 1974 is October 1976. We have twelve months of margin on the worst case."

"If the intelligence timeline is accurate," Krishnaswamy said.

"If the intelligence timeline is accurate," Karan confirmed. "Intelligence is a probability, not a certainty. We build to the tightest timeline that is achievable, which gives us the most margin against the intelligence being early."

Krishnaswamy nodded. He accepted this reasoning. He had been in enough programmes to know that timeline decisions were always probabilistic decisions, and that the correct response to uncertainty was to reduce it on the controllable side.

"One more thing," Karan said.

The room waited.

"The programme name," he said.

A brief pause.

Mehta said: "Dhanush."

The room was quiet.

Dhanush: bow, in Sanskrit. The weapon of Arjuna in the Mahabharata. The bow of the greatest warrior-archer in the epic, the weapon that required exceptional skill and strength to wield.

"Dhanush," Krishnaswamy said.

"Dhanush fits," Harshvardhan Singh said. He said it with the quiet certainty of someone for whom the name was not just poetic but operationally apt. "A bow is a precision weapon that delivers force at distance. The bowman who fires and moves is not where the arrow came from. The connection between the bow and the target exists only for the moment of the arrow's flight."

"Dhanush," Karan said.

He wrote it on the whiteboard.

DHANUSH PROGRAMME.

System A: Dhanush-40 (40km range) System B: Dhanush-35 (35km range)

He looked at the names.

The Arjuna was a tank.

The Dhanush was the bow.

Together, they were two-thirds of the equation.

He thought about the third.

But the third was not today.

The meeting closed at four-thirty.

The team began to disperse, but not immediately — the specific quality of dispersal that follows a significant meeting, when people needed the ten minutes of corridor conversation to confirm that they had understood correctly and to begin the working conversations that would happen between this meeting and the next.

Krishnaswamy stopped at the door.

"The AN/TPQ-37," he said, to Karan. "The twelve systems. How certain is the intelligence?"

"High confidence on the Chinese interest," Karan said. "Moderate confidence on the timeline. The technical specifications of the system are confirmed — it is not a classified specification, the American Army has published performance parameters in open source."

"The performance parameters," Krishnaswamy said.

"50 metres accuracy at 10 kilometres," Karan said. "Detection range of 24 kilometres for rockets and mortars, 30 kilometres for artillery. Processing time under 90 seconds from first detection to location solution."

"90 seconds," Krishnaswamy said.

"90 seconds," Karan confirmed.

"And the Dhanush," Krishnaswamy said. "The shoot-and-scoot time discipline. Ready to fire in 180 seconds, displacement in 90 seconds."

"Yes," Karan said.

"So the system fires," Krishnaswamy said. "The Firefinder detects. 90 seconds to compute the location. Counter-battery fire is ordered. The rounds leave the counter-battery guns. At 30 kilometres range, a 155mm projectile takes approximately 75 seconds to arrive." He did the arithmetic. "Detection to impact: 90 seconds compute plus 75 seconds flight time. 165 seconds."

"And the Dhanush displacement time is 90 seconds," Karan said.

"Which means the Dhanush fires and displaces in 90 seconds," Krishnaswamy said. "The counter-battery fire arrives at 165 seconds from detection. The Dhanush is not at the firing position." He paused. "75 seconds of margin."

"If the displacement time is met," Karan said.

"If the displacement time is met," Krishnaswamy agreed. He was quiet for a moment. "This is the whole game, isn't it. The entire doctrinal argument comes down to 90 seconds versus 165 seconds."

"Yes," Karan said.

"And if we miss the 90-second displacement target," Krishnaswamy said. "If it is 120 seconds. Or 150 seconds."

"Then the counter-battery fire finds the Dhanush at the firing position," Karan said.

Krishnaswamy stood in the doorway.

"The levelling system," he said.

"Yes," Karan said.

"The barrel travel mechanism," Krishnaswamy said.

"Yes," Karan said.

"Every second," Krishnaswamy said.

"Every second," Karan said.

Krishnaswamy nodded.

He walked out.

Mehta was the last to leave.

He stayed not because he had more to discuss but because he had the specific quality of someone who needed a moment in the room after the others had gone — the moment of being alone with the work before going back to the world where the work did not exist yet.

He stood at the whiteboard.

He looked at DHANUSH PROGRAMME.

He looked at System A: Dhanush-40.

He thought about the mountain sector. He had never served in the mountain sector — he was an armoured corps officer, tanks, and the Himalayan terrain was hostile to tanks. He knew it from maps and from the briefings he had received in the Advanced Projects Division's operational education programme that Harshvardhan Singh had run informally for the team's benefit. He knew it the way someone who had studied a place knew it — accurately but not bodily.

He thought about the mountain infantry soldier.

Harshvardhan Singh's description. Standing at a forward post looking at the ridgeline where the Chinese position was, knowing that artillery could reach it if the artillery was available.

If the artillery was available.

He thought about what it meant for a soldier to need something and not have it.

He knew what that meant from the armoured corps perspective — he had been on a Punjab road in 1971 and had understood, with the specific clarity of physical experience rather than theoretical knowledge, what it meant when the equipment failed the people who depended on it.

He thought about mountain infantry in a Himalayan engagement against an enemy with counter-battery radar and the range asymmetry it created.

He thought about what the Dhanush was.

It was the answer to a soldier standing at a ridgeline post in the Himalayan winter, looking at the Chinese position, knowing that in eighteen months there would be a system in Chinese service that could locate and destroy every Indian artillery piece that fired within thirty kilometres.

It was the answer built before the problem arrived.

He thought about Karan Shergill, who had received an intelligence summary on a Wednesday and had spent Thursday confirming it and had called this meeting on a Friday, and who had walked into Building 7 at six forty-five in the morning with the problem fully formed and the preliminary arrangements already made.

He had thought about this quality of Karan's across three years of working together — the quality of knowing what was needed before the need was articulated. The V-hull that was already the right answer before Mehta had described why it was the right answer. The armour specification that was designed against the T-72 before the T-72 was fully deployed. And now this — the counter-battery radar response built in the window before the counter-battery radar arrived.

He did not fully understand it.

He had thought about it enough times to know that he would not resolve the question by thinking harder about it. The quality was there. It had produced results. The results had been the right results.

He looked at the whiteboard one more time.

Then he went to the door.

He stopped.

"Karan," he said.

Karan was at the window, looking at the compound in the late afternoon light.

"Mehta," he said, without turning.

"The Dhanush programme," Mehta said. "The shoot-and-scoot doctrine."

"Yes," Karan said.

"The system fires and displaces," Mehta said. "The crew learns the timing. The 90-second discipline becomes instinct rather than procedure." He paused. "This is what training produces. The crew knows the system and the system serves the crew and the discipline is in the muscle memory."

"Yes," Karan said.

"I want to be in the crew training programme," Mehta said. "Not as an observer. As the trainer. I want to develop the crew training methodology for the Dhanush the way I developed it for the Arjuna."

Karan turned from the window.

He looked at Mehta.

"The Arjuna crew training," Karan said. "Three months to ninety-one percent gunnery. The evaluation crews outperformed historical wartime standards in a controlled environment."

"Yes," Mehta said.

"The Dhanush," Karan said. "What is the training methodology for the shoot-and-scoot time discipline? How do you teach a crew to displace in ninety seconds consistently, under pressure, in mountain terrain?"

Mehta was quiet for a moment.

"You time it," he said. "You time everything. Every drill timed. Every displacement timed. Every ready-to-fire sequence timed. The crew knows the target time for every element. The crew knows that the time is not a performance metric — it is the line between surviving and not surviving." He paused. "Then you make the timing boring. You repeat it until the timing is boring. The correct time is not achieved by trying hard. It is achieved by doing the procedure correctly, and the procedure has been done so many times that correct execution is the only execution the crew knows."

He looked at Karan.

"Boredom saves lives," he said. "In armoured operations, in artillery operations — the crews that survive are the crews for whom the correct procedure is so habitual it requires no thought. The crews that die are the crews for whom the correct procedure is an effort."

"Build it into the training methodology," Karan said. "You have the programme."

Mehta nodded.

He walked out.

Karan turned back to the window.

The compound outside was in the full October afternoon light — the late afternoon light that came at a low angle and lit the buildings from the side rather than from above, the light that made familiar things look different and sometimes made their significance visible in ways that the overhead light of midday did not.

He looked at Building 7.

The Advanced Projects Division. The northwest corner of the compound. The team that had built the Arjuna and was now building the Dhanush.

He thought about the two names.

Arjuna and Dhanush.

The warrior and his bow.

He thought about what came after.

He thought about the counter-battery radar that the intelligence summary had named and that Ghosh had correctly identified as the third system in the artillery equation — the system that detected enemy fire so that your own fire could respond. The system that meant not only that your artillery could operate outside the enemy's counter-battery range but that you could locate the enemy artillery that was operating within your range.

The system that closed the loop.

He had said, in the meeting, that the counter-battery radar was on the list but not for today.

He opened his notebook.

He wrote: 9 October 1974. Dhanush programme initiated. System A (40km) and System B (35km). Both indigenous. Timelines: System A June 1975, System B August 1975.

He looked at what he had written.

Then he wrote:

The bow requires the archer. The archer requires the bow. And the archer who cannot see the target cannot aim.

The third programme begins tomorrow.

He closed the notebook.

He left Building 7 and walked across the compound in the October evening, and the flag above the main building was catching the low light and moving in the mild October wind, and the compound around him was doing what it always did — working, making things, building the specific physical objects that turned security from an abstraction into a fact.

He walked through it.

He was already thinking about what came next.

End of Chapter 173

Dhanush Programme — Initiated 9 October 1974

Threat Context: 12 AN/TPQ-37 Firefinder counter-battery radar systems acquired by People's Republic of China from the United States. Estimated deployment timeline: 18-24 months. Detection range: 30km for artillery. Location accuracy: 50m at 10km. Computation time: under 90 seconds.

Operational implication: Any Indian artillery that fires within 30km of a Chinese Firefinder-equipped position can be located within 90 seconds and engaged by counter-battery fire. Current Indian artillery maximum range: 20km. This creates a lethal range asymmetry in the Himalayan sector.

Programme Response:

Dhanush-40 (System A): Calibre: 155mm Barrel: L52 (8m, smoothbore) Range: 40km standard, 50km+ with extended range munitions Platform: Tracked, SDG-1000 engine (1,000 hp) Weight: 42-45 tonnes Crew: 4 (commander, driver, gunner, loader) Ready-to-fire time: 180 seconds Displacement time: 90 seconds Mine protection: V-hull, Arjuna standard Target completion: June 1975

Dhanush-35 (System B): Calibre: 155mm Barrel: L39 (6m, smoothbore) Range: 35km standard, 40km with base-bleed ammunition Platform: Tracked, lighter chassis, SDG-1000 engine Weight: 33-36 tonnes Crew: 4 (same as System A) Ready-to-fire time: 180 seconds Displacement time: 90 seconds Optimised for: High-altitude mountain terrain, constrained access routes Target completion: August 1975

Shoot-and-scoot doctrine analysis:

Firefinder detection to location output: 90 seconds Counter-battery rounds in flight: 75 seconds (at 30km range) Total: impact at 165 seconds from first Dhanush round Dhanush displacement time: 90 seconds Margin: 75 seconds

Team — Advanced Projects Division: Dr. Anand Krishnaswamy — Programme Technical Director Suresh Nair — Propulsion Dr. Meenakshi Subramaniam — Armour and Crew Systems Major (Retd.) Balram Singh Mehta — Crew Systems/Training Brigadier (Retd.) Harshvardhan Singh — Operational Requirements Dilip Bose — Suspension and Chassis Ravi Shankar Pillai — Engine Development (altitude operation) Vikram Iyer — Barrel and Armament Parimal Ghosh — Fire Control and Computing

All components: 100% indigenous production, no imported parts in production specification

Next programme: Indigenous counter-battery radar (designation pending)