OFFSETOFFSET

Title 10 Structure: How Statute Organizes the Department of Defense

31 min read

Title 10 Structure: How Statute Organizes the Department of Defense

Every organization page on this platform sits somewhere in a structure that Congress wrote down. This page is the map. It explains what Title 10 of the United States Code actually says about who owns forces, who commands them, and who pays for them, and it gives the exact section for each proposition so a reader can check the work.

The organizing insight is simple and it is the reason the Department of Defense looks the way it does. Two different chains run from the same Secretary of Defense to the same soldiers, sailors, airmen, Marines and Guardians. One chain builds the force. The other chain uses it. Almost every confusing thing about the defense enterprise, including why a program office in Alabama answers to nobody in Tampa, resolves once you can see which chain you are standing in.

Read this before citing anything

Title 10 was renumbered. The John S. McCain National Defense Authorization Act for Fiscal Year 2019, Pub. L. 115-232, div. A, title VIII, § 808(a) (Aug. 13, 2018), moved the organizational provisions for the military departments into new section ranges. The change took effect February 1, 2019, per section 800 of that act.

SubjectPre-2019 citationCurrent citation
Secretary of the Army10 U.S.C. § 301310 U.S.C. § 7013
Secretary of the Navy10 U.S.C. § 501310 U.S.C. § 8013
Secretary of the Air Force10 U.S.C. § 801310 U.S.C. § 9013
Chief of Staff of the Army10 U.S.C. § 303410 U.S.C. § 7033
Chief of Naval Operations10 U.S.C. § 503310 U.S.C. § 8033
Commandant of the Marine Corps10 U.S.C. § 504310 U.S.C. § 8043
Chief of Staff of the Air Force10 U.S.C. § 803310 U.S.C. § 9033

Three traps follow from this, and they are worth internalizing.

First, the Army moved from the 3000-series to the 7000-series, the Navy occupies the 8000-series, and the Air Force occupies the 9000-series. Any source that cites § 3013 for the Secretary of the Army is describing the law as it stood before February 2019.

Second, and worse, a stale citation does not fail loudly. It quietly points somewhere else. Today 10 U.S.C. § 3013 is captioned “Technical data,” an acquisition definitions provision relocated from the old § 2302 by Pub. L. 116-283 and effective January 1, 2022. A reader who follows a stale Army citation lands on a definition of recorded technical information, not on a service secretary’s authority.

Third, and worst, the Air Force and Navy citations collide. The old § 8013 was the Secretary of the Air Force. The current § 8013 is the Secretary of the Navy. A pre-2019 Air Force citation now resolves to a real, valid, and completely wrong section. Nothing about the result looks broken. The collision is systematic rather than isolated, because the entire Air Force 8000-series shifted up into the 9000-series while the Navy 5000-series shifted into the vacated 8000-series. The same trap catches the Assistant Secretaries: old § 8016 was the Assistant Secretaries of the Air Force and is now § 9016, while § 8016 today is the Assistant Secretaries of the Navy.

The joint provisions in chapters 2, 4, 5 and 6 of subtitle A were not renumbered. Sections 111, 113, 131, 151 through 155, and 161 through 167 mean today what they meant in 1986.

1. The department and the Secretary

10 U.S.C. § 111 makes the Department of Defense an executive department and enumerates what it is composed of: the Office of the Secretary of Defense, the Joint Chiefs of Staff, the Joint_Staff, the Defense Agencies, Department of Defense Field Activities, the Departments of the Army, Navy and Air Force, the unified and specified combatant commands, and such other offices, agencies, activities and commands as may be established by law or by the President.

That list is the taxonomy this platform’s directory follows. It is not a chart somebody drew. It is a statute.

10 U.S.C. § 113 establishes the Secretary of Defense as the head of the department, appointed from civilian life. Subsection (b) is the load-bearing sentence: subject to the direction of the President, the Secretary “has authority, direction, and control over the Department of Defense.” That phrase, authority, direction and control, recurs throughout Title 10 and is the standard formula for full supervisory power. When a later section says an official acts “subject to the authority, direction, and control of the Secretary of Defense,” it is subordinating that official to § 113(b).

10 U.S.C. § 131 establishes the Office of the Secretary of Defense and names its statutory officials, including the Deputy Secretary, the Under Secretaries for Research and Engineering, Acquisition and Sustainment, Policy, Comptroller, Personnel and Readiness, and Intelligence and Security, along with the Director of Cost Assessment and Program Evaluation, the Director of Operational Test and Evaluation, the General Counsel, the Inspector General and the Chief Information Officer. 10 U.S.C. § 138 creates the Assistant Secretaries of Defense and specifies the duties of several of them by name.

OSD is a staff. It supervises, it sets policy, it allocates resources. It does not command.

2. The Chairman and the Joint Staff

10 U.S.C. § 151 composes the Joint Chiefs of Staff: the Chairman, the Vice Chairman, the Chief of Staff of the Army, the Chief of Naval Operations, the Chief of Staff of the Air Force, the Commandant of the Marine Corps, the Chief of the National Guard Bureau, and the Chief of Space Operations. Their statutory function is advice.

10 U.S.C. § 153 lists the Chairman’s functions, grouped by the statute into strategic direction, strategic and contingency planning, global military integration, comprehensive joint readiness, joint capability development, joint force development activities, and other matters. Everything in that catalog is advisory, integrative or supervisory. None of it is command.

10 U.S.C. § 155 establishes the Joint_Staff under the Chairman, to assist the Chairman and, subject to the Chairman’s authority, direction and control, the other members of the Joint Chiefs of Staff. The same section forecloses the historical worry that animated the 1947 debates: the Joint Staff “shall not operate or be organized as an overall Armed Forces General Staff and shall have no executive authority.”

The Chairman is not in the operational chain of command

This is the single most commonly misstated fact about the U.S. military, and three provisions establish it.

10 U.S.C. § 152(c) is the direct prohibition. The Chairman holds the grade of general or admiral and “outranks all other officers of the armed forces.” The next sentence takes the power back: “However, he may not exercise military command over the Joint Chiefs of Staff or any of the armed forces.” The Chairman is the senior officer in the United States military and commands nobody.

10 U.S.C. § 162(b) defines the chain exhaustively and leaves the Chairman out of it. See section 7 below.

10 U.S.C. § 163(a) explains why the Chairman nonetheless appears in every operational story. Subject to the limitations in § 152(c), the President may direct that communications between the President or the Secretary of Defense and the combatant commanders “be transmitted through the Chairman,” and may assign duties to the Chairman to assist the President and the Secretary in performing their command function. The Chairman is a conduit and an assistant, not a link. Orders pass through him. They do not originate with him.

10 U.S.C. § 163(b)(1) removes any remaining ambiguity. The Secretary may assign the Chairman responsibility for overseeing the activities of the combatant commands, but “[s]uch assignment by the Secretary to the Chairman does not confer any command authority on the Chairman and does not alter the responsibility of the commanders of the combatant commands prescribed in section 164(b)(2).”

Under § 163(b)(2) the Chairman serves as the spokesman for the combatant commanders, especially on their operational requirements, conferring with them, evaluating and integrating what he learns, advising the Secretary, and communicating combatant command requirements to the rest of the department. That is an enormous amount of influence over what gets built and funded. It is still not command.

3. The central distinction: organize, train and equip versus employ

Here is the spine of the whole page.

Military departments raise, train, equip and sustain forces. Combatant commanders command and employ them. A unit belongs to its service for its entire institutional life and answers to a combatant commander for the mission it is executing. Both relationships are real at the same time.

The organize, train and equip side

Three parallel sections, one per military department, carry identical structure. Each says the Secretary is responsible for and has the authority to conduct all affairs of the department, and then enumerates the same twelve functions.

DepartmentSecretaryComposition and functions
Army10 U.S.C. § 701310 U.S.C. § 7062
Navy10 U.S.C. § 801310 U.S.C. § 8062 (Navy), § 8063 (Marine Corps)
Air Force10 U.S.C. § 901310 U.S.C. § 9062 (Air Force), § 9081 (Space Force)

The enumerated list in § 7013(b), § 8013(b) and § 9013(b) is the statutory origin of the shorthand “organize, train and equip.” Each subsection (b) makes its Secretary responsible for:

  1. Recruiting
  2. Organizing
  3. Supplying
  4. Equipping, including research and development
  5. Training
  6. Servicing
  7. Mobilizing
  8. Demobilizing
  9. Administering, including the morale and welfare of personnel
  10. Maintaining
  11. The construction, outfitting and repair of military equipment
  12. The construction, maintenance and repair of buildings, structures and utilities, and the acquisition of real property

Read the list carefully and notice what is absent. There is no verb for fighting. No subsection authorizes the Secretary of the Army to conduct operations, order a movement, or select a target. The list is an industrial and institutional charter. It describes the business of producing military capability, not the business of using it.

The composition sections carry the mission language instead. 10 U.S.C. § 8062 provides that the Navy “shall be organized, trained, and equipped for the peacetime promotion of the national security interests and prosperity of the United States and for prompt and sustained combat incident to operations at sea.” 10 U.S.C. § 8063 requires the Marine Corps, within the Department of the Navy, to be organized to include not less than three combat divisions and three air wings, organized, trained and equipped to provide fleet marine forces of combined arms. 10 U.S.C. § 7062 states the intent of Congress to provide an Army capable, in conjunction with the other armed forces, of preserving the peace and security and providing for the defense of the United States. 10 U.S.C. § 9062 does the same for the Air Force. Even here the operative verb pair is “organized, trained, and equipped.” The employment authority lives elsewhere.

The Space Force sits inside the Department of the Air Force

10 U.S.C. § 9081 establishes “a United States Space Force as an armed force within the Department of the Air Force.” It is composed of the persons appointed, enlisted or conscripted into it and all Space Force units, organizations, installations and supporting elements, and it “shall be organized, trained, and equipped” to provide freedom of operation for the United States in, from and to space, to conduct space operations, and to protect the interests of the United States in space.

The placement matters and is frequently misdescribed. The Space Force is not a military department. There are still exactly three military departments under § 111(b), and the Secretary of the Air Force under § 9013 is the civilian responsible for the Space Force just as for the Air Force. The structural precedent is the Marine Corps, which is an armed force within the Department of the Navy under § 8063 while the Secretary of the Navy under § 8013 remains its Secretary.

10 U.S.C. § 9082 establishes the Chief of Space Operations, appointed from the general officers of the Space Force, and makes the Chief a member of the Joint Chiefs of Staff.

Service chiefs are on the building side, not the fighting side

10 U.S.C. § 7033 (Chief of Staff of the Army), § 8033 (Chief of Naval Operations), § 8043 (Commandant of the Marine Corps), § 9033 (Chief of Staff of the Air Force) and § 9082 (Chief of Space Operations) establish the uniformed service heads. Each performs duties under the authority, direction and control of the service Secretary and is directly responsible to that Secretary. Section 7033(d)(4) is characteristic: the Chief of Staff exercises supervision over Army members and organizations “consistent with the authority assigned to commanders of unified or specified combatant commands under chapter 6 of this title.”

That clause is the seam. The service chief supervises the institution up to the point where a combatant commander’s authority begins, and no further. Service chiefs do not command forces in operations. That was one of the deliberate results of the Goldwater_Nichols_Act.

The employ side

10 U.S.C. § 164(c)(1) is where the fighting verbs finally appear. Unless otherwise directed by the President or the Secretary of Defense, a combatant commander’s authority, direction and control over assigned commands and forces includes the command functions of:

  • (A) giving authoritative direction to subordinate commands and forces necessary to carry out assigned missions, including authoritative direction over all aspects of military operations, joint training and logistics
  • (B) prescribing the chain of command to the commands and forces within the command
  • (C) organizing commands and forces within that command as he considers necessary
  • (D) employing forces within that command as he considers necessary
  • (E) assigning command functions to subordinate commanders
  • (F) coordinating and approving those aspects of administration and support, including control of resources and equipment, internal organization and training, and discipline necessary to carry out assigned missions
  • (G) exercising authority over selection of subordinate commanders and combatant command staff, suspension of subordinates, and convening of courts-martial, as provided in § 164(e), (f) and (g) and § 822(a)

Compare § 164(c)(1)(D), “employing forces,” against the twelve items in § 7013(b). The two lists do not overlap. That is the distinction, drawn by Congress, in the text.

One usage note. The doctrinal acronym COCOM, expanded as “combatant command (command authority),” comes from joint doctrine rather than from the statute. Title 10 captions § 164(c) simply as “Command Authority of Combatant Commanders.” Joint doctrine adds that COCOM is nontransferable and may be exercised only by combatant commanders; the statute reaches the same result functionally through § 164(c)‘s opening clause and § 162(a)(3)‘s restriction on transferring assigned forces.

4. Combatant commands

Establishment. 10 U.S.C. § 161(a). With the advice and assistance of the Chairman, the President, through the Secretary of Defense, shall establish unified and specified combatant commands to perform military missions and prescribe the force structure of those commands. Section 161(b) requires the Chairman to review the missions, responsibilities including geographic boundaries, and force structure of each command not less often than every two years and to recommend changes to the President through the Secretary. The instrument that carries this out is the Unified_Command_Plan.

Assignment of forces. 10 U.S.C. § 162(a). As directed by the Secretary of Defense, the Secretaries of the military departments shall assign specified forces under their jurisdiction to the combatant commands. Four rules follow:

  • § 162(a)(1) places the assignment duty on the service Secretaries and requires the Secretary of Defense to keep assignments consistent with the President’s prescribed force structure.
  • § 162(a)(2) provides that a force not assigned to a combatant command “shall remain assigned to the military department concerned” for carrying out that Secretary’s responsibilities “as specified in section 7013, 8013, or 9013.” This is the statute expressly naming the two sides of the distinction in a single sentence.
  • § 162(a)(3) allows transfer of an assigned force only by authority of the Secretary of Defense and under procedures prescribed by the Secretary and approved by the President.
  • § 162(a)(4) places all forces assigned to a unified combatant command under the command of that commander.

Command authority. 10 U.S.C. § 164. Subsection (a) governs assignment of the commander, generally requiring joint specialty certification under § 661 and a completed joint tour as a general or flag officer, waivable in the national interest. Subsection (b) makes the commander responsible to the President and to the Secretary of Defense for the assigned missions and for the preparedness of the command. Subsection (c) confers the command functions listed above. Subsection (d)(1) places commanders of commands and forces assigned to a combatant command under the authority, direction and control of, and responsible to, the combatant commander on all matters for which the combatant commander holds § 164(c) authority.

Administration and support. 10 U.S.C. § 165. This is the section that makes the two-chain design work in practice.

  • § 165(a) directs the Secretary of Defense, with the advice and assistance of the Chairman, to provide for the administration and support of forces assigned to each combatant command.
  • § 165(b) makes the Secretary of a military department responsible for the administration and support of forces he has assigned to a combatant command, subject to the authority, direction and control of the Secretary of Defense and subject to the combatant commander’s § 164(c) authority.
  • § 165(c) lets the Secretary of Defense reassign all or part of that responsibility to other components of the department, including Defense Agencies and combatant commands themselves, after consulting the service Secretaries.

Section 165(b) is the answer to the practical question of who pays, who mans and who fixes. A carrier strike group under a geographic combatant commander is still crewed, maintained, funded and personnel-managed by the Department of the Navy. Assignment moves command, not ownership.

Funding. 10 U.S.C. § 166 requires a separate budget proposal for combatant command activities in the annual defense budget, covering joint exercises, force training, contingencies and selected operations as the Secretary determines in consultation with the Chairman. Combatant commands are commanders, not buyers. With one exception.

5. The exception: USSOCOM

10 U.S.C. § 167 establishes a unified combatant command for special operations forces. Under § 167(a) the President, through the Secretary of Defense and with the advice and assistance of the Chairman, shall establish it under § 161, and “[t]he principal function of the command is to prepare special operations forces to carry out assigned missions.”

Read that function statement against § 161 and § 164. Every other combatant command exists to employ forces. USSOCOM exists, by statute, to prepare them. That single sentence is why the command holds authorities no other combatant command holds.

Assignment. § 167(b) assigns all active and reserve special operations forces stationed in the United States to the command unless the Secretary of Defense directs otherwise. Other combatant commands receive forces from the services; USSOCOM receives them by operation of the statute.

Command of the mission. § 167(d) provides that a special operations activity or mission is conducted under the command of the geographic combatant commander in whose area it is conducted, unless the President or the Secretary of Defense directs otherwise, with the SOCOM commander able to exercise command when so directed. USSOCOM builds the force. A geographic commander normally fights it.

Service-like authorities. § 167(e) makes the commander responsible for, among other things, developing strategy, doctrine and tactics, training assigned forces, conducting specialized courses of instruction, validating requirements, establishing priorities, ensuring interoperability of equipment and forces, formulating intelligence requirements, and monitoring the promotions, assignments, retention, training and professional military education of special operations personnel. Compare that catalog against the twelve items in § 7013(b). The overlap is the point.

Acquisition. § 167(e)(4) is the provision that makes USSOCOM operationally distinct from every other combatant command:

  • (A) The commander is responsible for and has the authority to conduct development and acquisition of special operations-peculiar equipment and acquisition of special operations-peculiar material, supplies and services.
  • (B) In carrying out that function, the commander has “authority to exercise the functions of the head of an agency under chapter 137 of this title.” Chapter 137 is the legacy procurement chapter. Head of agency status is what lets an organization contract in its own name.
  • (C)(i) The commander’s staff “shall include a command acquisition executive,” responsible for overall supervision of acquisition matters for the command, with authority to negotiate memoranda of agreement with the military departments, supervise acquisitions whether performed by the command or by a department under delegation, represent the command with the departments on programs where the command is the customer, and ensure command representation in joint working groups and integrated product teams.
  • (C)(ii) The command acquisition executive is responsible for rapidly delivering acquisition solutions to meet validated special operations-peculiar requirements, is “subordinate to the Defense Acquisition Executive in matters of acquisition,” is “subject to the same oversight as the service acquisition executives,” and is included on the distribution list for departmental acquisition directives and instructions.
  • (D) The commander’s staff shall include an inspector general to audit and inspect purchasing and contracting.

The phrase “subject to the same oversight as the service acquisition executives” is the statutory basis for treating the head of SOF AT&L as a peer of the Army, Navy and Air Force acquisition executives. See SOF_AT_L.

Budget. § 167(g) provides that in addition to activities for which funding may be requested under § 166(b), the SOCOM budget proposal “shall include requests for funding for (1) development and acquisition of special operations-peculiar equipment; and (2) acquisition of other material, supplies, or services that are peculiar to special operations activities.” Under § 167(e) the commander also submits program recommendations and budget proposals and exercises authority over the expenditure of funds for forces assigned to the command.

Major Force Program 11. MFP-11 is the dedicated program category for special operations forces in the Future Years Defense Program. State this precisely, because it is often cited loosely: MFP-11 is not a Title 10 term. It is a Department of Defense budget construct created to implement the Nunn-Cohen Amendment, Pub. L. 99-661, div. A, title XIII (Nov. 14, 1986), the same legislation that added § 167 to Title 10. The codified requirement that survives in the U.S. Code is § 167(g). When you need a statutory citation for SOCOM’s budget authority, cite § 167(g) and § 167(e), and describe MFP-11 as the FYDP program element structure through which those requirements are executed.

Administrative chain. § 167(f) creates a second administrative chain that exists nowhere else in Title 10. Unless otherwise directed by the President, it runs from the President, to the Secretary of Defense, to the Assistant Secretary of Defense for Special Operations and Low Intensity Conflict, to the SOCOM commander. Section 167(f)(2) defines what travels down that chain: special operations-peculiar administration and support, including readiness and organization of special operations forces, resources, equipment and civilian personnel. It expressly does not include operational matters, which remain in the combatant commanders’ operational chain, and does not include matters that are not special operations-peculiar, which remain the purview of the armed forces.

10 U.S.C. § 138(b)(2)(A) builds the civilian half. The Assistant Secretary of Defense for Special Operations and Low Intensity Conflict has as a principal duty the overall supervision, including oversight of policy and resources, of special operations activities as defined in § 167(k) and low intensity conflict activities, and under clause (i) shall “[e]xercise authority, direction, and control of all special-operations peculiar administrative matters relating to the organization, training, and equipping of special operations forces through the administrative chain of command specified in section 167(f).” Under § 138(b)(2)(B), in discharging that responsibility the Assistant Secretary “is immediately subordinate to the Secretary of Defense,” and unless the President directs otherwise “no officer below the Secretary may intervene to exercise authority, direction, or control over the Assistant Secretary.”

That is the sentence that makes the analogy to a service secretary defensible. The statutory formula for a service Secretary in § 7013(b) is responsibility for organizing, training and equipping. The statutory formula for ASD SO/LIC in § 138(b)(2)(A)(i) is authority, direction and control over administrative matters relating to the organization, training and equipping of special operations forces, exercised immediately subordinate to the Secretary of Defense. Congress deliberately used the same vocabulary.

What it means practically. USSOCOM is a combatant command that also functions as a small military department for its own peculiar needs. It fields its own requirements process, runs its own program executive structure under a command acquisition executive with service-acquisition-executive-equivalent oversight, defends its own budget line in MFP-11, and reports administratively to a civilian assistant secretary who cannot be overruled by anyone below the Secretary of Defense. When a vendor sells to SOCOM it is selling to a buyer, not to a user who must go ask a service to buy on its behalf. When SOCOM funds a capability the money does not transit an Army or Navy program office. Everything not special operations-peculiar, meaning the service-common platforms, base pay, initial entry training and most infrastructure, still comes from the parent services under § 165(b). The recurring fight is over where the line between peculiar and common falls.

Other definitions in § 167: subsection (j) identifies which forces are special operations forces, subsection (k) lists the special operations activities, and subsection (h) makes clear the section does not authorize intelligence activities requiring notice to the congressional intelligence committees.

6. Defense agencies, field activities and combat support agencies

Establishment. 10 U.S.C. § 191 authorizes the Secretary of Defense to establish a single agency to perform a supply or service activity common to more than one military department whenever the Secretary determines that it would be more effective, economical or efficient to do so. Under § 191(b), any such agency “shall be designated as a Defense Agency or a Department of Defense Field Activity.”

The distinction between the two labels is one of scale and scope rather than of legal kind. Both are creatures of the same section and both appear separately in the § 111(b) list of what composes the department. Neither is a military department, and neither commands forces.

Supervision. 10 U.S.C. § 192 is captioned “Defense Agencies and Department of Defense Field Activities: oversight by the Secretary of Defense.” Under § 192(a)(1) the Secretary shall assign responsibility for the overall supervision of each Defense Agency and DoD Field Activity designated under § 191(b) to a civilian officer within the Office of the Secretary of Defense or to the Chairman of the Joint Chiefs of Staff. Under § 192(a)(2) the responsible official must keep the Secretary informed on how the agency’s program recommendations and budget proposals conform to the requirements of the military departments and the combatant commands. Section 192(a)(3) exempts the Defense Intelligence Agency and the National Security Agency from that assignment requirement.

This is why every Defense Agency page on this platform should identify its OSD principal staff assistant. That relationship is not organizational preference. It is § 192(a)(1).

Combat support agencies. 10 U.S.C. § 193 is a separate and stricter regime, captioned “Combat support agencies: oversight.” A combat support agency is a Defense Agency that supports operating forces, and it therefore answers to the Chairman on readiness in a way ordinary Defense Agencies do not. Section 193 requires the Chairman to report to the Secretary not less often than every two years on the responsiveness and readiness of each such agency to support operating forces, and to develop a uniform readiness reporting system for them.

§ 193(f) defines the term by enumeration. A combat support agency is any of the following Defense Agencies:

  1. The Defense Information Systems Agency
  2. The Defense Intelligence Agency
  3. The Defense Logistics Agency
  4. The National Geospatial-Intelligence Agency
  5. Any other Defense Agency designated as a combat support agency by the Secretary of Defense

Paragraph (5) is why the practical list is longer than the statutory four. The Defense Threat Reduction Agency, the Defense Contract Management Agency, the National Security Agency and others carry the designation by secretarial action rather than by enumeration in § 193(f). For NSA and NGA, the § 193 requirements apply only with respect to the combat support functions they perform for the Department of Defense, with policies established in consultation with the Director of National Intelligence.

So a defense agency page needs two facts, not one: its § 192 supervisory relationship, and whether it carries the § 193 combat support designation. Those are different questions with different answers.

National Guard Bureau. 10 U.S.C. § 10501(a) provides that there is in the Department of Defense a National Guard Bureau “which is a joint activity of the Department of Defense.” It is neither a Defense Agency nor a military department, and it gets its own statutory category.

7. The operational chain of command

10 U.S.C. § 162(b) states it completely:

Unless otherwise directed by the President, the chain of command to a unified or specified combatant command runs (1) from the President to the Secretary of Defense; and (2) from the Secretary of Defense to the commander of the combatant command.

Two links. That is the entire operational chain.

Note what Congress did not include. Not the Chairman of the Joint Chiefs of Staff, who is barred from military command by § 152(c) and reduced to a communications conduit by § 163(a). Not the service Secretaries, whose § 7013, § 8013 and § 9013 responsibilities are administrative and whose forces, once assigned under § 162(a), pass under the combatant commander’s command by § 162(a)(4). Not the service chiefs, whose supervision under § 7033(d)(4) and its counterparts is expressly bounded by combatant commander authority. Not the Under Secretaries or Assistant Secretaries of Defense, who staff the Secretary under § 131 and § 138.

Below the combatant commander the chain continues by § 164(c)(1)(B), which lets the commander prescribe the chain of command within his own command, and § 164(d)(1), which places subordinate commanders under his authority, direction and control. That is where subordinate unified commands, joint task forces and service component commands attach.

The two chains, drawn

flowchart TB
    P["PRESIDENT<br/>Commander in Chief"]
    SD["SECRETARY OF DEFENSE<br/>10 U.S.C. § 113(b)<br/>authority, direction and control"]
    P --> SD

    CJCS["CHAIRMAN, JOINT CHIEFS OF STAFF<br/>§ 152(c): may not exercise military command<br/>§ 163(a): communications may transit the Chairman<br/>§ 155: Joint Staff, no executive authority"]
    SD -.->|"advice and integration, NOT command"| CJCS

    subgraph ADMIN["ADMINISTRATIVE CHAIN: organize, train, equip, sustain"]
        direction TB
        SECARMY["Secretary of the Army<br/>§ 7013(b)"]
        SECNAV["Secretary of the Navy<br/>§ 8013(b)"]
        SECAF["Secretary of the Air Force<br/>§ 9013(b)"]
        CSA["Chief of Staff, Army<br/>§ 7033"]
        CNO["Chief of Naval Operations<br/>§ 8033"]
        CMC["Commandant, Marine Corps<br/>§ 8043"]
        CSAF["Chief of Staff, Air Force<br/>§ 9033"]
        CSO["Chief of Space Operations<br/>§ 9082"]
        SECARMY --> CSA
        SECNAV --> CNO
        SECNAV --> CMC
        SECAF --> CSAF
        SECAF --> CSO
    end

    subgraph OPS["OPERATIONAL CHAIN: command and employ"]
        direction TB
        CCDR["COMBATANT COMMANDERS<br/>§ 161 establishment<br/>§ 164(c) command authority"]
        SUBORD["Subordinate unified commands,<br/>joint task forces,<br/>service component commands<br/>§ 164(c)(1)(B)-(C), § 164(d)(1)"]
        CCDR --> SUBORD
    end

    SD -->|"§ 111(b): military departments"| SECARMY
    SD --> SECNAV
    SD --> SECAF
    SD ==>|"§ 162(b): THE CHAIN OF COMMAND"| CCDR

    FORCES["ASSIGNED FORCES<br/>the same units, standing in both chains at once<br/>manned, trained, equipped and sustained<br/>by the parent department under § 165(b)<br/>commanded and employed<br/>by the combatant commander under § 164(c)"]

    CSA --> FORCES
    CNO --> FORCES
    CMC --> FORCES
    CSAF --> FORCES
    CSO --> FORCES
    SUBORD --> FORCES

    SECARMY -.->|"§ 162(a)(1): assign forces"| CCDR
    SECNAV -.-> CCDR
    SECAF -.-> CCDR

    classDef adminNode fill:#e8f0f8,stroke:#2c5282,color:#1a202c
    classDef opsNode fill:#f8ece8,stroke:#9b2c2c,color:#1a202c
    classDef topNode fill:#f0f0f0,stroke:#333,color:#1a202c
    classDef joinNode fill:#f5f0e0,stroke:#744210,color:#1a202c
    class SECARMY,SECNAV,SECAF,CSA,CNO,CMC,CSAF,CSO adminNode
    class CCDR,SUBORD opsNode
    class P,SD,CJCS topNode
    class FORCES joinNode

Where they diverge. At the Secretary of Defense. Section 113(b) gives one civilian authority, direction and control over everything, and then the statute forks. Section 111(b) and the § 7013, § 8013, § 9013 triad send one branch down through the military departments. Section 162(b) sends the other branch straight to the combatant commander, skipping every intermediate headquarters.

Where they rejoin. At the unit. Section 162(a)(1) is the hinge: the service Secretaries assign forces to combatant commands as the Secretary of Defense directs. From the moment of assignment the unit has two masters and both are lawful. Section 164(c) gives the combatant commander command. Section 165(b) leaves the parent department responsible for administration and support, expressly subject to that commander’s § 164(c) authority. Section 162(a)(2) confirms the default: anything not assigned stays with the department for its § 7013, § 8013 or § 9013 purposes.

Where the Chairman sits. Beside both chains, in neither. The dotted line is the whole point.

Mapping platform organization types to statute

Organization typePrimary statutory basisWhat the statute doesPractitioner note
Department of Defense10 U.S.C. § 111Makes DoD an executive department and enumerates its components§ 111(b) is the canonical taxonomy for this directory
Office of the Secretary of Defense10 U.S.C. §§ 131, 138Establishes OSD and names its statutory officialsStaff, not a command. Supervises under § 113(b)
Military department (Army, Navy, Air Force)10 U.S.C. §§ 111(b)(6)-(8); Secretaries at §§ 7013, 8013, 9013; composition at §§ 7062, 8062, 9062Establishes the department and its Secretary’s twelve enumerated responsibilitiesThere are exactly three. Verify post-2019 numbering before citing
Armed force within a department (Marine Corps, Space Force)Marine Corps 10 U.S.C. § 8063; Space Force 10 U.S.C. § 9081Establishes the service inside its parent departmentNot a military department. Parent Secretary retains § 8013 or § 9013 authority
Service headquarters staff10 U.S.C. §§ 7033, 8033, 8043, 9033, 9082Establishes the uniformed service chief under the service SecretarySupervision bounded by combatant commander authority, e.g. § 7033(d)(4)
Combatant command10 U.S.C. §§ 161, 162, 164, 165, 166Establishment, assignment of forces, command authority, administration and support, budget§ 164(c) is the authority. § 165(b) is why the services still pay
USSOCOM10 U.S.C. § 167; civilian oversight at § 138(b)(2)Establishes the command and grants service-like organize, train, equip and acquisition authoritiesOnly combatant command with head of agency status under § 167(e)(4)(B) and a statutory command acquisition executive under § 167(e)(4)(C)
Service component commandNo direct establishing section. Derived from 10 U.S.C. §§ 162(a), 164(c)(1)(B)-(C), 164(d)(1), 165(b)Combatant commander organizes and prescribes the internal chain; parent department retains administration and support”Service component command” is joint doctrine vocabulary, not a Title 10 term. Cite the derivation, not a phantom section
Defense agency10 U.S.C. §§ 111(b)(4), 191, 192Establishment by the Secretary for common supply or service activities; OSD supervision assigned under § 192(a)(1)Every agency page should name its § 192 supervising OSD official
DoD field activity10 U.S.C. §§ 111(b)(5), 191(b), 192Same establishing authority and same supervision regime as a Defense AgencyDistinguished from a Defense Agency by scope, not by legal kind
Combat support agency10 U.S.C. § 193, definition at § 193(f)Chairman reviews readiness and responsiveness to operating forces at least every two yearsA status layered on top of Defense Agency status, not a substitute for it. Four named plus secretarial designations
Joint Staff10 U.S.C. § 155Establishes the Joint_Staff under the ChairmanExpressly barred from operating as an Armed Forces General Staff and has no executive authority
National Guard Bureau10 U.S.C. § 10501Establishes NGB as a joint activity of the Department of DefenseIts own statutory category. Chief is a member of the JCS under § 151
Direct reporting unit, field operating agency, major command, field commandNo Title 10 provision. Created under the service Secretary’s organizing authority at 10 U.S.C. §§ 7013(b)(2), 8013(b)(2), 9013(b)(2)Service regulation defines the construct, e.g. AFI 38-101 for Air Force and Space Force organization, AR 10-87 for Army commandsCite the service Secretary’s organize authority plus the implementing service instruction. Do not invent a section
Program executive officeNo section establishes an individual PEO. Nearest anchors: 10 U.S.C. § 1732 (portfolio acquisition executive), § 1737 (definitions); service acquisition official positions at §§ 7016(b)(5)(A), 8016(b)(4)(A), 9016(b)(4)PEOs are established by the service acquisition executive under the Secretary’s § 7013(b), § 8013(b) or § 9013(b) organize authority and DoD acquisition policyTerminology is in transition. Pub. L. 119-60 § 1802(b)(1) substituted “portfolio acquisition executive” for “program executive officer” in chapter 87 and added § 1732. Date any PEO citation and check § 1732

Citation hygiene

This platform cites statute in the form 10 U.S.C. § 164, with the section symbol, and ranges as 10 U.S.C. §§ 161-165. Subsections follow in parentheses without a space: 10 U.S.C. § 164(c)(1)(D).

Three rules keep the citations trustworthy.

Check the source date. Any document written before February 1, 2019 that cites a military department organizational provision is presumptively stale. Doctrine publications, CRS reports, service regulations, contract clauses and academic articles all carry this problem. The renumbering was mechanical and complete, so a stale cite is almost always a live section number pointing at the wrong subject.

Verify against the primary source. The Office of the Law Revision Counsel publishes the current code at uscode.house.gov, and Cornell’s Legal Information Institute mirrors it at law.cornell.edu. Both display the source credit, which shows the prior section number and the public law that moved it. Reading the source credit is the fastest way to confirm you are on the right section.

Do not manufacture a citation for a doctrinal concept. Service component command, COCOM as an acronym, direct reporting unit and Major Force Program 11 are all real and all consequential, and none of them is a Title 10 term. Cite the statutory provisions from which each derives, and identify the doctrine or regulation that supplies the vocabulary. A precise “derived from” is worth more than a confident wrong section.

See also

Title_10_USC | Goldwater_Nichols_Act | Unified_Command_Plan | USSOCOM | Joint_Staff | SOF_AT_L | Defense_Acquisition_System | PPBE_Process | Congressional_Budget_Process | DOTMLPF-P | JCIDS

Every section number on this page was verified against uscode.house.gov and law.cornell.edu on 2026-08-02. When you extend this page, verify before you add.

Graph View

Backlinks