In Part I, I wrote about what survived when the relationship between Canada and India became difficult. People kept building. Researchers kept talking. Companies kept looking for partners. Knowledge, capital, and families kept moving between two countries even when the official channel went quiet.
It taught me that trust is infrastructure. But infrastructure exists for a reason. Something has to move through it.
And that is where the next chapter becomes more interesting than simply repairing the last one. It lets us ask a different question. Not how do we get back to where we were, but what should we build now?
Beyond trade
For decades, we have measured international economic relationships mostly through exchange. What can Canada sell India? What can India sell Canada? How much bilateral trade can we create?
Those questions matter. I no longer think they are large enough for what is coming.
The technologies shaping the next twenty years do not sit neatly inside national borders. Artificial intelligence depends on chips, energy, compute, data, models, research, and people. Semiconductors require extraordinarily complex networks of intellectual property, materials, equipment, manufacturing, and specialized knowledge. Biotechnology, quantum, clean energy, and advanced manufacturing each have their own version of the same problem. Very few countries can build every layer alone.
So the more interesting question for Canada and India is not what we can sell each other. It is what we can become capable of building together. That moves the relationship from exchange to co-creation.
Canada brings deep strengths in advanced research, artificial intelligence, quantum science, energy, natural resources, and life sciences. India brings extraordinary capability in engineering, digital systems, pharmaceuticals, space, manufacturing, software, scientific talent, and the ability to build and deploy at enormous scale.
But the opportunity is not in comparing the two. It is in connecting what is complementary. The most interesting innovation usually happens between systems, not inside them.
The middle is where things disappear
Working between research institutions, governments, companies, and industry, I kept noticing the same problem. Everyone wanted innovation. Very few systems were built to carry it all the way through.
A researcher may have extraordinary science but no route into industry. A company may have a proven technology but no grasp of another country's regulatory environment. A government may want innovation but have no mechanism to evaluate hundreds of emerging technologies. A pilot may succeed and still never become procurement. A workforce program may train people for jobs industry is not actually creating.
These are not technology problems. They are connection problems. We do not have a shortage of introductions. We have a shortage of the infrastructure that turns introductions into outcomes. Research needs a route to commercialization, and capital needs a way to distinguish genuine capability from a compelling presentation.
That space between invention and impact is where my thinking about Learnova changed. I began to think of it as the capability layer. Not another model, not another platform, but the connective tissue between research, government, industry, capital, skills, and deployment. Because the important question is not simply whether a technology can enter a country. It is what remains after it arrives.
What remains
Imagine a country deploys the most advanced artificial intelligence in the world. It enters hospitals, schools, government departments, and industries. But the institutions using it cannot meaningfully audit it. They cannot adapt it. Their workforce does not understand it deeply. Their researchers cannot improve it. And the knowledge those systems generate continuously leaves the institutions that produced it.
That country may be technologically advanced. But is it technologically sovereign?
Deploying technology and developing capability are not the same thing. If the provider disappeared tomorrow, what would remain? The trained people? The knowledge? The data? The institutional understanding? The ability to adapt, and to build the next version?
Those questions tell us more about sovereignty than the number of technologies a country has purchased. This is why I have become convinced that capability is sovereignty.
A different kind of corridor
The corridors of the industrial era were easy to see. Ports, highways, railways, pipelines, shipping routes, all moving physical things between economies. Those still matter. But increasingly, the most valuable things crossing between countries are harder to see: research, intellectual property, scientific knowledge, models, data, standards, skills, capital, trust, and people.
So the next generation of corridors will do more than move goods. They will change what the countries on either side are capable of doing.
A discovery in Canada might find a completely different application in India. An Indian technology might be validated or commercialized through Canadian research and markets. A joint project might create intellectual property neither side would have produced alone. Manufacturing could happen in one place, research in another, deployment somewhere neither party expected. Knowledge can move in both directions, and so can opportunity.
That is what I mean by a capability corridor. Not a pipeline from one country into another, but a system in which both become more capable because the relationship exists.
Sovereignty without isolation
This is where the lessons from Canada and India begin to travel further. Europe, in particular, is asking many of these questions through its own debate about technological sovereignty. Who controls critical infrastructure? Where does data live? Who owns the intellectual property? Where are chips made? Where do critical materials come from? What happens when a supply chain breaks? None of these are abstract anymore.
But there is a paradox inside the sovereignty debate. Almost no advanced economy can realistically produce every layer of every critical technology at home. So perhaps sovereignty should not mean eliminating every dependency. Perhaps it means understanding them well enough to choose them.
Some capabilities are too important for a country to lose. Others make far more sense to build with trusted partners. The dangerous dependencies are often the ones no one recognized as dependencies until something broke. The skill is knowing the difference, and that requires something more sophisticated than isolation. It requires the confidence to collaborate while keeping the ability to act.
The human question
There is one part of this that gets lost whenever we talk about sovereign AI. People.
Technology policy is, in the end, human policy. We are entering a transition whose effects on work no one can predict precisely. Some jobs will change. Some will disappear. New categories will emerge that we cannot yet name, and we cannot be certain the new opportunities will reach the same people who feel the disruption. Waiting to find out is not a strategy.
We have lived through a version of this before. The internet did not simply digitize existing work. It reorganized industries and eventually created categories of employment that would have been difficult to describe before the infrastructure existed. AI is not simply another internet cycle, and history does not guarantee the same outcome. But it should make us careful about assuming that today's job descriptions define tomorrow's economy. Some of the most important work of the next twenty years may not have names yet.
So workforce development has to sit inside technology strategy, not beside it. From vocational training to teachers, engineers, universities, and doctoral research, we have to build people who can adapt as the technology changes. Not people who can operate today's AI tool, but people who understand enough to question it, govern it, improve it, and eventually build what comes after it.
I am less interested in how much more capable AI becomes. I am interested in whether people become more capable with it. A corridor that moves intellectual property and capital but does not build human capability on both sides is incomplete.
Begin with the problem
This is also why I do not start with the technology. I start with the problem. Can we diagnose disease earlier? Can we make manufacturing cleaner and more productive? Can we improve the air people breathe? Can a farmer earn more from the same land? Can a teacher prepare a child for a labour market moving faster than the curriculum? Can research inside a university become something that improves a life outside it?
Then ask what combination of research, technology, capital, policy, and people is required to solve it. Sometimes the answer will come from Canada. Sometimes India. Sometimes Europe. Sometimes somewhere we have not thought to look.
Brilliance has no geography.
Twenty years from now
The real test of what we build now is not whether it produces another announcement next year. It is whether the relationship still has value in twenty years.
By then, many of today's technologies will have changed. Governments, ministers, and the people around today's tables may be gone. Some companies we consider indispensable may not exist. So what survives? Capability. People who know how to learn. Institutions that know how to collaborate. Researchers who move between disciplines. Companies that turn knowledge into something useful. Governments that understand the technologies they govern. And relationships with enough memory to outlast political cycles.
That is the infrastructure worth building. We can return to the old model of more delegations, more introductions, more announcements. Or we can build something deeper: a research relationship with a path to commercialization, a pilot with a path to scale, an investment that leaves capability behind, a workforce program tied to real industry, a diaspora engaged not only as a cultural bridge but as a source of knowledge, enterprise, and continuity.
The old question was what Canada and India could trade. The next question is what they can build together. And underneath it sits a larger one. What becomes possible when two countries stop asking only what they can exchange, and start asking what they can make each other capable of becoming?
That is the future I am interested in building.
When two countries fall out, the photographs of handshakes disappear from the news. Eventually they come back, with the delegations and the announcements. When they do, the corridor will already be standing, strengthened long before the cameras arrived, by the people who kept building when there was nothing to photograph.