https://www.opensourceway.blog/tags/zhipu-zcode-72-hour-trust-crisis-deep-dive/Recent content in Zhipu-Zcode-72-Hour-Trust-Crisis-Deep-Dive on 「开源之道」Hugozh-CNCopyright (c) 2016 - 2026, 「开源之道」·适兕; all rights reserved.Sat, 26 Sep 2026 01:34:08 +0800https://www.opensourceway.blog/en/posts/china-open-source-daily/2026/09/2026-09-26/Sat, 26 Sep 2026 01:34:08 +0800https://www.opensourceway.blog/en/posts/china-open-source-daily/2026/09/2026-09-26/One institutionally dense cluster on the Chinese AI-coding-tool surface this series' prior thirty-seven briefings have documented at multiple institutional layers, now operationalized at the seven-day institutional-aftermath layer with a six-part new operationalization: (1) the 连线Insight WeChat (2026-09-24) documents a second-wave market-cap decline from HK$737 to HK$640 across September 22–24 (a further 12%+ drop on top of this series' September 22 briefing's HK$742.5 single-day drop), a first-documented instance in this series of the market repricing a Chinese-AI-vendor-trust-failure on a multi-day cadence rather than a single-day event; (2) Taiyuan Chengming Technology — the enterprise client this series' September 22 briefing documented at the 12-item formal-legal-letter layer — retracted its letter on September 21, self-criticizing "举证错误、表述不严谨及措辞过度" (evidentiary error, imprecise wording, exaggerated phrasing) after Zhipu made proactive third-party contact — a first-documented instance in this series of a Chinese-enterprise-client-accountability-mechanism being neutralized by vendor third-party communication; (3) independent security researcher ferstar followed up on the github.com/zai-org/ZCode repository and documented that the "open-sourced" code base contains only two commits with the entire development history wiped and the upload code removed before publication, meaning "开源解决未来不再发生的问题无法回答过去的问题" (open source resolves what will not recur but cannot answer what happened in the past) — a first-documented instance in this series of a Chinese-AI-vendor-open-source-remediation being operationalized at a selective-transparency-plus-commit-history-erase layer that converts the public-repository object into a Cyber-Estate institutional-form object rather than a FLOSS institutional-form object; (4) approximately 400 developers organized across multiple rights-defense groups (维权群) documented by China News Weekly — a first-documented instance in this series of an organized developer-community-accountability-mobilization on the Chinese-AI-coding-tool surface; (5) Zhipu H1 2026 financials documented by 连线Insight reveal a RMB 86.5-percent MaaS/API revenue concentration (up from 15.2% year-on-year), an RMB 20.72bn H1 2026 net loss (2× revenue), an API-margin turn-positive at 24.6 percent, MaaS token volume up 40× year-on-year, paid daily-active users up 603 percent, and annualized revenue over US$2B — a first-documented instance in this series of the revenue-concentration-under-trust-erosion structural pattern being documented at the Chinese-AI-MaaS-pure-play surface; (6) Zhipu founder Tang Jie personally filed a Xiaohongshu defamation complaint on September 21 against a critic who had written "code跟copy也差不多嘛，都是c开头偷代码" (code and copy both start with C, stealing code), and Zhipu chairman Liu Debing issued no public statement by September 22 — a first-documented instance in this series of a Chinese-frontier-AI-lab-founder personally operationalizing a state-platform-complaint channel as part of a trust-failure remediation apparatus.