A sovereign AI initiative. Quietly held together.
An active, defence-adjacent project at a Canadian sovereign AI and cybersecurity firm. A deployable, off-grid AI intelligence unit, built for environments where conventional cloud infrastructure cannot reach and data sovereignty is non-negotiable. My contribution is coordination and communication across an internal technical team, defence-sector partner, and a formal Canadian innovation program.
A deployable AI unit for environments where the cloud cannot reach.
The product under development is a deployable, off-grid AI intelligence unit. Designed to operate in environments where conventional cloud infrastructure cannot reach and where data sovereignty is non-negotiable. Think remote and austere operating environments, contested locations, critical infrastructure at the edge. The kind of contexts where standard assumptions about connectivity, power, and cloud access do not hold.
The project is in early prototyping. The firm's in-house security platform is integrated as a native layer given the sensitivity of the environments this product is built for. The partner ecosystem includes a government-aligned defence organization and a formal Canadian innovation body .
Further detail is withheld given the confidential nature of the initiative.
Coordination and communication. Not engineering.
This is a multi-party initiative. An internal technical team. External defence-sector partners. A formal innovation program. Each operates with different context, different vocabulary, and different definitions of what progress looks like. My job is the connective tissue.
Day to day
- Facilitate standups and maintain alignment across internal teams
- Translate between technical and non-technical stakeholders
- Track what is decided versus what is still open
- Own the written artifacts that represent the project externally
Where I've spent the most time
The written artifacts. I produced the initial product sheets used to bring partners to the table; translating early-stage thinking into documents that could represent the concept credibly to organizations evaluating whether to commit.
Detailed whitepapers followed, developed in close collaboration with the technical team. Currently under review as the product evolves.
Early-stage, multi-party technical projects fail in predictable ways.
- Ambiguity compounds
- Partners interpret the same conversation differently
- The technical team builds toward one target while business and partners work from a different picture
- Documentation lags behind decisions
- Nobody owns the connective tissue
What gets communicated externally has to be accurate. Commitments made to partners have to reflect what the team can actually deliver. The written artifacts have to hold up to scrutiny from organizations that take this domain seriously.
My job is to stay close enough to the technical work to translate it accurately, while keeping the broader initiative moving. Clearing blockers, maintaining momentum, making sure the right people have the right information at the right time.
Five capabilities, exercised in a high-stakes environment.
Want the longer version? Let's talk.
Most of what makes this work meaningful sits in the part I can't put on a public page. Happy to walk through the rest under the right circumstances.