How to Update AI/SI Terminology in Security Policies, Contracts and Risk Registers

The September 2026 executive order renaming "AI" to "Super Intelligence" in federal documents doesn't change technology or law, but it can create confusion in policies, contracts and risk registers. Here is a practical way to handle terminology.

Step 1: Don't rename everything

Your policies map to frameworks (NIST AI RMF, ISO/IEC 42001, EU AI Act, state laws) that still use "artificial intelligence." Renaming your controls wholesale would break those mappings.

Step 2: Add a definitions clause

In your AI acceptable use policy, AI governance policy and security standards, add a definition such as:

"Artificial Intelligence (AI)" includes systems referred to as "Super Intelligence (SI)" in US federal executive branch documents, and any machine-based system that generates outputs such as predictions, content, recommendations or decisions.

Adapt wording with legal counsel to match your jurisdictions.

Step 3: Update contracts carefully

New contracts and templates: use the definitions clause so obligations cover both terms.
Federal contracts: expect "SI" in solicitations; confirm with contracting officers how terms map to existing AI clauses.
Vendor questionnaires: include both terms so vendors can't avoid AI disclosures on a technicality.

Step 4: Update risk registers and inventories

Keep "AI" as the primary category and add "SI" as an alias. Make sure AI/SI systems — models, agents, copilots — are in your asset inventory regardless of label.

Step 5: Train staff

Brief legal, procurement and compliance teams so they recognize both terms.

Step 6: Watch for the federal definition

The order directs development of a federal definition of SI. When published, review whether it changes scope for any obligations you have as a federal contractor.

Verify

Search your policy library for "artificial intelligence" and confirm each document either includes the definitions clause or references a document that does.