The enterprise window is open. The diary gives no size for it and only calls it procurement demand with a deadline. Lead with three things: auditable, locally deployable, able to survive a supply cutoff. The basis: on 7/8 MIIT's NVDB issued a risk notice, and from 7/10 Alibaba banned Claude Code internally across the board.
The mainstream story treats decoupling as the result of government bans. The diary holds that this round started from one large company's procurement list: the MIIT notice is a posture, while Alibaba's blacklist is a real-money procurement decision. The risk sits in procurement decisions and has nothing to do with technical quality.
In late June developers reverse-engineered a detection mechanism built into Claude Code that checked time zone and proxy to identify China-related users; the company said it was an "experimental" measure launched in March and removed on 7/2. On 7/8 MIIT's NVDB issued a risk notice calling it a "security backdoor, serious harm". From 7/10 Alibaba banned it internally across the board and put it on its high-risk software list. Sources are ITHome, Zhidx and Guancha; whether the mechanism is a "backdoor" in the technical sense is disputed, and the diary draws no technical conclusion.
For founders: put "auditable, locally deployable, able to survive a supply cutoff" as the three lines on your product homepage and go after large companies' replacement budgets now. For investors: add "supplier nationality and cutoff contingency plan" to diligence on China developer tools, and mark down Chinese targets whose revenue depends heavily on US model APIs.