← Back to today's topics

Verified · Oct 21, 2026

Independently verified

The DeepSeek order covering US federal civilian agencies is dated July 24 — what landed Tuesday is its publication in the Federal Register, exceptions and all

4 sources

On October 20, 2026 (Tuesday, calendar-verified), the Federal Register published DHS's DeepSeek exclusion-and-removal order (Volume 91, Number 201, Document Number 2026-21447, Docket No. DHS-2026-0628; FR Doc. filed 10-19-26; 8:45 am). Per the notice's SUMMARY, the order is '(1) excluding information technology products and services developed by Hangzhou DeepSeek Artificial Intelligence Co., Ltd (DeepSeek), to include affiliated entities as defined in applicable regulations, from federal civilian agency procurements; and, (2) removing all DeepSeek and DeepSeek-affiliate products, and third-party products and services developed using DeepSeek implementations, from civilian agency information technology.' The signed order in the Appendix — 'Exclusion and Removal Order #2026-01', issued by Secretary Markwayne Mullin — carries its own header 'Original Release Date: July 24, 2026' (Friday, calendar-verified; read from the scanned appendix pages): the news is the publication of a July 24 order, and per CyberScoop (Monday October 19) 'the ban has been in place for months'. The order's stated risks, per its own Summary of Risks: 'DeepSeek's models present multiple threat vectors.'; 'DeepSeek servers are located in the PRC, and the PRC legal system permits extensive authority to government cyber and intelligence functions to access private company infrastructure.'; 'For DeepSeek-hosted instances of their models, DeepSeek's account generation process collects personally identifiable information (PII) and may also track and digitally fingerprint users.'; and 'The models themselves may contain malware or other security vulnerabilities. Indeed, open-source security research has found that the DeepSeek iOS mobile application contains multiple critical vulnerabilities.' Mechanics, per the order: exclusion is 'effective immediately after issuance of this Order'; removal runs 'immediately after the issuance of the Order, or seek an Exception, as described below.'; 'Executive agency requests for exceptions must be submitted in writing within 60 days of the issuance of this order', and 'CISA will review requests for exceptions and provide a written approval or disapproval.' China's response came the same day at the Foreign Ministry briefing: per the official transcript, Mao Ning said 'China consistently opposes overstretching the concept of national security and politicizing tech and trade issues. We will resolutely safeguard Chinese businesses' lawful rights and interests.' (zh original: 「中方一贯反对泛化国家安全概念、将科技经贸问题政治化。我们将坚决维护中国企业合法权益。」) Per TechCrunch (Kate Park, 6:07 AM PDT October 20), the order 'goes beyond banning DeepSeek's own product, but also covers third-party products and services built using DeepSeek technology, though agencies can request exceptions' — and TechCrunch's rendering of Mao Ning's answer reads 'technology and trade issues' and 'the legitimate rights and interests of Chinese enterprises'.

Why now

A paperwork milestone with a built-in honesty check — and the check is the content. Layer one, the date your audience will get wrong: the order's own header reads 'Original Release Date: July 24, 2026', and the Federal Register publication is Tuesday, October 20 (filed Monday the 19th) — the opened relay (TechCrunch, October 20) ran it as a fresh 'US orders' without the order's July 24 date, while CyberScoop had it the day before publication and even dates Mullin's letter June 26, a date that conflicts with the artifact. Layer two, the scope line that keeps you accurate: per the order's own text it applies to 'Federal Civilian Executive Branch Agencies except for their national security systems and secure compartmented information systems' — this is a federal-civilian procurement and IT action, not a US consumer ban, and no opened source supports any private-sector effect. Layer three, the mechanics nobody relays: exceptions exist — 'Executive agency requests for exceptions must be submitted in writing within 60 days of the issuance of this order', CISA issues 'a written approval or disapproval', and the interim measures are steps agencies are 'encouraged' to take, not mandates. Layer four, the response beat: the Foreign Ministry's own October 20 transcript carries Mao Ning's answer in full, and the MFA's English wording differs from TechCrunch's — a live demonstration of why per-outlet quoting matters.

Why it is worth publishing

The rare story where reading the primary document makes you materially more accurate than every relay: the two-date structure (July 24 order, October 20 publication), the federal-civilian-only scope, and the 60-day exceptions mechanism all vanish in flattened coverage. Creators who publish the document-faithful version own the AI-policy explainer beat this cycle — and the verification skill involved (opening a Federal Register PDF, reading its scanned appendix) is itself showable content for an audience that keeps seeing 'ban' headlines without the mechanics.

Evidence basis

Four opened sources: the Federal Register notice (official; API + raw text + govinfo PDF; publication 2026-10-20 per the volume's own 'Tuesday, October 20, 2026' header, filed 10-19-26 8:45 am; the appendix order scans read page-by-page at full resolution — no text layer exists, so appendix quotes are image-read and marked) and the MFA's bilingual briefing transcripts (official; both locales opened). Calendar checks: October 20, 2026 = Tuesday; October 19 = Monday; July 24, 2026 = Friday; June 26, 2026 = Friday; October 21 (card publish) = Wednesday. THE DATE CONFLICT IS CARRIED: the order's header says July 24; CyberScoop's sentence dates the letter June 26 — the artifact governs, and CyberScoop's date stays CyberScoop's. Per-outlet discipline: the MFA's English transcript ('tech and trade issues' / 'Chinese businesses' lawful rights and interests') vs TechCrunch's ('technology and trade issues' / 'the legitimate rights and interests of Chinese enterprises') — never blended; CyberScoop's '60 days in advance' vs the order's 'within 60 days of the issuance of this order'. TechCrunch's December 2025 law, September distillation report, Bloomberg export-controls item, and OpenAI/Anthropic distillation concerns ride TechCrunch's sentences only. The web-search quota was exhausted this run — sources reached by direct fetches (09-08 fallback) with Google News RSS as the second-source finder (10-18 precedent).

“The DeepSeek order reshaping US federal civilian agencies carries a July 24 release date — Tuesday's news is just that it's now published paperwork.”

Angle

Frame it as 'everyone showed you the ban headline — here's the document, its real date, and its exceptions door' in four beats. Beat one, the two dates: the order's own header says 'Original Release Date: July 24, 2026'; what happened October 20 is its publication in the Federal Register (filed October 19) — show both pages. Beat two, the scope, quoted: 'Federal Civilian Executive Branch Agencies except for their national security systems and secure compartmented information systems' — federal procurement and IT, not consumers, not companies. Beat three, the mechanics: exclusion effective immediately, removal immediate or exception, exception requests in writing within 60 days of issuance with CISA issuing 'a written approval or disapproval'. Beat four, the response: Mao Ning's answer from the Foreign Ministry's own transcript — and the bonus lesson that the MFA's English wording and TechCrunch's differ.

Format

Carousel

Demo idea

A show-the-document carousel: card one puts the order's 'Original Release Date: July 24, 2026' header next to the Federal Register's 'Tuesday, October 20, 2026' volume header; card two quotes the SUMMARY's exclude/remove verbs with 'third-party products and services developed using DeepSeek implementations' highlighted; card three diagrams the exceptions path (written request, within 60 days of issuance, CISA written approval or disapproval); closing card contrasts the federal-civilian scope line with the 'total US ban' headline framing.

Platform notes

Every date sentence names its date: July 24 stays the order's own release date per the artifact's header (CyberScoop's June 26 stays CyberScoop's), October 20 stays the Federal Register publication, October 19 the filing — never 'a new ban this week'. Scope stays federal civilian executive branch — never 'banned in the US', never a consumer or company claim. Threat language stays order-attributed ('the order's Summary of Risks says...'), and the iOS-vulnerability line stays the order's citation of open-source security research. The exception mechanism (written, within 60 days of issuance, CISA approval or disapproval) stays attached wherever the order's requirements appear; interim measures stay 'encouraged', never mandated. Mao Ning's words keep their per-outlet rendering (MFA transcript primary; TechCrunch's version labeled as TechCrunch's) — never a blended third form, never 'retaliated' (no source states it). zh scripts keep DeepSeek, DHS, CISA, Federal Register in English, write 刊出/发布 for October 20 — never 签发 — keep 排除出采购、从信息技术中移除 as the two verbs, keep 联邦文职机构 scoped, keep 「多重威胁向量」 as 命令自己的说法, and quote 毛宁 from 外交部官方实录.

Usable claims

  • On October 20, 2026 (Tuesday, calendar-verified), DHS's exclusion-and-removal order for DeepSeek was published in the Federal Register (Volume 91, Number 201, pages 66346-66350; Document Number 2026-21447; Docket No. DHS-2026-0628; FR Doc. 2026-21447 Filed 10-19-26; 8:45 am — Monday). Per the notice's SUMMARY, the Department of Homeland Security is publishing notice of the Secretary's issuance of an order '(1) excluding information technology products and services developed by Hangzhou DeepSeek Artificial Intelligence Co., Ltd (DeepSeek), to include affiliated entities as defined in applicable regulations, from federal civilian agency procurements; and, (2) removing all DeepSeek and DeepSeek-affiliate products, and third-party products and services developed using DeepSeek implementations, from civilian agency information technology.' The signed order in the Appendix — 'Exclusion and Removal Order #2026-01', issued by Secretary Markwayne Mullin — carries its own header 'Original Release Date: July 24, 2026' (Friday, calendar-verified; image-read from the scanned appendix pages): the October 20 event is the publication of a July 24 order, and per CyberScoop (Derek B. Johnson, Monday October 19) 'the ban has been in place for months'. The order's stated risks (image-read): 'DeepSeek's models present multiple threat vectors.'; 'DeepSeek servers are located in the PRC, and the PRC legal system permits extensive authority to government cyber and intelligence functions to access private company infrastructure.'; 'For DeepSeek-hosted instances of their models, DeepSeek's account generation process collects personally identifiable information (PII) and may also track and digitally fingerprint users.'; and 'The models themselves may contain malware or other security vulnerabilities. Indeed, open-source security research has found that the DeepSeek iOS mobile application contains multiple critical vulnerabilities.' Required actions (image-read): exclusion is 'effective immediately after issuance of this Order', and removal runs 'immediately after the issuance of the Order, or seek an Exception, as described below.' Exceptions (image-read): 'Executive agency requests for exceptions must be submitted in writing within 60 days of the issuance of this order', and 'CISA will review requests for exceptions and provide a written approval or disapproval.' China's response came the same day, per the MFA's own October 20 briefing transcripts: Mao Ning, per the official English transcript, said 'China consistently opposes overstretching the concept of national security and politicizing tech and trade issues. We will resolutely safeguard Chinese businesses' lawful rights and interests.' (zh original: 「中方一贯反对泛化国家安全概念、将科技经贸问题政治化。我们将坚决维护中国企业合法权益。」). Per TechCrunch (Kate Park, 6:07 AM PDT October 20), the order 'goes beyond banning DeepSeek's own product, but also covers third-party products and services built using DeepSeek technology, though agencies can request exceptions', and — per TechCrunch's rendering of the same MFA answer — Mao Ning opposes 'overstretching the concept of national security and politicizing technology and trade issues' and said 'We will resolutely safeguard the legitimate rights and interests of Chinese enterprises,' in TechCrunch's rendering — the MFA's own transcript wording differs and is kept per-outlet.

Evidence pipeline

Breakdown

A government-document story where the discipline is refusing the relay's flattening. Layer one, the dates: the order's own header reads 'Original Release Date: July 24, 2026' — the Federal Register notice of October 20 (filed October 19) is the publication of an existing order, and CyberScoop's June 26 letter date conflicts with the artifact, so the artifact governs and CyberScoop's date stays CyberScoop's. Layer two, the scope: the order applies to 'Federal Civilian Executive Branch Agencies except for their national security systems and secure compartmented information systems' — procurement exclusion plus IT removal, never a consumer or economy-wide ban. Layer three, the threat language stays attributed: 'multiple threat vectors' and the PII and server-location sentences are the order's own Summary of Risks, and the iOS-vulnerability line is the order's citation of open-source security research — the order's claims, not independently established findings. Layer four, the mechanics the relays drop: exceptions in writing within 60 days of issuance, CISA's 'written approval or disapproval', interim measures agencies are 'encouraged' to take. Layer five, the response beat: Mao Ning's answer exists in the MFA's own English transcript, TechCrunch's rendering, and the zh original — each stays that outlet's. Editor's rules: the artifact dates the artifact, the scope line kills the headline, and every rendering of the same foreign-official quote stays per-outlet.

Risks

  • Before publishing, re-check each layer: every date sentence names which date it means (order issuance July 24 per the artifact, FR publication October 20, filing October 19); the scope stays federal civilian executive branch; the threat sentences stay order-attributed; the exception mechanism (60 days, written, CISA approval or disapproval) stays attached wherever the order's requirements appear; Mao Ning's words carry their per-outlet rendering. If your script compresses any of these, cut the detail rather than round it.

Demo ideas

  • Show-the-document carousel: the July 24 order header beside the October 20 Federal Register volume header, with the exclude/remove verbs and the exceptions path diagrammed
  • Headline-vs-document segment: read one outlet's 'US orders' framing against the order's own release-date header and scope line, then explain what the difference changes