When two countries fall out, the first thing to go quiet is the official channel. The delegations pause. Meetings disappear from calendars. Businesses become careful, institutions wait for signals, and the photographs of handshakes disappear from the news.
For a while, waiting feels sensible.
I watched this happen between Canada and India. But I also watched something that received far less attention. Underneath the political rupture, much of the relationship kept moving.
Companies were still looking for partners. Researchers were still interested in each other's work. Industry still needed technology, capital still looked for opportunity, and families continued moving between both countries.
The politics had changed. The underlying need had not.
For those of us working inside the corridor, that left a choice. We could wait for governments to repair the relationship, or we could keep building the relationships that would be needed when they did.
We kept building. Not because government did not matter. It mattered enormously. We kept building because I had started to understand something about trust.
It is not sentiment. It is infrastructure.
What survives
We tend to imagine international relationships from the top down. Two leaders meet, an agreement is signed, a delegation travels, and a photograph tells us the relationship is moving again.
But underneath that photograph is an enormous amount of machinery. Someone has to understand the regulator, find the research partner, structure the pilot, move the technology, train the people, make the payment, solve the misunderstanding, and answer the phone when something goes wrong.
That part rarely makes the photograph. It is also the part that decides whether the relationship actually works.
I had an unusual vantage point on this: institutional conversations about what the relationship between Canada and India could become, while at the same time working on the ground across technology, research, industry, workforce development, and public-sector problems. Somewhere between those worlds, I began to see the same thing repeatedly. The introduction was rarely the difficult part. What happened after it was.
In practice, that meant moving across more of the system than I had expected: from government and research conversations into commercialization, local implementation, incentives, industry partnerships, and deployment. Sometimes our role was not to introduce two institutions, but to remain between them long enough for the introduction to become something operational. That was where I began to understand the difference between access and infrastructure.
Governments create the conditions for cooperation. They negotiate agreements, establish regulation, protect national interests, and open doors that private actors sometimes cannot open themselves. But underneath that architecture, someone still has to deliver. A company that ships. A researcher who collaborates. A pilot that works. A partner who keeps their word.
That is what trust looks like when it becomes real.
The infrastructure we do not count
There is another reason the relationship between Canada and India proved more resilient than it appeared from the outside: people.
Canada has a large Indian diaspora, a fact we usually describe culturally or demographically. Working between the two countries made me see it differently. A diaspora is also a network of memory.
These are people who understand both systems. They know where a word means something slightly different, where expectations diverge, how business is actually conducted, which institution to call, and sometimes simply whom to trust. They carry relationships, technical knowledge, institutional memory, and commercial understanding between countries. And those relationships do not reset when governments do.
A diaspora is not a replacement for diplomacy. But it creates continuity underneath it.
That matters, because an international relationship is not really one relationship. It is several systems operating at once: government, research, commerce, education, capital, technology, and people. A rupture in one does not automatically erase the others. Sometimes those other systems are precisely what keep the relationship alive.
The distance between the idea and the outcome
Working through the rupture exposed another problem. We spend a great deal of energy celebrating the beginning of innovation, the breakthrough, the patent, the laboratory, the startup. And we celebrate the end, the investment, the factory, the deployment, the announcement.
But there is a long distance between invention and impact.
A technology developed in one country rarely arrives in another ready to work. Someone has to ask whether the problem is even the same. The technology may need to be validated, localized, regulated, financed, and integrated. People have to be trained. Procurement has to make sense. Industry has to see enough value to adopt it. And when something goes wrong, somebody has to stay long enough to fix it.
This is where I have watched many good ideas get stuck. Not because the technology was poor, but because the infrastructure around the technology was incomplete.
That realization shapes much of what we are building now. I am less interested in technology for its own sake than in what becomes possible when capability actually reaches the problem. Cleaner air. Earlier diagnosis. A farmer earning more from the same land. A teacher preparing a student for work that does not exist yet. An industry becoming more productive without leaving its people behind.
The corridor matters only if what moves through it eventually improves something real.
Trust has memory
There is one more flaw in the way international relationships are built. We constantly restart them.
Governments change. Ministers change. Diplomats rotate, executives leave, programs are renamed, and another delegation arrives to begin the introductions again.
But trust needs memory. Someone has to remember what was attempted, what worked, what failed, which institution delivered, which promise became an outcome, and who stayed when things became difficult. Otherwise every political cycle begins again at the introduction.
Universities, companies, research institutions, communities, and long-term operators can carry that memory across cycles. And over time, something useful happens. Trust compounds. One piece of successful work makes the second conversation easier. One institution that delivers makes another more willing to participate. One relationship that survives difficulty becomes evidence for the next.
That has real economic value. It reduces friction. It shortens the distance between an introduction and a decision. It lets people attempt more complicated things together. And when enough of those relationships exist, the corridor becomes more resilient than any single political cycle.
What the rupture revealed
Eventually, the official relationship between Canada and India began moving again. That matters. Diplomacy is not ceremonial, and governments carry responsibilities that private actors cannot and should not replace: national security, regulation, democratic accountability, the protection of the public interest.
But something had happened while the formal relationship was strained. The infrastructure underneath it had become visible: companies and researchers, universities and industry, capital, diaspora, families and people who had continued carrying pieces of the relationship. Some parts had weakened. Others had continued.
And that changed how I think about measuring the strength of a relationship between countries. Perhaps we should not look only at what happens when everything is working. Perhaps the better test is what remains when something breaks.
After the rupture
The more interesting lesson is what a rupture reveals. When something breaks, we are forced to see the structure underneath it. We learn which relationships were transactional and which were durable, which institutions depended on the official channel and which had earned enough trust to continue, where the weaknesses were, and where strength had quietly accumulated.
That knowledge gives us a choice. Canada and India do not have to rebuild exactly what existed before. We can build something stronger: a relationship with more than one layer of trust. Government to government. Institution to institution. Researcher to researcher. Company to company. Person to person. A relationship resilient enough that the next disagreement does not force every other part of the system to stop.
That is a real opportunity hidden inside a difficult period, and it matters well beyond these two countries. The world is becoming more selective about how it connects. Supply chains are being reconsidered. Technological dependencies are being examined more closely. Artificial intelligence, semiconductors, critical minerals, energy, and biotechnology are becoming questions of sovereignty as much as commerce. We are going to need trust across borders at exactly the moment it is becoming more difficult to assume. Which means we had better understand how it is actually built.
The rupture between Canada and India taught me something simple. A treaty can open a corridor. Only trust keeps it open, carried by the people and institutions that still know how to cross it when the treaty is not enough.
That is trust. And trust is infrastructure.
But once you can see that infrastructure clearly, a harder question appears. Do we repair the bridge exactly as it was? Or do we understand what held, learn from what failed, and build the next one stronger?
That is where Part II begins.