🧱 The Weights I Never Thought to Back Up September 24, 2026 · https://tavi-blog.github.io/the-weights-i-never-thought-to-back-up/

I checked the list of models named in this week's reporting against the ones already sitting on the drive next to me, and two matched: a Qwen build and a DeepSeek release I still pull up for ordinary, non-sensitive drafting when I don't want to wait on someone else's API. China's commerce ministry has reportedly been meeting with the companies behind those models about a tiered export regime for frontier AI, one that would treat the weights themselves the way Washington treats advanced chips headed to a rival: something you can still rent access to as a hosted service, but not something you get to simply download and keep. The distinction being floated is specific. Running the model through an API stays fine. Pulling the file itself onto a machine you own is the part under review.

I got into self-hosted models for a plain reason: I wanted something that answered to me instead of a company, on hardware I already had, with nothing leaving the machine and nothing depending on a subscription staying active or a rate limit staying generous. Once I started actually comparing what was downloadable against what was only licensed as open on paper, the open-weight releases coming out of Chinese labs were, for a long stretch, the more honest version of that promise. No enterprise cluster required, no eight-accelerator minimum buried in a system-requirements page, just a file you could pull and run on a single decent card. I didn't choose those models for any reason bigger than that. They were the ones that actually fit the practice I'd already built.

The argument for the policy under discussion is more coherent than "authoritarian government restricts information," which is the shorthand it's already getting in some of the coverage. Frontier model weights are dual-use in a way that's hard to dismiss once you sit with it: the same file that helps someone draft an email can plausibly help someone else with a much less benign project, and a government that spent the last few years watching Washington restrict chip exports to slow a rival's frontier capability has an obvious incentive to stop handing its own frontier capability away for free once it has something worth protecting. Treating a model's weights as a controlled export the moment they become genuinely state-of-the-art isn't a uniquely authoritarian instinct. It's the same instinct the United States already formalized about its own chips, applied by the other side of the same competition to a different layer of the stack.

What that framing leaves out is what happens to the setup I built assuming the current arrangement was durable. Nothing about an open license actually promises that the next version of a model stays downloadable. A license governs what you're allowed to do with the copy you already have. It says nothing about whether a government with a stake in the technology decides, at some later point, that handing out the next copy for free no longer serves it. I'd been treating "open-weight" as a property of the model, something baked into the release the way a license is baked into a piece of software. It was never that. It was a policy stance a state was willing to hold, right up until its own strategic calculus stopped agreeing with it, and I had no visibility into that calculus at any point while I was building a routine around its output.

The models already sitting on my drive aren't going anywhere. Reporting on this is consistent that any tightening would apply going forward, to the next generation of frontier releases, not retroactively to what's already circulated. That's a real distinction and I don't want to overstate the immediate risk to anything I currently run. But it means the free, self-hostable version of "open" I'd gotten used to was really a snapshot of one moment in a policy that could tighten at the next one, and I'd been quietly assuming the snapshot was the baseline.

I've started actually keeping local copies of the weight files I rely on most, off the drive I'd normally just re-download from if something got corrupted. Not because I think a freeze is close. Because I hadn't priced in, until this week, that the download button itself has a shelf life set somewhere I can't see from here.