The bill replaces every occurrence of “Department of Defense” in the United States Code with “Department of War” and similarly renames the “Secretary of Defense” the “Secretary of War.” It directs that existing laws, rules, regulations, and official papers that refer to the Department of Defense should be read as referring to the Department of War, and it authorizes subordinate officials to use corresponding secondary titles (for example, Deputy Secretary of War). Implementation is explicitly subject to applicable law and the availability of appropriations.
On its face the measure is purely nominal: it does not add or subtract statutory authorities, alter chains of command, or reallocate funds. In practice, swapping names at the scale of the federal government touches statutes, contracts, seals, forms, procurement systems, international agreements, and court dockets.
That creates a mix of symbolic, legal, and administrative questions that will matter to counsel, agency officials, contractors, and partners abroad.
At a Glance
What It Does
The bill amends federal law to substitute the phrase “Department of War” for “Department of Defense” throughout the United States Code and to substitute “Secretary of War” for “Secretary of Defense.” It directs existing statutory and administrative references to be treated as referring to the new name and permits subordinate officials to adopt corresponding secondary titles.
Who It Affects
Directly affected entities include the Department itself (its offices, components, and personnel), federal agencies and statutes that reference the Department of Defense, defense contractors and grant recipients whose contracts reference the agency, and courts that interpret or apply statutes using the old name.
Why It Matters
Changing the official name is primarily symbolic but legally consequential: it creates a cascade of required updates across statutes, regulations, contracts, and agency records, raises questions about interpretation of existing laws and treaties, and signals a policy posture that could affect diplomatic and deterrence messaging.
More articles like this one.
A weekly email with all the latest developments on this topic.
What This Bill Actually Does
The bill is short and focused: it instructs Congress’s codified law to use a new name for a major executive department and to treat all existing references to the old name as references to that new name. That substitution applies across statutes and, by an explicit references clause, across rules, regulations, certificates, directives, instructions, and “other official paper” in force on the date of enactment.
The text also contemplates corresponding secondary titles for subordinate officials and declares that statutory references remain controlling until Congress changes them.
Because the bill changes only language on the page and leaves substantive authorities untouched, it does not directly rewrite authorities for force employment, procurement, or military organization. But federal implementation cannot be purely cosmetic: agency regulations, Executive Branch directives, appropriation language, procurement systems, grant instruments, employee records, security clearances, and statutory citations in ongoing litigation will need review to ensure consistency.
The bill’s instruction that references be read to mean the new name is intended to prevent immediate legal discontinuities, but it does not erase ambiguity about whether specific implementing documents require formal amendment.Practically, the Department would need a project plan to update agency identifiers (statutes, CFR citations, Federal Register entries), IT systems (contracting codes, SF forms, payment systems), publicly visible items (seals, signage, websites), and international communications (treaty party notices, NATO references). The clause conditioning implementation on the availability of appropriations gives the Department and OMB a leverage point: many of these changes carry measurable costs and will likely be phased or deferred pending funding decisions.Finally, the bill’s findings and “sense of Congress” language tie the renaming to policy messaging — a deliberate rhetorical shift toward “peace through strength.” That framing matters because renaming a department is a visible signal that can affect diplomacy and domestic politics even if it leaves statutory authority unchanged.
The Five Things You Need to Know
The bill directs a text‑level substitution: every statutory instance of “Department of Defense” becomes “Department of War.”, It similarly replaces “Secretary of Defense” with “Secretary of War” across federal law.
Any existing law, rule, regulation, certificate, directive, instruction, or other official paper that refers to the Department of Defense is declared to refer to the Department of War on the date of enactment.
Subordinate officials may use corresponding secondary titles (for example, Deputy Secretary of War), and statutory references stay controlling until Congress amends them.
Implementation is subject to applicable law and the availability of appropriations — the bill contains no dedicated funding for the renaming.
Section-by-Section Breakdown
Every bill we cover gets an analysis of its key sections.
Short title
This is the bill’s caption: the "Peace Through Strength Act of 2025." The short title signals the sponsor’s intent to tie the nomenclature change to a policy posture, which helps explain the legislative findings and sense language that follow.
Congressional findings
The findings recite historical precedent (the original Department of War created in 1789) and argue that the older name better communicates resolve. These findings are rhetorical and do not create legal obligations, but they provide legislative context that courts or agencies might cite if questions of statutory purpose arise during interpretation.
Sense of Congress on naming and posture
This subsection states Congress's view that the name “Department of War” promotes ‘peace through strength’ and sharpens focus on national interest. A sense clause carries no binding legal effect but makes the sponsor’s policy rationale explicit for executive branch officials, foreign governments, and the public.
Statutory substitution and reference treatment
The core operative text amends the United States Code by replacing the phrases “Department of Defense” and “Secretary of Defense” with “Department of War” and “Secretary of War.” It then declares that references to the old names in law, regulation, or other official papers shall be considered to refer to the new names, and it permits subordinate officials to use corresponding titles. This approach aims to minimize immediate legal disruption but raises technical questions about whether particular documents require formal amendment or can rely on a blanket substitution.
Statutory reference supremacy and implementation condition
The bill specifies that existing statutory references remain controlling until Congress changes them and then adds an implementation proviso conditioning changes on applicable law and availability of appropriations. That language preserves legislative primacy over substantive statutory language but also gives the Executive Branch an administrative discretion point as to pace and scope of reforms, largely driven by funding and regulatory update processes.
This bill is one of many.
Codify tracks hundreds of bills on Defense across all five countries.
Explore Defense in Codify Search →Who Benefits and Who Bears the Cost
Every bill creates winners and losers. Here's who stands to gain and who bears the cost.
Who Benefits
- Political proponents and messaging allies — Elected officials and advocacy groups favoring a tougher posture gain a concrete, high‑visibility policy win that aligns symbolism with their message.
- Historical or traditionalist organizations — Groups that prioritize historical nomenclature and ceremonial continuity obtain a statutory restoration of an older departmental name.
- Certain defense leadership seeking clear rhetorical posture — Senior officials who prefer unambiguous, aggressive deterrence signaling can use the new title in public diplomacy and internal branding to reinforce a particular institutional identity.
Who Bears the Cost
- Department of Defense (administration) — The Department itself will shoulder planning, legal review, and operational costs to update statutes, regulations, seals, signage, IT systems, and personnel records, absent dedicated funding.
- Federal agencies and statutory users — Any agency, inspector, or program that cites the Department of Defense in statutes, regulations, guidance, or interagency agreements will need to review and possibly amend documents to avoid inconsistency or litigation risk.
- Contractors and grant recipients — Companies and institutions with long‑running contracts, grants, or subawards that reference the Department must evaluate whether contract amendments, novations, or administrative changes are necessary.
- Courts and litigants — Ongoing litigation that cites statutes or agency actions referencing the Department of Defense may face interpretive disputes about whether the renaming affects rights, duties, or procedural posture.
- Congress and oversight committees — Lawmakers will likely need to consider and, in many cases, act to clean up statutory cross‑references, an unbudgeted drafting burden on congressional staff and committees.
Key Issues
The Core Tension
The central tension is between symbolic policy signaling and functional governance: renaming the department advances a clear rhetorical posture intended to strengthen deterrence messaging, but doing so at scale risks legal ambiguity, administrative cost, and operational friction — a trade‑off between message and machinery that no statute can fully reconcile.
The most immediate implementation tension is legal clarity versus administrative practicality. The bill attempts to prevent legal discontinuity by declaring that all existing references to the Department of Defense mean the Department of War, but that blanket rule does not eliminate gray areas.
Statutes that incorporate by reference specific ‘‘Secretary of Defense’’ authorities, appropriations bills that name funding accounts, international agreements in which the Department is a designated party, and court decrees tied to the old names could all require tailored legal analysis or amendment.
Cost and sequencing are unresolved. The bill conditions execution on availability of appropriations but provides no estimate or authorization of funds.
Agencies will therefore face choices about whether to implement piecemeal (update public‑facing materials first) or to undertake a comprehensive, funded transition. Both approaches carry risks: partial changes can create inconsistency across databases and documents; a full rebrand without budget authority could strain OMB priorities and impede other programs.
Finally, the renaming is primarily symbolic and may affect diplomatic, alliance, and adversary perceptions in ways that are hard to measure; those diplomatic effects could have downstream operational consequences even though the bill leaves authorities unchanged.
Try it yourself.
Ask a question in plain English, or pick a topic below. Results in seconds.