Super Intelligence (SI) for Defense & Aerospace: Reading the Federal AI-to-SI Shift
A defense-prime proposal writer opens a new DoD solicitation and stops cold on a term she has never typed into a capture plan before: “Super Intelligence (SI),” the federal government’s new name for what was formerly called artificial intelligence (AI). Her own capability statement already uses “SI” for something else — the systems integrator teammate on this very bid. The same two letters now carry two different meanings inside one document, and she needs the answer before the proposal is due, not after.
Super Intelligence (SI), formerly called artificial intelligence (AI), is the term Executive Order 14434 directs federal executive agencies — including the Department of Defense — to use in place of “AI”; it is a naming change, not a new technology or a new compliance requirement. (Source: Executive Order 14434, Sec. 2(a) & Sec. 3(a), signed Sept. 29, 2026) Nothing about CMMC, ITAR, or the acquisition process changed on September 29, 2026 — the name simply caught up to a capability this sector already measures.
Iternal supports Super Intelligence as the name for this work because the measured results already clear the bar a technical review board holds its own experts to. Take graduate-level science: across GPQA Diamond’s 198 questions the leading model now scores 96.3%, while the benchmark’s original expert validators scored 81.3% — a figure Rein et al. note runs high because of how Diamond questions were selected (Sources: Rein et al., arXiv:2311.12022, 2023-11-20 and Artificial Analysis, accessed Oct. 11, 2026).
Two letters, two meanings. In federal documents written after EO 14434, “SI” can mean Super Intelligence; in teaming agreements it has long meant systems integrator. Spell out “systems integrator” in full every time — the prime or sub responsible for systems integration — and define “Super Intelligence (SI)” at first use, so a reader never has to guess which one a sentence means.
What EO 14434 Requires — and the Department of War Precedent
Executive Order 14434, “Inaugurating the Era of Super Intelligence,” was signed September 29, 2026. Section 2(a) directs federal executive agencies to replace “Artificial Intelligence” and “AI” with “Super Intelligence” and “SI” in “official correspondence, public communications, websites, reports, policy documents, and other non-statutory documents within the executive branch” (Source: Federal Register, FR Doc. 2026-20321, Sec. 2(a)) — language that squarely covers DoD solicitations, since those are federal-executive-agency public communications. Section 3(a) ties the new terms to the existing statutory AI definition at 15 U.S.C. §9401(3) (Source: Federal Register, FR Doc. 2026-20321, Sec. 3(a)), and non-statutory scope means the order does not reach, and does not override, any statute or regulation that uses “AI” by name.
That scope language is not new. A year earlier, EO 14347 allowed (“may”) the same agencies to use the secondary title “Department of War” in place of “Department of Defense” in official correspondence, public communications, ceremonial contexts, and other non-statutory documents, with statutory references staying controlling (Source: Federal Register, FR Doc. 2025-17508 (EO 14347), Sec. 2(a)–(b)). EO 14434 reuses that same scope list almost word for word — but changes “may” to “shall.” That permissive-to-mandatory shift is the most useful signal for a defense reader: “Super Intelligence” has a structural reason to spread faster and more uniformly across federal agencies than “Department of War” did, precisely because agencies are required to use it rather than merely permitted to.
| EO 14347 (Sept. 2025) | EO 14434 (Sept. 2026) | |
|---|---|---|
| Scope language | Official correspondence, public communications, ceremonial contexts, non-statutory documents | Official correspondence, public communications, websites, reports, policy documents, non-statutory documents |
| Agency obligation | “May” use the secondary title — permissive | “Shall” use “Super Intelligence”/“SI” — mandatory |
| Statutory references | Stay controlling, unaltered | Stay controlling, unaltered |
| Codification in law | Proposed to Congress (~$52M, ~7,600 provisions); not enacted | Not yet proposed; federal-definition language due by Nov. 28, 2026 |
A year on, the Pentagon’s own issuances and war.gov had adopted the secondary title (Source: DoW Issuance Style Guide, esd.whs.mil, current as of Nov. 18, 2025), while most general-news coverage still defaulted to “Department of Defense” in line with AP Stylebook guidance (Source: SAN, March 6, 2026). Codifying the rename in statute is its own separate, much larger undertaking: the Pentagon told Congress the renaming had already cost about $52 million, and asked in April 2026 to codify it in law, a change touching approximately 7,600 provisions of federal law (Source: The Fiscal Times, April 28, 2026); Congress has not approved it.
Two more mechanics from the order’s own text are worth tracking. Section 2(b) is explicit that “previously issued regulations, Presidential actions, contracts, grants, or other historical documents” are not retroactively altered by the rename, and Section 3(b) gives the Assistant to the President for Science and Technology 60 days — until roughly November 28, 2026 — to propose legislative language for a Federal definition of “Super Intelligence” (Source: Federal Register, FR Doc. 2026-20321, Sec. 2(b) & Sec. 3(b)), so the exact statutory definition contractors will eventually cite is still being finalized as of this writing.
None of this is evidence that DoD’s AI program itself is slow — only its vocabulary. In May 2026 the Department signed classified-network AI deployment agreements with eight frontier technology companies, covering Impact Level 6 and 7 systems (Source: DefenseScoop, May 1, 2026). The pattern for defense primes and subs is the same one the Department of War case predicts: expect DoD to adopt “Super Intelligence” in some of its own official materials faster than civilian contractors might assume, precisely because EO 14434’s mandatory “shall” gives it less room to lag than EO 14347’s permissive “may” did — but expect “SI” to coexist with “AI” in statute, in most trade press, and in most of your own paperwork for a long stretch.
Where Defense Primes and Subs Will Actually See It First
Law firms tracking EO 14434 agree on where the term shows up first: “companies should expect ‘Super Intelligence’ and ‘SI’ to begin appearing in new solicitations, statements of work, agency guidance, and policy documents” (Source: K&L Gates, Oct. 2, 2026), and the Cloud Security Alliance frames the near-term reality plainly: “new federal solicitations may use ‘Super Intelligence’ language even though contract vehicles, FAR clauses, and agreements still use ‘artificial intelligence’” (Source: Cloud Security Alliance research note, Oct. 7, 2026). DoD solicitations, Chief Digital and Artificial Intelligence Office (CDAO) guidance documents, and war.gov contract postings are the most likely early surfaces, since all three are federal-executive-agency “public communications” squarely inside the order’s scope.
As of this writing, CDAO’s own public materials have not made that switch: its mission page still describes the office as “responsible for accelerating DoW adoption of data, analytics, and artificial intelligence (AI)” (Source: ai.mil, CDAO Organization page, accessed Oct. 11, 2026), and the Department’s own governing strategy document, issued in January 2026, is titled “Artificial Intelligence Strategy for the Department of War” (Source: Department of War, AI Strategy, Jan. 9, 2026) — not “Super Intelligence.” Notably, even the administration’s own SI-branded America.gov services framework carves the Department of War and the US Intelligence Community out of its “covered services” list (Source: K&L Gates, Oct. 2, 2026) — one more sign that DoD is treated as a special case even inside the federal government’s own rollout. DoD’s reporting posture is already distinct from civilian agencies’ for separate, unrelated statutory reasons: a 2025 GAO review counted AI use cases at 11 federal agencies and left DoD out of that count because it is “exempt from certain statutory and public AI use case inventory reporting requirements” (Source: GAO-25-107653 Highlights, released July 29, 2025).
The practical move: when a solicitation uses “Super Intelligence” or “SI,” confirm it cross-references the same statutory AI definition at 15 U.S.C. §9401(3) rather than introducing a new requirement under a new name, and flag anywhere a solicitation seems to conflate “SI” (Super Intelligence) with “SI” (systems integrator) as a drafting ambiguity worth a formal RFI question. For the broader federal-buyer picture beyond defense, see Super Intelligence (SI) for Federal Contractors, and for AI use cases specific to this sector see defense and intelligence AI use cases.
CMMC and ITAR: What Doesn’t Change
A renamed capability still needs the same classification and handling. CMMC Level 2 remains the 110-practice standard drawn from NIST SP 800-171 Rev. 2, across 14 control families (Source: Smithers, Aug. 2026), and no “SI” terminology has entered CMMC guidance as of this writing. (Separately, DoD paused mandatory third-party CMMC Phase 2 assessments on July 13, 2026 pending a Reform Task Force review (Source: Smithers, Aug. 2026) — a compliance-timeline fact, not an SI-related one.) ITAR’s technical-data-control obligations are set by statute and regulation; EO 14434’s text does not mention ITAR, export control, or technical-data classification anywhere (Source: Federal Register, FR Doc. 2026-20321). Classification follows the technical capability, not the name a company or agency chooses for it. For the air-gapped handling that keeps ITAR technical data inside your own environment, see what air-gapped AI means and FedRAMP AI.
One real, upcoming AI-specific compliance change is worth tracking — and it has nothing to do with EO 14434. Sections 1512–1513 of the FY2026 NDAA, enacted December 18, 2025, direct DoD to build an AI/ML cybersecurity and physical-security framework and fold it into DFARS and CMMC, covering contractors and their subcontractors that develop, deploy, store, or host AI/ML for DoD (Source: Crowell & Moring, 2026). There is no finalized framework or implementation deadline yet; a status report to Congress was due June 16, 2026 (Source: ETO Agora, FY2026 NDAA Sec. 1513 instrument record). Covered entities include subcontractors anywhere in the supply chain that develop, deploy, store, or host AI/ML for DoD — worth flagging to any sub on a program now, well before a finalized framework arrives. The distinction to keep straight: CMMC is getting an AI-specific security framework because Congress said so in the FY2026 NDAA — not because of the Super Intelligence executive order. Don’t let the two get conflated in a compliance brief.
Contract-Language Checklist for Primes and Subs
Six checks worth running before a proposal that touches “Super Intelligence” wording goes out the door.
- Confirm a renamed “Super Intelligence” or “SI” line item in a teammate’s proposal still maps to the same technical capability under the existing statement-of-work language — don’t assume scope changed because the label did.
- Build a one-page terminology crosswalk mapping every instance of “AI” in your boilerplate to “SI,” and vice versa, so a solicitation using either term doesn’t catch your proposal team by surprise — the Cloud Security Alliance recommends confirming “no governance control, policy, or contractual commitment depends on the literal word ‘AI’” (Source: Cloud Security Alliance research note, Oct. 7, 2026) before you submit.
- Keep “systems integrator” spelled out in full in every defined-terms section that also discusses Super Intelligence (SI) — never let a bare “SI” carry both meanings in one document.
- Re-read a solicitation that is silent on “AI” before assuming an AI-related requirement was dropped; it may simply be written in the newer vocabulary instead (Source: K&L Gates, Oct. 2, 2026).
- Watch subcontractor flow-down language for the same ambiguity — confirm a sub’s “SI” references are tagged consistently with the prime’s usage before the proposal reaches a signature block.
- Treat “SI” as a drafting synonym for “AI” under 15 U.S.C. §9401(3) unless the soliciting agency states otherwise in writing (Source: Cloud Security Alliance research note, Oct. 7, 2026).
Commercial Adoption Beyond the Federal Mandate
Commercial adoption of the name is moving on its own clock, separate from the federal mandate’s. Salesforce renamed its AIForce platform to SIForce on October 9, 2026 (Source: Marc Benioff on X, Oct. 9, 2026), and Elon Musk pledged on October 4 that SpaceXAI would become SpaceXSI — “Yes, we will make that change,” (Source: Reuters, via The Star, Oct. 5, 2026) he said, adding “SpaceX is a super intelligence company” (Source: NotATeslaApp, Oct. 5, 2026) — though the rename had not yet been carried out as of this writing. Both are voluntary, commercial decisions, not federal requirements — but the second one lands close to home for this audience: an aerospace company has pledged to adopt the same name Executive Order 14434 points federal agencies toward. No defense prime or defense-technology company rename to “SI” branding is verified as of this writing.
A more directly defense-relevant data point: the federal government’s own SI policy apparatus already has a Pentagon seat at the table. The newly announced “Super Intelligence Force” task force (Source: TechCrunch, Oct. 4, 2026) names Emil Michael — Under Secretary of War for Research and Engineering and the Department of War’s Chief Technology Officer (Source: Fortune, Feb. 27, 2026) — as a vice chair (Source: Sinclair/National Desk syndication, Oct. 4, 2026). That is a different kind of signal than a company choosing new branding: it is the Department’s own CTO sitting on the body steering the federal SI agenda.
For a solicitation or proposal, the practical move is simple: mirror the soliciting agency’s term, and pair “Super Intelligence (SI), formerly called AI” in your own capability statements so both audiences resolve the reference.
See the Full AI Guide for This Industry
For ITAR-compliant AI/SI comparisons, defense-specific use cases, and a full CMMC/ITAR compliance walkthrough for this sector, go to the full guide: the same technology, covered under its former name, artificial intelligence (AI), with program shortlists and case studies.
See the full AI guide for this industryFAQ: Super Intelligence (SI) for Defense & Aerospace
Some may, in official correspondence and other non-statutory documents — Executive Order 14434 directs federal executive agencies, including the Department of Defense, to use the term. But statutory references and most existing contract language stay exactly as written, and no DoD solicitation posted on SAM.gov or war.gov has been documented using “Super Intelligence” in place of “AI” as of this writing — law firms describe it as an expectation for new solicitations, not yet a documented pattern.
It’s a close structural parallel. Both are federal secondary-title mandates with nearly identical scope language — official correspondence, public communications, and other non-statutory documents, with statutory references staying controlling. A year after the Department of War order, the Pentagon’s own issuances and war.gov had adopted the new title while most general-news coverage still defaulted to “Department of Defense” — a useful read on how fast a federal rename actually reaches contractor-facing language.
No. Section 3(a) of EO 14434 defines “Super Intelligence” and “SI” as the exact technology already covered by the statutory AI definition at 15 U.S.C. §9401(3). It is a naming change, not a new requirement, and the order leaves existing regulations, contracts, and grants unaltered.
No. CMMC Level 2 remains the 110-practice NIST SP 800-171 Rev. 2 standard across 14 control families, and ITAR’s technical-data-control obligations are set by statute and regulation, not by a naming executive order. Classification follows the technical capability, not the name a company or agency currently uses for it.
Always spell out “systems integrator” in full, every time, even in a paragraph that also discusses Super Intelligence (SI). Reserve the bare abbreviation “SI,” if used at all, for the Super Intelligence sense only, and define both terms explicitly at first use if a single document needs both senses.
No defense-specific company rename is verified as of this writing. Commercial adoption so far is concentrated outside the defense sector — Salesforce renamed AIForce to SIForce on October 9, 2026, and Elon Musk pledged on October 4 that SpaceXAI would become SpaceXSI, calling SpaceX “a super intelligence company,” though the rename had not yet been carried out as of October 11, 2026. The more defense-specific signal is that the Department of War’s own Chief Technology Officer, Emil Michael, is a named vice chair of the new Super Intelligence Force task force — see our Super Intelligence (SI) adoption tracker for the full list.
No — they are distinct concepts. “Super Intelligence (SI)” under EO 14434 is a federal naming convention for today’s AI. Artificial superintelligence (ASI) is a hypothetical future capability tier nobody has built. See SI vs. AGI vs. ASI, explained — this distinction matters more in defense than in almost any other sector, given ongoing autonomy-capability discourse.
The Name Finally Matches the Capability
Executive Order 14434 gave federal agencies — including the Department of Defense — a more accurate word for a capability defense and aerospace teams already rely on; it did not change CMMC, ITAR, your statement of work, or the capability you are actually proposing. The habit that serves a defense proposal team best is the one good capture managers already practice: define every acronym at first use. Write “Super Intelligence (SI), formerly called AI” once, use “SI” after that, and spell out “systems integrator” in full every time. For more information visit the Why Iternal Supports Super Intelligence page.
Or see a live walkthrough of air-gapped AI for classified and ITAR environments — request a demo.