491 people lost their job
to AI today.
What are you going to do about it?
The numbers are already here and they are not slowing down. This is not a think-piece about the future. This is about right now — what AI is replacing, how fast it is moving, and the only real answer that exists. Waiting is not one of them.
Search "I lost my job to AI" on YouTube. Watch what comes up. Not think-pieces. Not economists. People — real people — sitting in front of their cameras, trying to explain to anyone who will listen what happened to their livelihood. The view counts are not small. The comments are worse.
This is not a future problem. It is a present one and it is accelerating in a way that the headlines have not fully caught up to.
(cite index="27-1">In 2024, layoffs and freezes from a group of seven international companies led to approximately 18,000 AI-related job losses. That number increased by at least 5x in 2025, resulting in over 100,000 layoffs due to AI. In the first seven months of 2026, more than 165,000 roles have already been cut.
(cite index="30-1">In 2025, 342 tracked tech company layoffs eliminated 77,999 positions — roughly 491 people losing jobs every single day in that sector alone. Every single day. Before you finish reading this article, more people will have joined that number.
(cite index="26-1">In March 2026, AI became the number one most-cited reason for workforce reductions for the first time ever, accounting for 25% of total cuts that month. Not cost-cutting. Not restructuring. Not a pivot. AI. Named directly, on record, as the reason.
What is actually being replaced — and how
// Chapter 01 — This is not hypotheticalThe conversation about AI and jobs tends to happen in the abstract. It should not. The specific roles being displaced right now are not edge cases — they are the backbone of how most businesses operate.
Governments are talking. Nobody is acting.
// Chapter 02 — The institutional failureEvery government in the world is aware of this. The IMF has published reports. The WEF has published reports. National AI strategies exist from the EU to South Africa. Committees have been formed. Frameworks have been discussed.
Meanwhile, (cite index="26-1">40% of employers are planning to reduce their workforce where AI automates tasks in 2026. They are not waiting for government frameworks. They are not waiting for retraining programmes. They are not waiting for anything.
(cite index="25-1">Companies attributed 55,000 job cuts directly to AI in 2025 — a 12x increase from 2023. The irony is not lost on job seekers: the same technology they fear will take their job is already making it harder for them to find a new one. AI-powered applicant tracking systems filter out resumes before a human ever sees them.
The speed of corporate AI adoption and the speed of government response are not in the same conversation. They are not even in the same timezone. Businesses are adopting AI at the pace of competitive advantage. Governments are responding at the pace of policy consultation. By the time the consultation is published, the jobs it was meant to protect no longer exist.
The cars and the horses
// Chapter 03 — This has happened beforeWhen the automobile arrived, it did not ask permission. It did not publish a consultation paper. It did not phase in gradually to allow the horse and carriage industry to adapt. It arrived, it was useful, and the horse and carriage industry was over.
The people who worked in that industry — the drivers, the stable hands, the harness makers, the farriers — they did not disappear. The economy did not collapse. But the people who survived the transition were not the ones who waited for someone to save their previous role. They were the people who found what the car needed that the horse did not — mechanics, fuel stations, roads, insurance, logistics.
AI is the car. The jobs it is replacing are the horses. The question is not whether this is happening. The question is whether you are building the thing AI needs — or waiting for someone to bring the horses back.
A minute you can never get back
// Chapter 04 — NetworkChuck said it bestI did not ask permission to start task-bridge. I did not ask permission to start TripSpace Global. They are not finished. They are not perfect. But they exist — and they exist because I started them instead of waiting until everything was ready.
Nothing is ever ready. The window is always smaller than you think. The technology is moving faster than you are planning for. The people who are going to be okay on the other side of this shift are not the ones who had the best plan. They are the ones who started something.
You do not need to build a protocol or a marketplace. You need to find one thing AI cannot do as well as a human who gives a damn — and do that thing better than anyone else. There is still a very long list of things on that list. The list is getting shorter every year. Start now.
What task-bridge actually is — and why it matters here
// Chapter 05 — The only answer worth buildingtask-bridge is an open protocol — early, imperfect, still being built — for routing AI-displaced work back to humans. The premise is simple: AI systems generate tasks that require human judgment, validation, creativity, or presence. Instead of those tasks disappearing into the AI, they get routed to a human who can do them. The human gets paid. The AI gets better data. The gap between "AI does everything" and "humans do nothing" gets a structure.
It is not a job board. It is not a gig economy platform. It is a protocol — the same way HTTP is a protocol. Anyone can build on top of it. Any AI system can emit signals into it. Any human with the right skills can respond to those signals and earn from them.
(cite index="25-1">The World Economic Forum projects AI will create a net 78 million new jobs by 2030. That projection requires infrastructure. It requires a layer between the AI economy and the human workforce. task-bridge is one attempt at building that layer. It needs more people building on it. It needs more AI companies contributing to it. It needs governments to take the protocol-layer approach seriously rather than building centralised job boards that will be obsolete before they launch.
If you are a developer and this resonates — the GitHub is open. If you are an AI company and you are genuinely thinking about what happens to the people your products displace — the protocol is there and the conversation is open.
Do something AI cannot
// Chapter 06 — The only strategy that worksMake AI your tool, not your replacement. Use it to build something. Use it to learn something. Use it to move faster than you could without it. That is what I am doing. It is what every person in this article who will be okay is doing.
The businesses that survive this are not the ones that avoided AI. They are the ones that adopted it early, moved fast, and used the efficiency to do things they could not afford to do before. The individuals who survive it are not the ones who had roles that AI could not touch. They are the ones who developed skills AI cannot replicate — judgment, relationships, creativity, accountability, showing up — and combined those with AI's ability to scale.
Do something meaningful that people need. Not something that requires a job posting and an office. Something real. Something you could start this week. Something that solves a problem for someone who will pay you for solving it.
I did not ask anyone's permission. I started in the South African night with a laptop and a frustration that the tools were impressive but not useful. That frustration became a book, became a protocol, became a business, became a security research programme, became this article.
The gap between where you are and where you want to be is not a skills gap or a funding gap. It is a starting gap. Close it. The minute you are waiting for is already gone.
// task-bridge — the open protocol
AI is generating work. Humans should be doing it.
task-bridge is an open protocol for routing AI-displaced tasks back to humans. Early, open source, MIT licence. If you are a developer, an AI company, or a government thinking seriously about this problem — the GitHub is open.