A magazine explainer for the thinking Indian citizen

 Somewhere between a WhatsApp forward claiming India "faked" 7.8% growth and a government press release calling it a triumph, most Indians have quietly given up trying to understand their own economy's report card. That's a problem, because GDP arguments aren't abstract — they decide whether your child's first job is secure, whether the rupee buys less petrol next year, and whether "India growing" means you growing.

This piece takes twenty-two of the sharpest questions Indians have been asking about the Q1 FY2026-27 GDP number — 7.8% real growth, a rival "2.6%" claim, a mysterious base-year change — and answers them one at a time, in plain language, with Indian examples and a look at how other countries have wrestled with the same demons: rebased economies, doctored statistics, jobless booms, and technology built at home but owned abroad.

The one-line verdict up front: the 7.8% figure is a legitimate number from a recent (if badly communicated) statistical overhaul; the rival 2.6% figure is valid only for an earlier base. But both camps are arguing past the real question — not "did the economy grow?" but "who is the growth for, and who owns what it built?"

First, the four measures everyone throws around

Before the fireworks, the flashcards. Four numbers get quoted in every GDP story, and mixing them up is where half the confusion begins.

GDP — Gross Domestic Product. The total market value of everything final that got produced in the country in a period. It answers: how big and how fast is the economy?

GVA — Gross Value Added. What producers and sectors actually add, once you strip out the inputs they bought. If a Tiruppur garment unit sells ₹100 crore of clothes made from ₹60 crore of fabric and yarn, its GVA is ₹40 crore. GVA tells you which sectors are creating value — agriculture, manufacturing, services — and India's GDP and GVA growth rates can diverge because of taxes and subsidies sitting between the two.

PFCE — Private Final Consumption Expenditure. What households actually spend — food, rent, school fees, phone bills, the works. It answers: how much are people consuming? It's the single largest slice of India's GDP, so a good PFCE print usually means a confident consumer — though inflation alone can inflate it too.

GFCF — Gross Fixed Capital Formation. Money sunk into things that will keep producing for years: factories, machines, roads, software. It answers: how much is the economy investing in tomorrow? "Gross" means depreciation hasn't been subtracted yet, and it excludes financial punts like buying shares.

None of these four numbers directly measures your salary, your job security, or how evenly the gains are shared. Keep that sentence in your back pocket — you'll need it by the end of this piece.

What exactly are we even fighting about?

Before deciding whether 7.8% is impressive or a scam, is this a dispute about economic activity, methodology, inflation adjustment, or outcomes?

All four, but they don't deserve equal airtime. The much-shared 2.6% number is simply not a valid calculation — more on that in a moment. The genuine live argument is a technical one: do India's new price deflators measure real activity accurately? The bigger, more consequential argument is developmental: does this output turn into jobs, wages, private investment, and technology India actually owns? Treat arithmetic, measurement, and development as three separate courts, or you'll convict the wrong defendant.

Round 1 — Doing the Maths Honestly

"2.6% growth" — the viral number that isn't a number

Is the claim that India grew only 2.6% based on a fair comparison?

The 2.6% figure compares Q1 FY27 nominal GDP of ₹88.27 lakh crore, measured under India's new 2022-23-base series, against Q1 FY26 nominal GDP of ₹86.05 lakh crore measured under the old 2011-12-base series. That's like comparing your height measured in centimetres this year against your height measured in inches last year and calling the difference "growth." The valid comparison — new series against new series — is ₹88.27 lakh crore against a revised ₹80.00 lakh crore: 10.3% nominal growth and 7.8% real growth. The 2.6% figure is a useful red flag about how large the revision was; it is not an alternative official growth rate.

Why can't figures from two different base-year series simply be combined?

Because a base-year change resets sector weights, data sources, price indices and estimation methods all at once. Combining old-series and new-series numbers treats a statistical redesign as if it were real economic change — it's not a conservative estimate, it's an invalid ratio, full stop.

Indian context: This isn't India's first base-year change — the country moved from a 2004-05 base to a 2011-12 base in 2015, and that revision also sparked confusion when it retrospectively lifted growth estimates for 2013-14. Base revisions are a recurring ritual in Indian GDP-watching, not a one-off scandal.

Global comparison: Nigeria offers the most dramatic version of this confusion. When it rebased its GDP from a 1990 base year to a 2010 base year in April 2014, its estimated economy leapt by 89% overnight — instantly making it Africa's largest economy, ahead of South Africa. The updated figures did reflect genuinely under-measured sectors, like telecom and the Nollywood film industry, but they also sat alongside the country's real, unchanged problems — low fiscal revenue, weak job creation, persistent poverty. No Nigerian became 89% richer that morning — the ruler changed, not the country. India's much smaller revision provoked outsized panic partly because nobody drew that Nigerian-style picture for the public in plain language.

Once you compare like-with-like, how much should we trust the 7.8%?

Moderate confidence, not blind faith. The number is internally consistent — it's backed by 8.2% real GVA growth, 9.2% manufacturing growth, 10.0% services growth, 7.1% consumption growth (PFCE) and a strong 11.9% investment growth (GFCF). But it remains provisional and sensitive to the deflator (see Round 2), so transparency and independent replication still matter before anyone chisels it into stone.

Has the debate confused nominal GDP, real GDP, and revisions?

Yes, constantly. Nominal GDP is value at today's prices; real GDP strips out inflation to show volume; a revision changes the estimate of an earlier period using better data. A lower revised base can mathematically raise this year's growth rate without any manipulation — but the statistics office owes the public a clear explanation of exactly why the earlier number changed, not just a new number dropped without a bridge.

Was India's real growth actually close to zero this quarter?

Not as any defensible national-accounts estimate — that reading only survives if you deliberately compare mismatched series and then bolt on an assumed inflation adjustment. But here's the honest caveat: a household's felt growth can be close to zero even when the national number is genuinely 7.8%, if wages, job security, and purchasing power for that household haven't moved. That's a distributional judgment about who's benefiting, not a rival estimate of total output. Both things can be true at once — remember this, because it becomes the spine of the whole article.

Round 2 — Why Last Year's GDP Suddenly Got Smaller

Is a revision this size normal?

Revisions are routine whenever base years, data sources, weights and deflators change — but a jump this large demands unusually clear communication, even though "unusual" doesn't mean "illegitimate." The entire historical series has to be rebuilt from scratch for old and new numbers to stay comparable.

Does the new methodology genuinely improve accuracy?

In principle, yes. It draws on broader administrative and enterprise data (GST filings, corporate ministry records, e-Vahan vehicle registrations), updated household surveys, over 300 price indicators, better informal-sector coverage, and "double deflation" in manufacturing (explained below). But "in principle better" is not the same as "proven better" — that requires the back series, source notes and replication files to be made public, which as of this writing they largely haven't been.

Has the scale of revision, even if legitimate, created a trust problem?

Yes — and this is where India's statisticians have genuinely fumbled the ball. The public first saw an ₹86.05 lakh crore figure, then a revised figure near ₹80 lakh crore, then a fresh ₹88.27 lakh crore figure — with no immediate, plain-language bridge explaining the jumps. Being technically correct doesn't erase a communication failure. Credibility needs a visible paper trail, not a black box.

Global comparison — the cautionary tale: Argentina shows what happens when a statistics office loses that trust entirely. After its national statistics agency, INDEC, was politically overhauled in 2007, its officials were widely accused of tampering with inflation figures, and Argentina went on to become the first country the IMF ever formally censured for submitting inaccurate inflation and growth data. Independent economists ended up running their own private price-tracking websites just so ordinary Argentines had numbers they could trust — down to things as mundane as adjusting a divorce settlement for real inflation. India's MoSPI is nowhere near that credibility crisis, but the lesson stands: once citizens stop trusting the referee, no number — however honestly calculated — will be believed. India's fix is cheap by comparison: publish the revision ledger.

Why did the new series make earlier years look smaller?

Reweighted sectors, revised informal-sector estimates, new industrial and price data, different price treatments, and improved statistical-discrepancy adjustments can all lower a historical estimate. It means the ruler changed — not that the economy physically shrank in hindsight.

What should MoSPI publish so outsiders can check its homework?

A machine-readable comparable back series, a vintage-by-vintage revision ledger, sector weights, granular deflators, source-coverage notes for GST/MCA/PLFS/PFMS/e-Vahan data, and reconciliation tables — with independent review built into the release process itself, not bolted on after controversy erupts.

Round 3 — The Deflator: India's Real Technical Fault Line

This is the one genuinely wonky bit worth understanding, because it's where honest critics have their strongest point.

Is a GDP deflator of around 2.3% believable right now?

It's possible, because the GDP deflator prices a different, broader basket than retail inflation (CPI) or wholesale inflation (WPI) — but it looks unusually low next to both. That makes it a candidate for audit, not an automatic disproof of the growth number. The real test is whether the underlying output and input prices reflect actual transactions across sectors, not guesswork.

Why shouldn't the GDP deflator track CPI or WPI anyway?

CPI tracks what households buy at retail; WPI tracks wholesale goods. The GDP deflator is an implicit, economy-wide price measure covering investment, government services, exports and imports too — it can legitimately diverge from both. But a persistent, large gap needs an explanation, not a shrug.

How does "double deflation" let real growth beat nominal growth?

It deflates a sector's output prices and its input prices separately, instead of applying one blanket index to everything. If input costs (say, steel and energy for a factory) rise faster than what the factory can charge for its products, nominal value added gets squeezed even while the physical volume of goods produced keeps climbing. So real GVA can genuinely outpace nominal GVA — the arithmetic is sound, but its reliability rides entirely on how good the underlying price data is.

Does double deflation make things more accurate, or more fragile?

Both, honestly. It's more accurate when input and output prices are well measured, because it stops one broad index from being force-fitted onto unlike items. But it's also more sensitive — an error in either price series distorts the "residual" value added, so India needs granular, transparent price data to make this method trustworthy rather than a black box that quietly produces flattering numbers.

Is 9.2% manufacturing growth real, or a methodology artefact?

The wider evidence — corporate sales, electricity use, GST collections, capital-goods output — points to genuine industrial expansion. But the exact 9.2% figure, sitting alongside 7.7% nominal growth and an unusually low deflator, is a gap large enough to deserve item-level cross-checks against real-world indicators before being taken as gospel. Real growth with an uncertain precise magnitude is the honest verdict — not fraud, not full confidence either.

Round 4 — Does the Rest of the Economy Back Up the Headline?

What independent, real-world signals support 7.8%?

Vehicle registrations, capital-goods production, cement and steel output, electricity consumption, bank credit growth, GST collections, corporate capex announcements, payroll additions, and a strong 12.0% real export growth all point the same direction. No single indicator is decisive, but together they make a "zero real growth" story implausible.

What contradicts or complicates the story?

Agriculture grew only 3.6%; mining actually contracted 2.4%. Rural demand, real wages, informal enterprises, private capex intentions, and some manufacturing-sentiment surveys remain patchy, and declining foreign investment plus currency pressure complicate any tidy "boom" narrative. These don't erase the growth — they narrow its width and question its quality.

What's actually driving growth — consumption, government spending, investment, or exports?

A mixed bag tilted toward public capital spending, formal services, and select manufacturing clusters, rather than one broad-based private investment wave. Consumption (PFCE) grew 7.1%, investment (GFCF) 11.9%, exports 12.0% — but whether private capex and rural demand can carry the baton is still the real test of durability.

How broad-based is the boom across sectors, regions and incomes?

Uneven, by design of the numbers themselves. Urban formal services, listed companies, and specific manufacturing clusters are running hot; agriculture, informal businesses and lower-income households are lagging. Premium consumption — SUVs, five-star weddings, iPhones — can surge even as mass-market purchasing power stays flat, producing what analysts call a K-shaped recovery: two diverging lines on the same chart, not one rising tide.

Can GDP boom while ordinary households feel stuck?

Yes, unavoidably. GDP measures total production, not median wages, job security, household debt, or how gains are shared. Employment can technically "rise" through gig work or casual labour even while secure, well-paid jobs stay scarce. Both a genuinely valid 7.8% output number and real public frustration can be true in the same country, in the same quarter. This is the crux the entire rest of this article now turns to.

Round 5 — Rajan vs. Vembu: Two Diagnoses, One Patient

Two of India's sharpest public voices — economist Raghuram Rajan and technology entrepreneur Girish Mathrubootham/Zoho's Sridhar Vembu — have been read as contradicting each other in recent months. They aren't. They're examining two different organs of the same patient.

Are Rajan and Vembu really disagreeing?

Not fundamentally. Rajan's question is: why isn't growth producing enough decent jobs, private investment, and human capital? Vembu's question is: why does India capture so little of the technology, intellectual property, and profit margin from the work actually done here? One diagnoses the employment outcome; the other diagnoses who owns the value chain. Complementary, not competing.

Can low-paying assembly jobs become a ladder to something better, the way they did in East Asia?

Yes — but only when assembly is deliberately used as a learning platform, not treated as the finished product. South Korea and Taiwan didn't stay content-to-assemble; they used early low-value assembly contracts to build domestic suppliers, engineering talent, export capability and eventually world-beating firms of their own (think Samsung's leap from assembling foreign electronics to designing its own chips, or TSMC becoming the company Apple and Nvidia depend on rather than the other way round). Without those deliberate conditions, assembly work becomes a permanent low-wage enclave — a treadmill, not a ladder.

What makes an assembly ecosystem actually build local suppliers, skills and IP?

Time-bound incentives tied to rising local content, supplier development, apprenticeships, R&D spending, domestic patents, export sophistication and productivity — with firms required to publish capability milestones and lose their support if they miss them. Support without a scoreboard just becomes permanent subsidy.

How long should India accept lower wages while companies "climb the value chain"?

Only as a clearly defined transition — never an open-ended promise. A five-to-ten-year support envelope, reviewed every three to five years, with subsidies tapering automatically if wages, skills, local suppliers and R&D fail to improve, is the discipline that separates genuine industrial policy from indefinite corporate welfare.

Does India need millions of ordinary jobs, or fewer high-productivity ones?

Both, simultaneously. India needs accessible jobs now for workers still moving out of low-productivity farming, and a parallel expansion of high-productivity careers in engineering, design, digital services and advanced manufacturing. Picking only one horn of this dilemma leaves the other problem — mass employment or national productivity — permanently unresolved.

Can high-value services and startups alone create enough jobs?

They can generate excellent, high-paying, export-earning employment — but not at the scale India needs. Roughly 11 million people are expected to enter India's workforce every year for the next two decades. Manufacturing, construction, logistics, tourism, and care work will have to carry much of that load; software unicorns cannot absorb a labour force that size on their own.

What does a real career pathway from a ₹20,000 factory job actually look like?

Apprenticeship → portable certification → process and quality training → promotion to technician or supervisor → movement into supplier engineering → eventually design or R&D roles. It requires employers who actually run engineering functions in India, continuous upskilling, basic social protection, and wages tied to measured productivity gains — not just tenure.

Round 6 — Who Actually Owns the Value?

This is the section every Indian techie, founder, and policymaker should read twice.

Does hosting global R&D automatically mean India captures the value?

No. Global Capability Centres (GCCs) in Bengaluru, Hyderabad and Pune generate real wages, local procurement, tax revenue, and genuine skill-building — all valuable — but the parent multinational typically retains the intellectual property, the licensing income, the platform rents, and the commercial profit, booked abroad. A GCC's headcount is not the same thing as ownership of the technology those employees built.

How much of the value Indian engineers create shows up in India's GDP?

There's no single reliable percentage — that's precisely the problem. Indian GDP captures wages, domestic profit, local inputs and taxes; the IP royalties, equity gains, and profits recognised in a parent company's home country are largely not counted as Indian value-added. Getting a precise number would need firm-level accounts and detailed supply-chain data that mostly don't exist publicly yet.

Is comparing Indian headcount to a multinational's global profit meaningful?

Too simplistic to use as an accounting argument, though the direction of the comparison is a fair provocation. Profit also depends on IP ownership, capital, risk-taking, transfer pricing, and global market control — not labour input alone. The asymmetry it illustrates is real; the specific ratio isn't rigorous.

Does owning IP matter more than manufacturing volume for wages?

For sustained wage growth, yes — ownership of scarce technology and commercial rights is usually more decisive than sheer manufacturing volume. High-volume assembly without design ownership or supplier power tends to keep both margins and wages anchored close to bare labour-cost competition.

Global illustration: This is exactly the trap South Korea and Taiwan escaped and many other assembly-hub economies haven't. A country can host enormous manufacturing volume — think of the "world's factory" label applied at different times to Mexico's maquiladoras or Vietnam's electronics-assembly boom — without ever owning the brand, the chip design, or the software stack that captures the lion's share of the final retail price.

What would encourage more India-owned, India-commercialised IP?

R&D tax credits tied specifically to domestic patenting and commercialisation (not patent-filing alone), stronger university-industry technology transfer, patient deep-tech capital, government acting as an anchor customer for homegrown tech, and better standards, procurement and IP enforcement.

Domestic champions, technology transfer, or MNC incentives — which does India need?

All three at once. Domestic champions create genuine Indian ownership; better technology-transfer mechanisms build capability; predictable incentives can persuade multinationals to locate real decision-making and IP functions inside India rather than just assembly lines. No single lever closes this gap alone.

Can India capture more value without scaring off the MNCs that employ Indian engineers?

Yes — through predictable rules, strong IP protection, deep skilled talent, deep capital markets, and incentives for local R&D, rather than punitive restrictions. The goal is parallel ecosystem-building: keep attracting multinationals while simultaneously making Indian firms capable of owning, financing and commercialising their own technology.

Round 7 — Does India Need a Sharper Industrial Policy?

Is industrial policy necessary for a developing country to build technological capability?

Usually, yes. Late developers face coordination failures — in skills, suppliers, finance, technology — that markets alone often can't solve fast enough. But industrial policy has to be disciplined, transparent and temporary; its job is to buy capability, not protect inefficiency forever.

Is India's current industrial policy building competitive firms, or subsidising assembly?

A mixed picture, with a genuine risk of subsidising assembly for its own sake — rewarding output volume more than R&D, local components, exports, or productivity gains. The real test isn't the size of the incentive announcement; it's whether domestic supplier depth, patents, engineering decision-making, wages, and export sophistication are actually rising over time.

What separates good East Asian industrial policy from protectionism and cronyism?

Successful programmes tied support to exports, productivity, local capability-building and technology learning; exposed firms to genuine competition; reviewed performance regularly; and withdrew support on a pre-announced schedule. Protectionism shelters firms without demanding results; cronyism picks beneficiaries without any public performance test at all.

Should support require R&D, local IP, exports and productivity — not just production?

Yes. Production should be an entry condition, not the finish line. Support should also demand R&D intensity, domestic patents, local suppliers, export complexity, worker training, rising productivity and wages, and energy efficiency.

How long before an industry is expected to compete on its own?

A pre-announced five-to-ten-year window, with milestone reviews every three to five years and automatic tapering — varying by sector, but with the discipline that missing capability milestones triggers withdrawal of support, not renewal through lobbying.

Is India's real choice "become Mexico" or "become East Asia"?

Too narrow a frame. India can combine labour-intensive manufacturing for mass jobs, high-value services for exports, digital public infrastructure (UPI, Aadhaar, ONDC) for productivity, and entrepreneurship for innovation — a genuinely hybrid Indian model rather than a copy of any single country's playbook.

Round 8 — Growth, Imports, and the Rupee

Can strong GDP growth coexist with pressure on the rupee and the current account?

Yes, routinely. Catch-up growth raises demand for imported energy, machinery, semiconductors, software and capital goods. If imports outpace exports, the current account and the currency can come under pressure even while real GDP is growing rapidly — India has lived this cycle before, notably around 2012-13.

Does faster growth deepen import dependence before domestic capability catches up?

Yes, especially in data centres, semiconductors, renewable-energy hardware and advanced machinery. That's not automatically bad — productive imports can build future capacity — but it becomes a genuine risk if domestic suppliers, R&D and skills never scale up to replace them.

How much domestic value does India actually retain from import-heavy exports?

It varies too much by product for a single number to be honest. Domestic value is wages, local services, logistics, taxes and Indian profit; imported components and foreign-owned technology largely pass through with limited retention. India's supply-and-use tables should publish sector-specific domestic value-added shares rather than leaving this to guesswork.

Is telling citizens to cut foreign travel, weddings abroad, and gold buying meaningful, or symbolic?

Mostly symbolic at the macro scale — though not entirely irrelevant. The decisive foreign-exchange pressures come from energy, capital goods, and technology imports, not household discretionary spending. Policy shouldn't offload a structural, national-level responsibility onto individual moral appeals.

Should the burden fall on households, or on energy and technology policy?

Policy has to lead. Energy diversification, domestic capital-goods manufacturing, technology capability-building, export upgrading and stable trade rules matter far more than broad appeals asking households to tighten their belts. Targeted restraint can help at the margins — it cannot substitute for industrial and energy strategy.

Which imports are wasteful, and which are investments in the future?

Luxury consumption and non-essential gold generally add little productive capacity. Machinery, semiconductors, software, renewable-energy equipment and R&D tools may worsen the near-term trade balance but count as investment if they raise productivity, capability, or future exports. The test is future learning value, not the import label itself.

How long before India's tech and energy import dependence meaningfully shrinks?

Technology dependence is roughly a 10-to-15-year project if R&D, skills, and manufacturing scale up consistently. Energy dependence will likely take longer — 15 to 20 years — because it involves transport, storage, grids, and industrial fuel substitution all moving together. These are planning horizons, not guarantees.

Round 9 — Big Investment Announcements vs. Real Transformation

Are giant investment announcements being mistaken for actual value creation?

Often, yes. An announcement is a commitment, not proof of money spent, domestic value added, jobs created, or technology transferred. Data centres may be strategically important, but their direct GDP and employment effects can be modest relative to the headline capex numbers splashed across newspapers.

How much spending on a new data centre flows straight back out through imported GPUs, servers and cooling systems?

A significant share can leak abroad, though the exact proportion depends entirely on project design and procurement choices. GPUs, servers, cooling and networking equipment are import-intensive, so the domestic value of the construction phase shouldn't be mistaken for the value of the entire investment. Real answers need project-level bills of materials, not press-release arithmetic.

Can data centres still deliver big second-order benefits?

Yes — through cloud services, home-grown AI companies, and digital exports — but only if Indian firms actually build products and services on top of that infrastructure. Without domestic platforms, skills, data governance and genuine customer demand, India risks hosting foreign digital workloads while retaining mainly construction, power, and facility-management jobs.

What needs to be built around this infrastructure to capture more value?

Domestic cloud and server capability, chip and component supply chains, reliable green power, AI and cybersecurity skills, data governance frameworks, compute credits for startups, public procurement support, and export channels. The goal is Indian firms owning the models, applications and customer relationships — not merely renting out imported compute.

Should capital-heavy infrastructure be judged by different metrics than mass-employment sectors?

Yes. Data centres deserve to be judged on strategic resilience, productivity spillovers, digital exports, energy use, and technology ownership. Textiles, food processing, tourism, and care work should be judged far more heavily on jobs created. A single "jobs-per-rupee" test would undervalue infrastructure investment; a single capex test would quietly hide weak employment outcomes.

What separates "hosting compute" from building a genuine indigenous AI economy?

An indigenous AI economy has Indian-owned models, datasets, applications, patents, firms and export revenues — built on top of domestic compute and talent. Simply hosting foreign hyperscalers' servers, without local ownership, builds infrastructure capacity while leaving the highest rents and strategic control sitting elsewhere.

Round 10 — GDP vs. Lived Reality

Can the 7.8% number be statistically sound while public frustration is equally legitimate?

Yes. GDP measures the volume of production; it says nothing about median wages, job security, household debt, inequality, or public confidence. A valid national number and a genuinely weak household economy can coexist in the very same quarter, in the very same country.

Has India put too much political weight on one single number?

Yes. A quarterly GDP print has become an all-purpose proxy for national welfare, even though it was never designed to measure welfare in the first place. It deserves to sit as one indicator on a public dashboard — not stand as a verdict on every household's life.

What indicators should accompany every GDP release?

Employment, real wages, private investment, household consumption by income group, productivity, and per-capita income — alongside labour-force participation, female workforce participation, payrolls, vacancies, hours worked, rural incomes, private capex, external balance and emissions. Quantity of growth and quality of growth need to be reported together, every single quarter.

Does the new series capture informal workers, gig workers and household enterprises properly?

Better than the old series — through GST data, enterprise surveys, the Periodic Labour Force Survey, e-Vahan and other administrative sources — but still imperfectly. Informal and gig activity is often estimated indirectly, and small household enterprises can slip through the gaps between survey rounds. More frequent surveys and anonymised microdata would close this gap.

What should "quality growth" mean for a country at India's stage of development?

Rising productivity accompanied by rising real wages, secure and formalising jobs, stronger rural incomes, higher female workforce participation, domestic technology and IP ownership, export competitiveness, and resilience to energy and climate shocks. Growth has to widen opportunity — not just expand output inside a handful of capital-intensive enclaves.

How do we stop legitimate scrutiny from collapsing into partisan denial of the whole economy?

Separate technical adjudication from political theatre. Publish methods and revision ledgers, allow independent replication, clearly flag what remains provisional, and always read GDP alongside jobs, wages and investment data. Criticising a method should never be twisted into denying real economic activity; celebrating activity should never be used to silence legitimate scrutiny either.

Closing Question — Measurement Problem, or Development Model Problem?

Suppose the 7.8% figure is methodologically sound. If India keeps growing fast while staying dependent on imported energy and technology, capturing limited value from work done here, and struggling to create better-paying jobs — is that a measurement problem, or a development-model problem? And ten years from now, will it matter more how fast GDP grew, or how much technology, IP, productive capacity and prosperity India actually kept?

Primarily a development-model problem, with a continuing measurement-and-credibility problem sitting at the margins. Accurate GDP growth can perfectly well coexist with weak value capture, import dependence, and poor job quality — India's own recent history is proof of concept. Ten years out, the decisive scoreboard won't be a quarterly growth print; it will be domestic IP, supplier depth, productive skills, real wages, energy resilience, and how broadly prosperity actually spread. The growth rate is necessary evidence of India's story. It is nowhere near sufficient evidence of India's development.

A note on statistical honesty, for the record

None of this is unique paranoia. For years, China's own provincial GDP figures, added together, ran higher than the national total the central government reported — a gap widely traced to local officials whose careers depended on flattering growth numbers, most visibly when Liaoning province's governor publicly admitted in 2017 that city and county officials there had fabricated growth and fiscal data for three straight years. India's episode is nowhere near that scale of deliberate fraud — this is a genuine base-year revision with a communication failure, not a cover-up. But the comparison is a useful reminder of what real data manipulation looks like, so citizens can tell the difference between a badly explained methodology and an actually rigged number.