# 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. Canonical: https://rangoon.ai/insights/white-house-super-intelligence-si-terminology/ Author: Rangoon Editorial (https://rangoon.ai/insights/editorial/) Published: 2026-10-10 Updated: 2026-10-10 Event date: 2026-09-29 Tags: [Super Intelligence](https://rangoon.ai/insights/tags/super-intelligence/), [SI](https://rangoon.ai/insights/tags/si/), [AI governance](https://rangoon.ai/insights/tags/ai-governance/), [Federal terminology](https://rangoon.ai/insights/tags/federal-terminology/) Source note: 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. Image: White House North Lawn in Washington, D.C., photographed October 10, 2023. Context photograph; it does not depict the September 2026 signing or prove a superintelligence capability. Credit: Harrison Keely Source: [Source photograph](https://commons.wikimedia.org/wiki/File:The_White_House_North_Lawn_in_Washington,_D.C.jpg) Rights: [Rights information](https://creativecommons.org/licenses/by/4.0/) Rights note: CC BY 4.0. Credit: Harrison Keely. Original JPEG unchanged; WebP derivatives resized and cropped. Attribution, license link and change notice required. No government endorsement or trademark/personality rights granted by Hypler. ## 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](https://www.whitehouse.gov/presidential-actions/2026/09/inaugurating-the-era-of-super-intelligence/) [source 3](https://www.law.cornell.edu/uscode/text/15/9401) 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](https://www.nasa.gov/what-is-super-intelligence/) [source 3](https://www.law.cornell.edu/uscode/text/15/9401) 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. ## Analysis: authorization remains separate from names A renamed inventory item still needs the same decisions about data access, release approval and execution scope. An assistant may summarize a contract without permission to alter it; a workflow may prepare a deployment without permission to publish it. Operators should bind approval to an exact action, target and payload, then record enforcement and outcome. Changing a title from AI to SI should never widen a connector's access or convert a recommendation into an authorized action. Rangoon.si displays the brand direction while the canonical Rangoon.ai address remains in place. Its active development architecture keeps execution authority at a separate boundary, using pluggable policy engines and permission checks rather than a rename. LNSAT is one reference execution-authority path: it can evaluate a proposed operation and preserve evidence, but it does not make a policy decision disappear behind terminology. This is development context, not a claim of shipment, certification, government use or endorsement. ## 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. ## Rangoon connection ### Terminology can change without changing authority Rangoon.si is active development. Rangoon.ai remains canonical. Its LNSAT reference path keeps policy engines and permission checks pluggable at the execution boundary; terminology alone does not authorize an operation. No shipment, certification, government use or endorsement is claimed. [Learn more](https://rangoon.ai/architecture/) ## Sources 1. [White House: Executive Order 14434, Inaugurating the Era of Super Intelligence](https://www.whitehouse.gov/presidential-actions/2026/09/inaugurating-the-era-of-super-intelligence/) 2. [NASA: What Is Super Intelligence?](https://www.nasa.gov/what-is-super-intelligence/) 3. [Cornell Legal Information Institute: 15 U.S.C. 9401, Definitions](https://www.law.cornell.edu/uscode/text/15/9401) ## Related reading - [NIST, NSA and CISA publish voluntary SI incident-readiness practices](https://rangoon.ai/insights/nist-si-incident-readiness/) - [UK’s third-party AI assurance roadmap mapped professionalization, information access and a planned innovation fund](https://rangoon.ai/insights/archive-uk-trusted-third-party-ai-assurance-roadmap-september-2025/) - [UK’s AI Playbook expanded government guidance to ten principles across selection, deployment and assurance](https://rangoon.ai/insights/archive-uk-government-ai-playbook-february-2025/) ## Related Rangoon material - [Super Intelligence](https://rangoon.ai/super-intelligence/) - [Government solutions](https://rangoon.ai/solutions/government/) - [Software governance](https://rangoon.ai/software/execution-governance/) - [September 29 meeting analysis](https://rangoon.ai/insights/trump-super-intelligence-accord-agent-governance/) ## More information - [Documentation index](https://rangoon.ai/llms.txt) - [AI access and policies](https://rangoon.ai/ai/) - [Source repository](https://github.com/hypler-dev/rangoon)