For six months I was certain about the direction.
Editorial update, October 11, 2026: This is the strategy turn published June 15, 2026. Its August launch, institutional/legal system and French-specialization commitments are historical roadmap statements, not a report that each shipped. The July 12 decision and the July postmortem document the later hosted-model changes and what the author reported actually releasing. The August delegation reflection adds later limits. No missing release or evaluation record is implied by those links.
Seven days ago that broke.
The idea was clean.
Canadian institutions need AI they can trust, so build them a Canadian model: train it on Canadian law, regulation, finance, and government records.
Run it on Canadian servers.
Make it open, so anyone could check our work.
Teach it to operate in both English and French, the way this country actually does.
Ship a small family of models, and release the research we built along the way.
I thought I'd be writing about that all summer.
The idea wasn't wrong.
The way I was building it was.
I had confused the model with the system.
The category error
Here's the mistake in plain terms.
I thought "Canadian AI" meant a model that has memorized Canada - every law, rule, and convention learned in advance and stored in its head.
So the plan was to teach it all of that up front, like a student cramming for a closed-book exam.
What people actually need is closer to an open-book exam.
A capable, well-trained mind - plus a current, trustworthy library it can pull from at the moment a question is asked.
Those are two different things.
One is the model. The other is the system around it.
I had been pouring all my effort into the first, when the second was where the value lived.
The model is the reasoning - the part that reads a rule it has never seen and applies it correctly.
The library (in the trade we call it retrieval) holds the live, citable Canadian sources and hands the model the right pages when a question comes in.
And we let it use real tools, so it can check authoritative systems directly instead of recalling a frozen, months-old impression of them.
Here's what a week of staring at this taught me.
My bet was that institutions would value current sources more than a model claiming to have memorized them.
That pointed me toward a capable model, a source library and tools to verify information.
I wanted the Canadian context to be current and sourced at the moment of the answer. Retrieval still needs verification.
For institutional work, I preferred the open-book architecture. That preference is not evidence that it wins every task or is ready for regulated use.
It stays current.
Rules and guidance change. OSFI's E-23 model-risk guideline, for federally regulated financial institutions, has a May 1, 2027 effective date; it is not a universal rule for every Canadian AI deployment.
Editorial update, October 11, 2026: Primary regulator record: OSFI E-23. The guideline sets model-risk expectations; it does not certify this system or require a particular model architecture.
A memorized model is out of date the day a rule changes and doesn't know it.
A library you can update overnight.
It shows its work.
A bank, a hospital, or a government department doesn't want a confident-sounding paragraph.
They want the answer and the exact source it came from.
A retrieval system can provide citations, but they still need to be checked for accuracy, relevance and whether they support the answer.
A model answering from memory just asks you to trust it - which is the one thing these buyers will never do.
It keeps the model smart.
Cramming a powerful general model full of one country's fine print doesn't make it more Canadian.
It can change capabilities in ways we need to measure. I cannot assume that specializing a model always makes its reasoning worse.
A library can make source updates easier, but maintaining it, retrieving the right passage and checking the answer still cost work.
Why this is the bigger bet, not the smaller one
If the "Canadian" part lives in the library and not the model, then the same system serves any country.
Point it at Canadian sources, it serves Canadians.
Point it at Brazilian or German or Kenyan sources, it serves them.
The thing I'd framed as a Canadian moat was really a general capability with a Canadian configuration.
That matters more to us than it would to most companies, because of how we're built.
We're bootstrapped.
No venture capital, no runway funded by someone else's fund, no permission to spend two years on a beautiful thing that serves exactly one mid-sized market.
Revenue is oxygen - and a from-scratch Canadian model capped our market at a single country.
A model-plus-library architecture gives us other markets to explore; it does not remove language, legal, product or distribution limits.
The same architecture could be explored elsewhere. Each language, legal system and customer need would still require its own work.
For a company that has to pay for itself, "the approach that also opens the rest of the world" isn't a nice-to-have.
It's the difference between a project and a business.
It also makes the work easier - which I should have weighted far more heavily than I did.
Standing on a strong open model means I inherit a frontier-grade mind and spend my effort on the parts that are actually ours: the quality of the library, the tools, the way we prove the answers are right.
Building the mind myself meant owning the hardest, most expensive part of the whole stack - to get a result the open world was about to hand me for free.
Less to build. More capable. A bigger market.
I was choosing the opposite of all three.
The tradeoff, said plainly
Every real decision costs something, and I want to name this one honestly.
Focusing on the best possible general model means the dedicated French and Quebec work has to wait.
Building a model that nails Quebec's legal-French conventions as a specialty was on the near-term list.
For now, it's deprioritized.
I don't love writing that.
French is something I care about personally, and I'm not letting it go.
Here was my reasoning, rather than a measured French-language result.
I wanted a capable general model that also handled French well. Character tuning and general capability do not establish that outcome on every task or language.
French was part of that goal.
Neither general training nor French specialization guarantees the register or legal accuracy a particular task requires.
We would still need task-specific results to know.
So French doesn't disappear from the plan.
It arrives a different way: a fluent, capable model, plus the actual French-language sources in the library it reads from.
The polished Quebec legal register comes later.
General French capability still needs evaluation on the tasks and register we claim to support. It is not free or guaranteed just because we think the model is built correctly.
What's preserved - and now belongs to everyone
Two things I built for the old plan don't just survive the pivot.
They matter more now, and they're going out to the world.
The Canadian Bilingual Legal Corpus and CBLRE - our way of measuring legal-AI quality - were going to be training fuel.
Used once, melted into the model, invisible afterward.
Under the new approach, a body of legal text and an honest way to score legal-AI answers are exactly the open-book library and the report card.
They're load-bearing, not leftovers.
We are publishing public methodology and a harness. Access to particular corpus, bank and held-out data has its own terms; public methods do not mean every dataset is openly downloadable.
A legal corpus that spans two languages and two legal traditions, and a straight way to measure how well an AI actually handles legal questions.
These are among our first gifts to the community.
Researchers can inspect the public methods and follow the documented access terms. That is different from independently reproducing the reported results with every underlying dataset.
That contribution is worth far more to the world as an open gift than it ever would have been buried inside one company's model.
The bet
What we're launching on August 8 is one thing, not a lineup with two years of promises attached.
Editorial update, October 11, 2026: The August 8 launch and public-verification bundle below were the plan described in this June essay. A release receipt for that exact promised institutional/legal system is unavailable here. The public CBLRE-method/gated-data distinction is documented in the updated evaluation account; this was an early method proposal, not an adopted compliance standard.
It's called vinci-studio: a strong open model, a Canadian library it reads from, the ability to use real tools, a bit of character tuning, and a public bundle anyone can use to confirm it does what we claim.
The rest is roadmap, not promise.
I'd rather under-promise the lineup and over-deliver on the one thing than the reverse.
It's a smaller launch than I first announced.
It's a more honest one, it's built the right way, and - for a company that has to fund itself - it's the version that can actually pay for itself.
The lesson
Two of them, and the second is the one I actually needed.
The easy one: hold your thesis as a question, not an answer.
"A Canadian model" was my answer.
The real question - what gives serious institutions AI they can trust and verify? - kept evolving while I defended the answer I'd already announced.
From now on I write the question down at every big decision, separate from whatever answer I'm working with.
When the answer shifts under me, the question is still there to steer by.
The hard one: don't make the machine memorize what it could simply look up.
The most powerful-sounding option is rarely the right one.
I spent two weeks longer than I should have on the harder, more expensive path because changing course in public felt costly.
It is costly - but that cost is paid once, up front.
The cost of building the wrong thing is hidden, and it grows every day you keep going.
I'm choosing the upfront cost over the hidden one from here on.
What I'm watching
The ground is moving fast.
Open models get better every month.
The rules keep shifting.
The research I'm trying to keep up with ships faster than I can read it.
My job is to keep listening, and to change course early and out loud rather than late and quietly.
The pattern I most want to catch next time it forms: mistaking the thing I announced for the thing I was actually trying to do.
The June plan named August 8 as the launch date.
That's what I'm building now - seven days into the turn, writing from inside it instead of after.
We'll see in six weeks how it lands.