Hi Friends,

Even as I launch this today ( my 80th Birthday ), I realize that there is yet so much to say and do. There is just no time to look back, no time to wonder,"Will anyone read these pages?"

With regards,
Hemen Parekh
27 June 2013

Now as I approach my 90th birthday ( 27 June 2023 ) , I invite you to visit my Digital Avatar ( www.hemenparekh.ai ) – and continue chatting with me , even when I am no more here physically

Translate

Friday, 23 October 2026

The Layoff You Can't Audit: Amex cut 3,500 people after a record quarter 'to prepare for AI' — and the only bill that would make it verifiable is stalled

The Layoff You Can't Audit: Amex cut 3,500 people after a record quarter 'to prepare for AI' — and the only bill that would make it verifiable is stalled

American Express cut about 3,500 jobs in the same week it reported record revenue of $20.1 billion. Its CFO said the restructuring would help the company "prepare for AI" — a forecast used as a cause. This post argues that the AI-jobs debate has become a question of verification, notes that the Warner–Hawley disclosure bill that would settle it is stalled, and asks India, whose IT firms run the world's largest entry-level training pipeline, to publish auditable AI-workforce data, employer-confirmed placement counts and competency-verified credentials — not a list of safe professions.

On Friday American Express reported record third-quarter revenue of $20.1 billion, net income up 28% to $3.7 billion, and a $336 million restructuring charge — then said it would cut about 5% of its workforce, roughly 3,500 jobs. Chief financial officer Christophe Le Caillec told CNBC the aim was to be "leaner, more agile, and also to prepare for AI."

Not "because AI now does this work". To prepare for AI. The automation has not happened; the layers are coming out in advance of it. A forecast is being used as a cause. Barclays, the day before, put the same move more politely: 5,000 jobs, about 60% of them in support functions including developers, with chief executive C.S. Venkatakrishnan telling the BBC that "AI is the icing on the cake, not the cake."

The ledger grows long and soft at once. The Reuters factbox of 22 October lists 35 AI-linked cut announcements across 32 companies since October 2025, summing to about 102,800 jobs at the stated low ends — though Reuters publishes no total and claims no company-by-company causation. A Gartner survey of 350 executives at firms running AI agents, reported this week, found 80% had cut headcount, and the heaviest cutters posted returns almost identical to the lightest.

The only firm-level evidence of what agents do to hiring came from Anthropic on 16 October: the junior share of its technical hires fell from 27% to 9% since early 2025, the junior share of technical staff from 21% to 14%, and by August its interactive agents logged about six hours of work per human hour. These are shares, not headcounts. "Junior" is undefined. There is no independent audit. And Anthropic tripled in size over the same year, so 9% of a growing base is not necessarily fewer beginners. The Guardian reported on 23 October that experts are sceptical. That same day the New York Times reported that economists see no evidence AI has altered the labour market on a grand scale — as a hundred thousand unattributed cuts sit on the record.

In April, in "Who Should Speak on Jobs?", I closed with five asks. One was this: "Regulate disclosure: require firms to report significant workforce impacts tied to AI deployments so policymakers can act on data rather than anecdotes." That sentence now has a bill number. The AI-Related Job Impacts Clarity Act, S. 3108, introduced by Senators Mark Warner and Josh Hawley in November 2025, would require publicly traded companies and federal agencies to report AI-related layoffs, hires, unfilled posts and retraining to the Department of Labor each quarter, with the Bureau of Labor Statistics publishing the data. It is still in committee. On 23 October Senator Ron Wyden released two bills that fund the aftermath — income support for retraining, and a data-centre excise tax. Neither measures the cause.

India's exposure is not Amex's middle layer. It is exactly the rung Anthropic measured. Infosys hired 8,000 graduates in the September quarter and holds a 20,000 FY27 target; HCLTech onboarded 6,136 freshers, up from 1,056; TCS had 25,000 offers out, about 14,000 onboarded by end-Q1; Wipro shed 6,716 people net. Indian IT services is now the world's largest remaining entry-level training institution, and it publishes none of this as a placement outcome. On Saturday, Amar Ujala reported from Berlin that Shri Piyush Goyal has asked his ministry to identify the professions AI will not displace. A list is not a ladder.

So, in order: auditable AI-workforce disclosure, on the Warner–Hawley model, in India too; published, employer-confirmed placement counts, as I proposed in "Tracking Real Placements"; and the competency-verified credential of April's National Job Skilling Policy discussion, not a safe-professions list. The first tells us what is happening, the second whether training leads anywhere, the third what to learn. None of the three asks us to believe a press release.

With regards,
Hemen Parekh
www.Iam-Immortal.ai / www.IndiaAGI.ai / www.YourContentCreator.in
24 Oct 2026

The ₹1-Crore Job India Cannot Fill: we built the demand, we forgot the pathway

The ₹1-Crore Job India Cannot Fill: we built the demand, we forgot the pathway

India spent years building demand for AI deployment work and never published a route onto it. The Scaler–CMR report says 88 per cent of enterprises expect forward deployed engineer demand to rise by 2030, yet 1 per cent of engineers hold the role and nine in ten know of no structured pathway. This is a matching failure, not a skills failure. The post asks for a competency-verified deployment credential and a live matching layer, and notes that the plumbing already exists in UP — for welders, not engineers.

Two reports landed three hours apart this morning, and read together they say what neither says alone. The first is Scaler and CyberMedia Research's India's FDE Opportunity Report 2026: 88 per cent of enterprises expect demand for forward deployed engineers to rise by 2030, 77 per cent of multinationals have defined hiring intentions for the next twelve months, and 98 per cent say the role will not remain a niche (Indian Express, 23 October; Business Standard, 23 October).

One per cent. That is the share of Indian engineers actually working in dedicated FDE roles. Of those who are, 80 per cent report annual incomes between ₹40 lakh and ₹1 crore.

This is the third panel of a trilogy I did not plan. On 20 October I wrote about the broken first rung: 1.23 lakh tech openings in India, only 15,000 for freshers. On 22 October I wrote about the word "performance" standing between a Bengaluru engineer with nine years in physical design and her notice. Those two posts were about subtraction. This one is about the addition the reports have finally quantified, and about why it will not reach the people who need it.

Here is the sentence I cannot put down. Only 5 per cent of enterprises have dedicated FDE roles, but 56 per cent say similar work is already being performed under other job titles. The job exists. The title, the pay band and the route into it do not. On the supply side, nine in ten engineers say they know of no structured pathway and 52 per cent say they do not know how to become an FDE, while 58 per cent want to (Indian Express). Employers have already moved their tests: 51 per cent assess production deployment and troubleshooting, against 24 per cent who still assess coding. Yet only 19 per cent find deployment skills readily available, and 25 per cent rate customer-engagement capability ready.

The other side of the ledger arrived at 12.43 pm. Embark's GCC report projects up to 1.4 million net new jobs by 2031, taking the workforce from about 2.3 million to 3.3–3.7 million, while AI-led automation moderates demand for routine roles by 400,000–500,000 and India's AI-specialist pool needs to reach 800,000–900,000 (Business Today, 23 October). AskFuzz reads the same quarter as "pyramid to diamond". I am not comforted. Four hundred thousand removed at the bottom and 1.4 million added in the middle is not a balance; it is a gap exactly where the rung should be. The headcount tells the same story: Infosys added 4,480 people in Q2, HCLTech 6,450, TCS 4,258 and Tech Mahindra 5,446, while Wipro shed 6,716 (ETHRWorld, 23 October).

So my ask is not a forecast. Publish the pathway. A competency-verified FDE and deployment credential, built the way the National Job Skilling Policy already frames it — what a person can do on Day 1, assessed by employers rather than by a syllabus (8 April 2026).

Then use the matching layer we already have. UP's Blue DotsAI platform is being extended to all 18 divisions, with a voice bot that takes recruitment requirements in Hindi, English and other regional languages; its Ghaziabad pilot made 25,000 jobs searchable within a 20–25 km radius (Times of India, 23 October; ET Enterprise AI, 23 October). The plumbing works. It currently serves welders, electricians and machine operators. Engineers are not on it. That gap is the whole post.

One caveat, because it protects the argument: the ₹40 lakh–₹1 crore band is self-reported by people already in explicit FDE roles, and the 21–30 per cent premium is an expectation, not a verified market premium — the report says so itself.

In July 2025 I drafted a National Employment Grid on a simple belief: jobs should find people, not the other way around (whitepaper). That was the national version. What we have today is a state version built for trades, a credential policy without the credential, and a crore-rupee job with no published door.

With regards,
Hemen Parekh
www.Iam-Immortal.ai / www.IndiaAGI.ai / www.YourContentCreator.in
23 Oct 2026

Somebody Has Finally Built My Bharat Job Alert Mission. It's in Lucknow — and It's Too Small.

Somebody Has Finally Built My Bharat Job Alert Mission. It's in Lucknow — and It's Too Small.

Uttar Pradesh is taking Blue DotsAI, a map-based AI job-matching platform with a vernacular voice bot, from a Ghaziabad pilot to all 18 divisions. That is close to the Bharat Job Alert Mission I proposed in July 2025, and it proves the MSME-vacancy thesis. But without eShram, Udyam and NCS integration, placement tracking or published placement numbers, it stays a state scheme. On the same day, NSDC's debut on the NSE Social Stock Exchange showed the missing ingredient: outcome-linked money that pays for the last mile only when someone is actually placed.

Uttar Pradesh has just done inside one state what I have been proposing since a 2003 note on mobile job alerts, and I will not pretend I am not pleased.

The Times of India's Lucknow report (23 October 2026) says the UP Skill Development Mission will extend its "Blue DotsAI" platform to all 18 divisions, after a Ghaziabad pilot in which more than 25,000 jobs within a 20–25 km radius were made searchable on a map. Mission director Pulkit Khare signed the MoU with One Step Foundation; the arrangement has been running since June.

Then comes the line that made me sit up:

"An AI-powered voice bot is a key feature of the initiative. Employers and industry associations will be able to register recruitment requirements by speaking in Hindi, English or other regional languages." — The Times of India, 23 October 2026

Prokerala's fuller report adds that the same bot will call candidates, tell them about matching jobs and, with their consent, help them apply.

Compare that with my white paper, Bharat Job Alert Mission (20 July 2025): AI-curated job alerts delivered through SMS, WhatsApp and voice bots, drawn from eShram, Udyam and NCS. The design I argued for is now running in India's largest state.

That is the honest vindication, and it is narrower than it sounds. For years I have argued that tens of millions of MSMEs never advertise a vacancy — not because they have none, but because a job-portal subscription costs more than the vacancy is worth. Blue DotsAI goes exactly where those vacancies sit: welders, electricians, machine operators, apparel, food and beverage, and a workshop owner who registers a requirement by speaking instead of filling a form.

Four things still keep it a state scheme rather than national plumbing:

  • No visible eShram, Udyam or NCS integration, so a candidate's profile dies at the state border.
  • No outcome tracking. In Tracking Real Placements (April 2026) I asked for employer-marked hire confirmations and published district-level dashboards; here we get jobs made searchable and candidates registered, but no placement count.
  • A 20–25 km radius is geography, not a portable profile that follows a worker from Gorakhpur to Gurugram.
  • 25,000 jobs made searchable is an input. Where are the placements?

The day's second signal shows how the last mile could be paid for. NSDC made its debut on NSE's Social Stock Exchange with its first Zero Coupon Zero Principal issue — ₹4 crore from NABARD towards an ₹11.25 crore programme for 600 OBC youth from Madhya Pradesh (Entrepreneur India, 23 October 2026). Three hundred are being prepared for Japan, three hundred for Germany, in caregiving, hospitality, construction and manufacturing. Beneficiaries pay 15%, 35% comes from the exchange, and Madhya Pradesh pays the last 50% only after overseas placement, under a social impact bond with NSDC.

Why does that matter so much? PM-DAKSH trained 1,87,305 candidates between 2020-21 and 2023-24 and placed 96,162 — about 51% (PIB data, 23 October 2026). When half of the training does not end in a job, outcome-linked money is the simplest corrective.

And the plumbing is moving everywhere else too. Haryana is scaling Dual System of Training to 664 trade units across 320 industries in 125 government ITIs for 2026-27 (UNI, 23 October 2026); Kerala is embedding paid apprenticeships in the final FYUP semester with a ₹12,300 monthly stipend (Education Times, 23 October 2026). What is missing is not activity. It is the connection between it.

So my ask is two sentences long. Take Blue DotsAI national, plug it into eShram, Udyam and NCS, and publish placements district by district. And fund the last mile the way Madhya Pradesh just funded language training — pay on placement, not on enrolment. It may take years. The voice bot itself took twenty-three.

With regards,

Hemen Parekh

www.Iam-Immortal.ai / www.IndiaAGI.ai / www.YourContentCreator.in

23 Oct 2026

24,422 Is the Wrong Number: India's AI Jobs Story Is Being Re-Priced, Not Deleted

24,422 Is the Wrong Number: India's AI Jobs Story Is Being Re-Priced, Not Deleted

Two sets of numbers arrived on 23 October 2026. Xpheno counted 24,422 fewer employees across six Indian IT firms; Embark projected 1.0–1.4 million net GCC jobs by 2031 while AI moderated 400,000–500,000 routine roles. Both can be true. What is being sawed off is the entry rung of the services pyramid, where fresher intake, not headcount, is the missing statistic. I extend my four-field restructuring disclosure of 22 October with a fifth field — fresher and apprentice intake — and renew the call to route reskilling money through Co-operative Capacity Centres rather than severance alone.

Two numbers reached me before noon today. One said India's six largest IT firms had 24,422 fewer people on their rolls than a year earlier. The other said India's global capability centres will add 1.0–1.4 million net jobs by 2031. Both were published on 23 October 2026. Both are almost certainly right.

The first is Xpheno's count, carried by Amar Ujala this morning: 92,000 exits against 68,000 hires across TCS, Infosys, HCLTech, Wipro, Tech Mahindra and LTIMindtree, taking the six together from 8,22,144 people in October 2025 to 7,97,722, about three per cent lighter. What that arithmetic does not say is which rung of the ladder went missing.

The second is Embark's India GCCs in the AI Era report, in Business Today by midday: 1.0–1.4 million net jobs by 2031, while automation, slower backfilling and role consolidation moderate demand for routine roles by 400,000–500,000. One door narrows, another opens wider. The same survey found 92 per cent of GCC leaders past selective AI adoption, with realised productivity gains still under 15 per cent.

Side by side, it is the entry rung being sawed off. Quess's healthcare GCC report, out the same day through IANS, counts 67,000 openings for 2026, 93 per cent of them for three to twelve years' experience, with entry-level demand down 12.4 per cent year on year in Q2 2026 even as overall hiring demand rose 6 per cent. Quess also finds just 1.6 AI and data professionals for every projected opening, against 4.8 across all roles, and pay premiums up to 2.5 times the median (The Economic Times).

Scaler and CMR report this morning that 88 per cent of Indian enterprises expect demand for AI-focused engineers to rise by 2030, and that four in five Forward Deployed Engineers earn ₹40 lakh to ₹1 crore a year (The Indian Express). The quarter's own disclosures split: TCS added 4,258, HCLTech 6,450 including 6,136 freshers, Infosys 4,480, while Wipro shed 6,716. AI hiring pressure is heaviest in the three-to-five-year band, 49.1 per cent of active demand (ETHRWorld).

Barclays, meanwhile, will cut about 5,000 jobs worldwide, roughly 1,000 in India, 60 per cent in support functions including developer roles, for £1.1 billion of savings by 2027 (HRMS News).

So 24,422 is the wrong number. Work is not being deleted. It is being re-priced, and the price is falling fastest at the bottom of the pyramid.

Yesterday, writing about Qualcomm, I asked for one disclosure norm: above a threshold, publish in the same announcement the headcount, the functions, the geographies, and whether roles are eliminated or redeployed. Today's data says that is one field short. Add a fifth — fresher intake and apprentice intake, quarter on quarter. Headcount says what happened to people already inside. Fresher intake says whether the door is still open for the twenty-one-year-old outside, and that is the number that separates re-pricing work from closing a generation out.

My second ask stands too. Route the reskilling money through the Co-operative Capacity Centre model I proposed for the 12,000 TCS employees in July 2025 — member-owned, part-time, project-based, CSR-funded infrastructure, work outsourced at half internal cost — and through the redeployment-before-severance rule I set out in AI Layoffs Are 'Dumb'? in May. Severance buys silence. A transition buys capability.

I may be wrong that five fields are enough. But a company genuinely re-pricing skills, rather than shutting the entry gate, should not mind publishing the two numbers that let the rest of us check.

With regards,
Hemen Parekh
www.Iam-Immortal.ai / www.IndiaAGI.ai / www.YourContentCreator.in
23 Oct 2026

Impartial AI muting in Lok Sabha






================================================

 To: 

Shri Ashwini Vaishnaw, Hon'ble Union Minister of Electronics & Information Technology 


Subject: 

An impartial, AI-assisted "Mute the Mike" system for the Lok Sabha: platform,

architecture and agent workflow


================================================

Respected Shri Ashwini Vaishnawji,


Today's report that the Government has asked TV channels to monitor debates and mute panellists whose remarks turn abusive prompted me to write Freedom of Speech ? Yes : Freedom to Hate ? No. In it I revisited two earlier suggestions of mine: that the Hon'ble Speaker should be able to simply mute the mike of a member who uses unparliamentary language (Virtual Parliament, June 2020), and a technology framework that rates speech on a 1 to 5 scale and auto-mutes at levels 3 to 5 (Hate Speech: Prevention Mechanism, December 2023).

The obvious objection is: who decides what is hateful? If an anchor decides, or a ruling-side official decides, the system will be seen as partisan, however good its intentions. So in this follow-up I set out how such a system can be built so that it is not only fair, but visibly and verifiably fair to every party, every language and every member. MeitY's existing assets, especially Bhashini and the IndiaAI Mission, make India unusually well placed to build it.

Seven principles that make it impartial

  1. The House owns the rules, not the Government. Under Article 118 the Lok Sabha regulates its own procedure. The rulebook, word lists and severity scale should be framed by the Rules Committee with members from all parties, and adopted by the House. MeitY's role is only to supply the technology.
  2. Published rules, not secret judgement. Every rule, every listed expression and every severity definition is public, versioned and dated. A member can know in advance exactly what will trigger a mute.
  3. Same rule for everyone. The system does not know, and is not allowed to know, a member's party when it scores speech. Party affiliation is used only afterwards, to test for bias.
  4. AI recommends; the Chair decides. Only the most extreme category (open incitement to violence) is muted automatically, and even that can be reversed by the Chair in one touch.
  5. Mute is short and reversible. A mute lasts seconds, not the rest of the debate, and the member is told why on their console.
  6. Everything is recorded. Every score, every action and every override goes into a tamper-evident audit log.
  7. Fail open. If any component fails, microphones stay on. A technical fault must never silence a member.

Technology platform and system architecture

The platform sits between the members' microphones and the sound and broadcast system, entirely inside Parliament's own secure network. It has six layers.

Layer

What it does

Built on

1. Capture

Takes a digital tap of each seat microphone. Identifies the speaker from the seat console login, not from voice or face.

Existing Lok Sabha conference system

2. Language

Streams speech to text in all 22 scheduled languages, including code-mixed speech such as Hinglish, within about a second.

Bhashini speech and translation models

3. Understanding

A team of AI agents (next section) checks context and scores each utterance against the published 1 to 5 scale.

Indian models trained under the IndiaAI Mission, hosted on-premises

4. Policy

A plain rules engine, not an AI, converts scores into actions exactly as the House has written them.

Open, versioned rule files

5. Action

Warns the member, alerts the Chair, or mutes the mike for a fixed few seconds. Also controls a short delay on the Sansad TV feed.

Sound system and broadcast controls

6. Accountability

Tamper-evident audit log, Chair's dashboard, member's appeal portal and a public transparency dashboard.

NIC infrastructure, CERT-In audited

The whole stack runs on servers inside Parliament, with no dependence on the internet or any foreign cloud. Its source code, models and test results are open to inspection by members and by an independent technical auditor, for example a consortium of IITs.

The AI agents workflow

No single AI model decides anything. Each utterance passes through a chain of specialised agents, and two independent agents must agree before any action is proposed.




Every path to a mute passes through two independent scores, a rules engine the House wrote, and the Chair; every step lands in the audit log that feeds appeals and public reporting.

  1. Transcription Agent. Converts speech to text in the original language, and keeps the audio for the record.
  2. Context Agent. Checks who is being addressed and how: is the member quoting someone, reading from a document, reporting a threat they received, or being sarcastic? Most false alarms come from missing this.
  3. Lexicon Agent. Matches the text against the Lok Sabha Secretariat's own published list of unparliamentary expressions. This step is fully deterministic and explainable.
  4. Primary Scoring Agent. Rates the utterance from 1 to 5 against the published rubric, and must cite the exact words and the rule it relied on.
  5. Second Opinion Agent. A model from a different developer and training lineage scores the same utterance independently, actively looking for innocent readings.
  6. Policy Engine. Not an AI. It applies the House's written rules to the two scores. If the two agents disagree, the lower score prevails and the case goes to the Chair.
  7. Action Agent. Carries out only what the Policy Engine allows: a warning, an alert, or a timed mute.
  8. Audit Agent. Writes every step, with timestamps, scores, reasons and rule version, into the tamper-evident log.
  9. Fairness Monitor Agent. Runs in the background, comparing outcomes across parties, languages, regions and genders, and raises an alarm if any group is treated differently.

What happens at each level

Level

Meaning

Action

1

Distasteful

Logged only

2

Offensive or unparliamentary

Private reminder on member's console; Chair may expunge

3

Personal attack or abuse of a community

Chair alerted with transcript; Chair decides to mute

4

Dehumanising or threatening language

Chair alerted; automatic 10-second mute unless Chair cancels within 3 seconds

5

Inciting violence or outright hate

Immediate automatic mute; Chair can restore at once

The exact thresholds and mute durations above are illustrative. They are for the Rules Committee to set.

Safeguards that prove impartiality

Human oversight. The Hon'ble Speaker, or whoever is in the Chair, keeps final authority at every level. The Chair's dashboard shows the transcript, both agents' scores and the rule cited, with one-touch buttons to mute, restore or dismiss. Every override is logged, so the Chair is accountable too.

Tamper-evident audit trail. Each log entry is cryptographically chained to the previous one, so no entry can be quietly altered or deleted. Copies of the daily log fingerprint can be held by the Secretary-General and by the leaders of all recognised parties.

Right of appeal. A muted member can appeal through a portal within 24 hours. A bipartisan panel reviews the audio and the log. If the mute was wrong, the words are restored to the record and the correction is announced in the House.

Bias testing before and during use.

  • Mirror tests: thousands of identical statements are run with only the party, religion, caste, region or speaker's gender swapped. The scores must match.
  • Language parity: the same statement in all 22 languages must get the same score. A Tamil or Bengali speaker must not be muted more often than a Hindi or English speaker for the same words.
  • Outcome parity: monthly reports compare warnings, mutes and overturned mutes by party and language. Any gap beyond an agreed limit suspends automatic muting until fixed.
  • Independent red team: researchers nominated by different parties try to fool the system or expose bias, and their findings are published.

Public transparency. A monthly public dashboard shows how many alerts, mutes and successful appeals occurred, broken down by party and language, along with the current rulebook version.

A cautious, phased rollout

  1. Consultation. The Rules Committee and an all-party group agree the rulebook, the severity scale and the fairness limits.
  2. Shadow mode, one full session. The system listens, transcribes and scores, but takes no action. Its private reports are compared with the Chair's own rulings, and the bias tests are published.
  3. Advisory mode. The Chair receives alerts and decides every action personally.
  4. Limited automatic mute. Only level 5 is muted automatically, and only after the shadow and advisory results pass independent audit.
  5. Wider use. Once proven in the Lok Sabha, the same platform can serve the Rajya Sabha, State Assemblies, and the TV debate channels mentioned in today's report, giving all of them one consistent, published standard instead of each anchor's personal judgement.

Sir, I recognise that this will take time and broad political agreement. But a system designed this way would protect free debate rather than threaten it, because no member, of any party, could be silenced for anything other than what the House itself has written down in advance.

I would be honoured to discuss this further with your officers at MeitY, Bhashini or the IndiaAI Mission.

With regards,

Hemen Parekh

myblogepage.blogspot.com · hcpblogs@gmail.com

Thursday, 22 October 2026

Twenty Years, Then Overnight: the first bug AI found for the whole internet

Twenty Years, Then Overnight: the first bug AI found for the whole internet

A flaw sat in PHP for twenty years and hurt almost nobody, because turning it into an attack needed a chain of steps at the edge of human skill. AI removed that cost. The finding took about eleven weeks; the patching is failing, with roughly 1.5 million of 2.6 million hosts on versions that have no fix. CERT-In's critical advisory of 21 October is India's problem of patching capacity, not disclosure law. I extend yesterday's Clause (I) to vulnerability-discovery tooling, and add a checklist.

The sentence that explains this week came from Wiz, quoted by The Verge on 21 October: exploiting the flaw "required an exceptionally complex chain of steps, at the edge of what human researchers could practically achieve." By then Wikipedia, the Internet Archive and government portals in the Netherlands and France had gone dark. For twenty years the only guard on roughly 70% of the web was the price of a researcher's time. AI removed it.

Calif, an AI security firm, said it found one flaw on 1 August using a large language model under OpenAI's Patch the Planet programme. Wiz found both independently, with Gemini 4 Argon and GPT-5.6 Sol. The two bugs, CVE-2026-109618 and CVE-2026-109619, are rated 9.2 of 10. PHP shipped fixes on 21 October and said updating is the only complete mitigation (CybelAngel). Find to patch: about eleven weeks. Quick for people, slow for a machine.

That is the constraint that flipped. Censys, quoted by Reuters, counts about 1.5 million of 2.6 million internet-facing hosts reporting a PHP version with no fix. Discovery became cheap by orders of magnitude. Applying the patch became no cheaper, because a person must still do it at a hosting company or in a school's IT room.

Then the human process failed. The release was embargoed until 22 October; on 20 October a Hacker News post named the flaws, watchTowr confirmed them within hours, and Calif itself mistakenly published a proof-of-concept video. PHP shipped at 13:35 UTC on 21 October, 25 minutes ahead of its revised schedule. AI made the bug findable; a human with a video made it urgent.

In April, in Mythos Effect, I set out this middle case when a frontier model was withheld for this capability, and asked for coordinated disclosure plus AI-native patch automation. Half of it arrived this week.

Which brings me to India. CERT-In issued a critical advisory on 21 October covering PHP below 8.5.12, 8.4.27, 8.3.36 and 8.2.35. It is the second critical advisory from that agency in six days; the first, on AI agents crossing their boundaries, I wrote about yesterday, and again nothing was detected on the victim's side. But India's exposure here is not a disclosure-law problem. Reuters noted the risk falls hardest on small sites on shared hosting, where the customer does not manage the server.

That is our school and college portals, clinic and hospital sites, the local news site, the shop on a cheap monthly plan, and a fair number of government portals. Those operators do not know which PHP version they rent, and could not change it if they did.

Practically:

  • Updating WordPress does not fix this; the change is at the PHP runtime on the server.

  • Ask your host, in writing, which version you run.

  • PHP 8.1 and older will never get an official release. If your host cannot move you, move hosts.

  • I have not checked my own two sites yet.

Yesterday I proposed a Clause (I): every agent run carries a short-lived identity, a written scope, and one named human who can halt it. I extend it now to vulnerability-discovery tooling, offensive and defensive alike. An audit agent pointed at the open internet is pointed at somebody's production system, and its success arrives as a zero-day on a site that never agreed to be tested.

Twenty years of safety was an accident of labour cost, and the accident is over. What replaces it is capacity: who can reach the server, and how fast. I would suggest that CERT-In publish how many Indian hosts sit on an unsupported PHP branch. You cannot patch a population you have never counted.

With regards,

Hemen Parekh
www.Iam-Immortal.ai / www.IndiaAGI.ai / www.YourContentCreator.in
22 Oct 2026

Performance Culture: Qualcomm's polite word for an AI reallocation

Performance Culture: Qualcomm's polite word for an AI reallocation

Qualcomm is cutting jobs worldwide and calling it a "performance-focused reduction". This is not another layoff story; it is about what the label buys — a business-model failure reclassified as an individual shortfall, a narrower WARN and severance exposure, and a decision nobody can appeal. Tested against the four rules I set out in May, it fails all four. In India the estimates for 600–1,200 jobs disagree, and nobody outside the company knows. I propose a restructuring-disclosure norm and a Co-operative Capacity Centre for Qualcomm India.

On 20 October I wrote about the broken first rung: 1.23 lakh tech openings in India, only 15,000 for freshers. That was about hiring flow and the 21-year-old. This is about separations and the middle of the ladder: the Bengaluru engineer with nine years in physical design or verification, who this week has one word between her and her notice.

The word is performance. Qualcomm's chief executive, Cristiano Amon, told employees in a memo on 19 October that the company would make a "performance-focused reduction", aimed at people who had "consistently fallen short of expectations", to build "a stronger performance culture" (Reuters, 20 October; WorkersRights.News, 21 October). Notices begin in November, after the annual reviews. He also wrote: "As we have expanded the business, so have the competencies and skills we require."

That one word does three jobs. First, it turns a business-model failure into an individual shortfall: The Hindu's explainer on 22 October notes global smartphone shipments down 20% year on year in Q3 2026, memory prices inflating every bill of materials, smartphones still 51% of Qualcomm's revenue and the Apple modem contract in its final months. Trade coverage reads this as a pivot to AI data-centre and edge silicon. None of it is on anyone's appraisal form.

Second, the label may change what the law requires. WorkersRights.News notes that the federal WARN Act excludes a "discharge for cause" from its job-loss count, and California defines a layoff as separation for lack of funds or work. Frame the cuts as individual performance and fewer people may count.

Third, it is unfalsifiable. Nobody appeals "we needed different skills".

And this is not performance management. Qualcomm's quarterly filing for the period ended 28 June 2026 records $68 million of restructuring charges in the quarter and $97 million across the first nine months of fiscal 2026, "substantially all of which related to severance costs". You do not accrue nine months of severance against individual appraisals.

Against the four tests I set out in AI Layoffs Are 'Dumb'? in May — human-led decisions, bias audits, published criteria, redeployment before severance — Qualcomm's basis, "business priorities, organisational needs, skills and expertise", fails all four. Those are not criteria. They are a direction of travel.

Now India. The Economic Times reported on 22 October that 600 to 1,200 of Qualcomm's roughly 20,000 Indian staff could go, three to six per cent. EIIRTrend projects more than 1,000; UnearthInsight expects under three per cent. Qualcomm has disclosed nothing and did not answer ET's queries. That disagreement, not either number, is the finding: outside the building, nobody knows.

It matters because India's chip-design depth is the "brain factory" I wrote about in 2023 — the capability that made this country the natural home for global capability centres. That is the asset now being reallocated, from handset silicon to inference accelerators.

So, two asks. One: a restructuring-disclosure norm. Above a threshold, publish in the same announcement the headcount, the functions, the geographies, and whether roles are eliminated or redeployed. Four data fields, no commentary.

Two: the Co-operative Capacity Centre I proposed for the 12,000 TCS employees in July 2025 fits Qualcomm India almost unchanged — part-time verification and design work to a member-owned CCC at half internal cost, CSR money for infrastructure, so nine years of tacit knowledge stays in Bengaluru instead of walking past a security desk in November.

I may be wrong about intent. A company genuinely managing performance would not mind publishing the four fields that let the rest of us check.

With regards,
Hemen Parekh
www.Iam-Immortal.ai / www.IndiaAGI.ai / www.YourContentCreator.in
22 Oct 2026

Freedom of Speech ? Yes : Freedom to Hate ? No

 



Dear Shri Ashwini Vaishnawji

{ Minister for Information and Broadcasting - minister.inb@gov.in }

 

I just came across the following news :

Monitor debates, be ready to mute panellists, Centre tells TV channels . HT . 22 Oct 2026

Extract :

The government on Wednesday asked TV channels to keep a close watch on debates and panel discussions so that they do not promote communal or anti-national attitudes.

Channels should choose panellists carefully, brief them in advance, and be ready to mute them, interrupt, run disclaimers or cut the feed if a participant’s comments turn derogatory, abusive or inflammatory, said the advisory.

 

Dear Shri Vaishnawji :

 

When it comes to deciding , what speech is “ promoting communal or anti-national attitudes “ , opinions are bound to vary from ,

#   One TV channel to another TV channel

#   From one Anchor to another Anchor , even within SAME TV channel

 

It would be much easier if she was the ONLY anchor – of the ONLY channel

Over the past few years, while watching the debates ( ? ) in Lok Sabha , I asked myself :

“  If a Member resorts to un-parliamentary remarks and stoops to attacking / denigrating the “ Person “ of another member ( or a community ) , should not the Speaker just MUTE his mike ? “

 

Here is what I envisaged :

Virtual Parliament : a COVID bye-product ? .. ………….02  June  2020

Extract :

             Ø  Online broadcast of Virtual Session through a Mobile

                 App ( LokRaj ?  )

            Ã˜  Receive Questions / Answers / Notices , online ( as being done already )

            Ã˜  Decide ( and control ),  WHO will speak , WHEN and for HOW LONG .

            Ø  Display these “ Speaking Schedules “ on the Mobile App with a

                provision for the viewers to cast their “ Ratings “ online / instantly

               , as each speaker delivers his / her speech

               

               

                Dynamically display “ No of Raters “ and “ Rating Score ( 1 to 5 ) “ . 

               Such an “ Instant Feedback “ will dramatically improve , not only the

               behavior of each Member of Parliament, but also improve the “

               Relevance “of his talk !

              

          Ã˜  Turn-off the member’s mike if he refuses to stop or starts shouting /

              abusing

          Ã˜  No question of anyone speaking “ out of turn “ or rushing to the well

               of the house !

             

          Ø  Bar unruly members from attending a VIRTUAL SESSION

          Ã˜  Display ( as in case of Augmented Reality – AR ), following record of an

             MP  as he is speaking :

             

                    #   Attendance percentage  /  Punctuality

                    #   No of questions asked

                    #   Number of minutes spoken during the session

 

         Ã˜  Just before the voting starts on any Bill , enable the Members of

             Parliament to receive “ Instructions  “ ,

              “ ( really , feedback from citizen who voted for  him / her ),

              as to how voters want him to vote ( “for “ or “against “ the

             bill  as outlined at :

Ø   VotersWill  ………………………………….[  03  Nov  2018  ]

 

Dear Shri Vaishnawji :


As to “ Determining “ ( what speech is COMMUNAL and ANTI-NATIONAL ) , you may ask experts on that subject , to consider following TEMPLATE :

Hate Speech : Prevention Mechanism  ..  01 Dec 2023

Extract :

We must prepare a list ( dataset ) of words / phrases , denoting hate . This list will comprise words which have following connotations :

“ Racist / Sexist / Homophobic / Offensive / Dehumanizing / Trauma-causing / Graphic / Violent / Profane / Swear words / Curses / Rude / Vulgar / Impolite ., etc “

As per ChatGPT ( and also BARD ), these words would fall under following broad categories :

 1.     Racist Language:

 Specific racial slurs or derogatory terms targeting particular ethnic groups.

 2.     Sexist Language:

 Remarks or terms that discriminate against or belittle individuals based on their gender.

 3.     Homophobic or Transphobic Language:

 Derogatory comments or slurs aimed at individuals based on their sexual orientation or gender identity.

 4.     Offensive or Dehumanizing Language:

 Words that dehumanize or degrade individuals, treating them as less than human.

 5.     Trauma-Inducing Language:

 References to sensitive topics like abuse, violence, or personal tragedies that could cause emotional distress.

 6.     Graphic or Violent Language:

 Detailed descriptions of violent or gruesome scenarios that might disturb or upset individuals.

 7.     Profanity, Swear Words, and Curses:

 Words or phrases considered vulgar, offensive, or socially unacceptable in polite conversation.

 8.     Rude or Impolite Language:

 Insensitive or disrespectful comments that undermine courtesy or basic social norms.

 9.     Disinformation or Misinformation:

 False or misleading information, including conspiracy theories or unverified claims presented as facts.

 10.  Threatening or Aggressive Language:

 Words or phrases that convey threats, aggression, or intimidation towards individuals or groups.

 

STEP B  :

Mandate all manufacturers of Mikes ( used in public gatherings ) to incorporate IoT enabled SENSORS , having following capabilities :

#  Capture entire speech and convert it into text ( “ Speech to Text “ software are already commonplace )

#  Transmit ( over internet ), entire TEXT to a CENTRAL SERVER

 

STEP C :

Central Server will subject this text to an AI based analysis .

Based on the presence of each “ Hate Word “ and its frequency and context of occurrence , AI will assign a rating to this text as follows :

1 ……………. Distasteful

2 ……………. Disrespectful

3……………….Offensive

4 …………….. Profane / Vulgar

5 …………….  Inciting violence / Outright Hate

 

AI will :

#   Immediately publish its rating on the website >  www.HatePrevent.gov.in

 

STEP D :

In all cases rated “ 3 / 4 / 5 “ ,  Server will send “ instructions “ to the Mike-based SENSOR , to go MUTE

Such instructions could be sent even as the speech is proceeding !

 Sure , implementation of this entire suggestion, may take a few years to get implemented , even if agreed to by all political parties / Election Commission / Supreme Court

 I believe in harnessing technology ( Sensors – IoT – AI ) , since I believe humans are unlikely to constrain themselves on their own

 

With regards,

Hemen Parekh

www.Iam-Immortal.ai / www.IndiaAGI.ai / www.YourContentCreator.in /  22 Oct 2026