White House SI terminology order: what changes for federal AI governance
Executive Order 14434 changes executive-branch terminology to Super Intelligence and SI. Agencies still need separate controls for systems, data and execution authority.
Executive Order 14434 was published September 29, 2026. This article separates official terminology and statutory facts from independent operational analysis. It does not provide legal advice or assert a federal mandate beyond the order's stated scope.
Key takeaways
- The order directs executive-branch communications and non-statutory materials to use Super Intelligence and SI, while leaving historical documents unchanged.
- The existing statutory AI definition remains the reference point while a legislative SI proposal is prepared; no new statutory definition was enacted by the order.
- Names, capability claims and authorization to act are separate records that should remain separately reviewable.
What the terminology order does[source 1][source 3]
Executive Order 14434, published by the White House on September 29, 2026, directs executive departments and agencies to use Super Intelligence and SI in place of Artificial Intelligence and AI for communications and other non-statutory materials, to the extent permitted by law. The order also says previously issued regulations, contracts, grants and historical documents do not need to change. That is a terminology instruction for current federal communications, not proof that a new class of technical system has appeared.
The order points to the existing definition of artificial intelligence in 15 U.S.C. 9401(3) while directing a legislative proposal for an SI definition within 60 days. A requested proposal is not enacted law. Teams reading the order should therefore avoid describing it as a new statutory capability threshold or as a mandate to recertify systems. The authoritative question for any particular record remains its applicable legal and program context.
NASA shows how agencies can adopt the language[source 2][source 3]
NASA's public explainer, What Is Super Intelligence?, uses the new term and points readers back to the established federal AI definition. That presentation is useful because it treats SI as current public terminology while preserving a traceable reference to the existing definition. It does not announce a separate NASA technical test, a new procurement category or a finding that any system meets a superhuman benchmark.
For communications owners, the practical lesson is modest: update outward-facing vocabulary where the order applies, then retain enough context for readers to find older AI-era material. A glossary, a redirect note or an alias field can make that transition legible. Rewriting every historical title can erase decision context and create needless disputes over which record was in force at the time.
Analysis: terminology migration is not a capability claim
A name change should not collapse three different questions: what a system is called, what it can do and what it may do. Technical capability still needs task-specific evidence: model version, evaluation method, operating conditions, known limits and measured results. A system called SI may be a conventional classifier, a retrieval assistant or an agentic workflow. Conversely, a high-performing system does not gain authority because a label becomes fashionable.
This distinction matters in procurement and inventory work. Agencies can add SI as a display term and preserve AI as a searchable alias during a migration. Supplier records, model cards, purchase orders, API fields and security findings should retain stable identifiers instead of depending on a renamed label. If a telemetry namespace moves from ai.* to si.*, dashboards need a documented mapping, bounded dual-write period and checks for missing events. Otherwise a communications update can make operational history look like a system outage.
What operators can do next
A sensible migration plan starts with a scoped communications inventory, not a bulk rename. Mark which pages, templates and non-statutory materials are in scope; identify immutable identifiers and contractual names that must stay stable; then publish an alias policy for search and analytics. Monitor telemetry continuity during the namespace change and preserve the old-to-new mapping with the event schema. Review exceptions with the owner of each system rather than assuming every occurrence of AI has the same status.
None of these recommendations creates a legal requirement. They are independent operational practices for keeping records, measurements and authority understandable while terminology changes. The order supplies a naming direction; each agency still needs to determine its own implementation, controls and approvals under applicable law and policy.
Sources
Continue reading
Related reading
News analysisNIST, NSA and CISA publish voluntary SI incident-readiness practices3 min read
News analysisUK’s third-party AI assurance roadmap mapped professionalization, information access and a planned innovation fund3 min read
News analysisUK’s AI Playbook expanded government guidance to ten principles across selection, deployment and assurance3 min readRelated Rangoon material
Super Intelligence Government solutions Software governance September 29 meeting analysis