Several stories this week are worth highlighting individually. While they share no single overarching theme, all four touch on the most tangible tensions across the AI industry right now: whether training data constitutes copyright infringement, whether domestic chips can support inference at scale, whether open-source agents can mature into team infrastructure, and how workers affected by AI actually feel. Each stands on its own; here is the breakdown.
The U.S. Department of Justice has taken an explicit stance in the ongoing AI copyright dispute. On September 1, it filed a Statement of Interest with the U.S. District Court for the Southern District of New York. In the consolidated OpenAI copyright litigation (In re OpenAI, MDL No. 25-md-3143, presided over by Judge Sidney H. Stein), the DOJ argued that using copyrighted works to train large language models does not constitute infringement and qualifies as transformative fair use. The proceeding encompasses The New York Times’ late-2023 lawsuit against OpenAI and Microsoft, alongside all publisher and author lawsuits consolidated into the same docket.
First, a clarification of its legal standing: this is a government legal position filed pursuant to 28 U.S.C. § 517. It is neither legislation nor a judicial ruling, and it carries no binding authority over the court—Judge Stein is free to adopt or disregard it. Its significance lies in the executive branch officially placing its bet on the side of the AI industry, which will serve as a reference point for subsequent litigation and congressional policy debates.
The DOJ’s core argument unfolds in three layers. First, it bifurcates training from output: during training, entire books may be copied but are never exposed to the public, while at the output stage, generations “often if not always lack substantial similarity,” warranting separate fair use analyses. Second, it contends that training is “extraordinarily transformative,” citing precedents from the Google Books case and Google v. Oracle, while pointing out that model training does not produce market substitutes for the original works—tilting the market harm factor toward fair use as well. Third is a policy and national security framing: the DOJ argues that legal rules making it difficult for the U.S. to build a competitive AI industry “threaten national security and give a competitive advantage to foreign adversaries.”
The DOJ also directly targeted its own Copyright Office. In the statement, it asserted that former Register of Copyrights Shira Perlmutter’s refusal to grant blanket fair use to AI training in her May 2025 report “does not warrant deference” and that her analysis was “threadbare.” Perlmutter was removed by the Trump administration shortly after releasing the report and is currently contesting her dismissal. Crucially, the DOJ’s filing sidestepped one major issue: it does not address whether training on pirated materials constitutes fair use. This leaves the legality of pirated training corpora—such as those highlighted by Anthropic’s $1.5B settlement approved in July, covering roughly 480,000 books downloaded from shadow libraries—still unresolved.
The New York Times immediately rejected the government’s position. As reported by Politico, Times spokesperson Graham James stated that the administration is siding with “a handful of trillion-dollar AI companies” at the expense of “countless American creators whose work they stole.” To date, no federal appellate court has issued a substantive ruling on AI training and fair use; the first circuit court decision will be what truly sets the precedent.
According to a Bloomberg report on September 4 citing anonymous sources familiar with the matter, DeepSeek plans to deploy at least 160,000 of Huawei’s next-generation Ascend 950DT chips in its roughly 1 GW data center in Ulanqab, Inner Mongolia. This would mark the largest known single Ascend cluster to date, approaching roughly 80% of the scale of xAI’s Colossus Phase 1 (around 200,000 GPUs).
First, the necessary caveats: this originates from a single Bloomberg source. Neither DeepSeek nor Huawei has responded or made an official announcement, and no other top-tier outlets such as Reuters, the FT, or Caixin have corroborated the reporting yet. It remains a “plan,” not a confirmed fact. TechTimes calculated the order’s nominal value at roughly ¥17.76 billion (around $2.64B) based on an estimated market price of about ¥111,000 per chip, but this is a rough calculation, not a disclosed contract figure.
The most critical takeaway is the chips’ designated workload: they will be used exclusively for inference, not for training. DeepSeek still relies on Nvidia hardware to train its next-generation models. Previous Bloomberg reporting indicated that DeepSeek reverted to Nvidia after multiple training attempts on Ascend failed. Under this plan, domestic chips will handle the commercial monetization layer (API inference), but the core R&D layer (training) remains tied to Nvidia. This aligns directly with DeepSeek founder Liang Wenfeng’s assessment during a leaked July 2026 investor call: “four Huawei GPUs equal one Nvidia GPU, and it’s two years behind” (leaked call transcript recorded by Hello China Tech).
Delivery remains a hard constraint. The Ascend 950DT relies on Huawei’s in-house 144GB HiZQ 2.0 HBM, but high-end memory shortages have capped Huawei’s 950DT output this year at the “low end of hundreds of thousands,” which must also be shared across other clients. Bloomberg noted that fulfilling this order could take over a year, with some capacity targeted to come online by late 2027 or early 2028. The production ramp-up of domestic HBM (CXMT’s HBM3E remains in risk production) will directly determine whether Huawei can deliver on schedule. In parallel, DeepSeek is currently in talks to raise several billion dollars in funding to expand its infrastructure.
Open-source agent platform OpenClaw released version 2.0 (tagged v2026.8.1, official blog + GitHub release). It marks the largest single release in the project’s history: 16,000+ PRs and 933 contributors (569 of whom contributed for the first time); according to third-party data, it accounts for roughly half of all merged PRs in the project’s history. As of early September, the repository counted approximately 389k stars.
The release highlights three core features. First is simplified installation: onboarding detects existing ChatGPT/Claude subscriptions, API keys, and local models, verifying connectivity before saving, and can even import memories from Claude Code, Codex, and Hermes. Second is a rewritten browser Control UI with improved performance. Third is multiplayer support through shared cloud sessions, featuring three permission tiers: view, suggest, and contribute. The team explained that this stemmed from internal dogfooding: while developing 2.0, they wanted to bring colleagues into the same working session and realized OpenClaw previously couldn’t support it.
The real significance of this update lies in positioning rather than features: 2.0 pushes OpenClaw from a “personal AI assistant” into “team collaboration infrastructure.” That shift brings immediate permission and trust challenges. In the release notes for v2026.9.2 (a fast-follow release in September), the project issued a direct warning: when relevant settings are omitted, “agents with session tools can now read and search other agents’ conversations, including other users’ transcripts.” It urged administrators to set explicit visibility and agent limits, adding that mutually untrusted users require separate Gateways. This validates concerns raised by outlets like The Register regarding permission boundaries in shared sessions: when multiple users share an agent equipped with shell, email, and browser access, the blast radius of a single misconfiguration is far wider than in single-user setups.
Community reception is equally telling. The upgrade path remains unpolished, with r/openclaw overwhelmingly advising a clean install over an upgrade, and users continuing to report frozen upgrades even after v2026.9.2 rolled out. Licensing also remains unclear: the GitHub API returns NOASSERTION, whereas most media reports describe it as MIT.
Employer review data is sending clear signals. On August 27, Glassdoor’s Economic Research team published a report titled How workers feel about AI in 2026, analyzing reviews submitted by full-time and part-time U.S. employees. The headline figures: AI mentions surged 240% year-over-year in May 2026; among reviews mentioning AI, the share of positive sentiment dropped from 81% in 2019 to 43% in 2026, while negative sentiment reached 53%.
Sentiment is strongly linked to layoffs and burnout. Employees who mention AI in their “cons” are 6.0 times more likely to mention layoffs than the baseline, and 3.7 times more likely to cite burnout or career insecurity; 25% of reviews citing AI in the cons mention layoffs concurrently. The occupational divide is extreme: insurance claims adjusters registered a 98% negative sentiment rate toward AI, with writers, journalists, accountants, customer service reps, designers, and IT professionals also expressing widespread negativity. Conversely, senior corporate leadership expressed the highest positive sentiment (with 67% of AI mentions falling in the pros). While the tech sector mentioned AI 3.6 times more often than the baseline, not a single industry exhibited net-positive sentiment toward AI—even the legal sector, the most favorable, stood at just 50%.
Methodology warrants clarification: this report is based on text analysis of workplace reviews rather than a questionnaire survey. Reviews were tagged as mentioning AI if they contained standalone terms such as AI, LLM(s), GPT(s), Artificial Intelligence, or OpenAI, with sentiment classified by whether the mention appeared under “pros” or “cons”—representing descriptive correlations rather than causal conclusions.
These findings neatly complement the prevailing “layoff-and-rehire” narrative. Research by University of Pittsburgh professor Mark Ma and colleagues published in The Conversation (analyzing millions of Glassdoor reviews alongside roughly 10,000 earnings call transcripts) provides a mechanistic explanation: AI-driven layoffs and resulting job insecurity are “actively destroying the very conditions needed for AI to make workers more efficient,” while leadership’s optimistic statements on earnings calls show no correlation with actual productivity. For AI product builders, the data offers a sober reminder: the pace of tool adoption is ultimately bounded by the fears of the people asked to use it, not merely by the capability of the tool itself.