At a glance
Possible toolACQ-44 · Other statutory tools
Authority holder: Secretary of Defense; Service/component acquisition decision officials
Other statutory tools
Mechanism tags describe the source text; they do not expand the authority.
Availability and verificationExpress statutory pathway; award-specific appropriations, available balances, delegations, implementation and approvals not independently verified.
Program process and intake
Checked 2026-10-04 · process documented. Program evidence is separate from legal authority, available funds and transaction approval.
Software pathway planning has concrete documents and user commitments; current oversight shows that nominal pathway adoption does not guarantee effective user engagement.
Software Acquisition Pathway planning and execution
- Who this route serves
- Government software programs and selected development partners
- Administering office / routing lead
- Program decision authority, program manager, operational sponsor and contracting activity
Related processThe April 2026 DoD engineering guide explicitly implements planning under DoDI 5000.87, the software acquisition pathway associated with section 3603. It does not establish a particular contract award under that section.
What this evidence label means Current process documented; newer policy identifiedThe April 2026 guidance remains a documented process source. WHS also lists instruction 8430.01, Accelerated Mission Software, dated September 8, 2026. Its full text was inaccessible, so its detailed interaction with DoDI 5000.87 was not verified.
Status reference date: 2026-10-04 · research checked 2026-10-04
WHS recently published issuances · September 8, 2026 DoWI8430.01 Accelerated Mission Softwareofficial issuance index · Evidence record Program eligibility
Steps and preparation
Prepare capability needs statement, acquisition strategy, test/evaluation strategy, user agreement and value assessment before execution; maintain iterative development and evaluation.
Software R&M engineering guidance addendum · Section 1.2.1 planning phase and 1.2.2 execution; source note 2 to DoDI 5000.87official engineering guidance · Evidence record
Funding, limits and authority relationship
Software pathway document requirements → (Access restricted)
published guidance: Program planning guidance; contracting/OT/CSO selection and funding remain separate decisions.
Source access and verification notes
Research scope and sources checked
Read indexed primary April 2026 engineering guidance and pathway document table, current WHS publication status, and the specific GAO NI2 finding. The new8430.01 PDF returned403; no unsupported new cybersecurity mandates or transaction ties were inferred.
What remains unverified
- September 2026 instruction full text, program-specific decision memorandum, appropriations and contract instrument require separate verification.
A dated source check is not continuing monitoring. Recheck the linked official notice before preparing a submission. Browse program research →
Funding conditions
- Appropriate software/hardware lifecycle funds; correct contracting instrument and sustained operations budget still needed.
Read the funding and execution guide
Who contributes what
Need & planning
- Operational requirement owner; Service/component portfolio acquisition executive and program manager
Resources
- Sponsoring Service/component appropriations manager and comptroller
Approval
- Service/component acquisition executive and authorized contracting authority, at applicable threshold
Partners & review
- User command
- Counsel, fiscal, engineering, testing, logistics and security staff as applicable
Office links are editorial matches to the original role text, not verified delegations. Composite labels and unmatched actors are preserved.
Coordination pathwayUser/program team → software acquisition decision → contracting/software engineering/test/security → frequent evaluated delivery.
Actor and execution-role sources
What this research establishes
Legal basisSources linkedLegal sources and instrument limits are recorded.
RequirementsGates recordedRead the requirements for this instrument; applicability depends on the proposed action.
Public fundingRules recordedAppropriate software/hardware lifecycle funds; correct contracting instrument and sustained operations budget still needed. Office budget figures are separate institutional context, not an allocation to this instrument. Assigned rolesRoles recordedPublic sources describe institutional authority. The instrument identifies approval and execution roles; a specific signature remains transaction-dependent. EngagementRelated evidenceSoftware pathway planning has concrete documents and user commitments; current oversight shows that nominal pathway adoption does not guarantee effective user engagement. Program check: 2026-10-04; see each route for intake status. Confidence: High on express authority and cited conditions; execution assignment is illustrative unless statute expressly names it.
Currentness: GovInfo 2024 Code (includes FY2025 NDAA, P.L. 118-159) read in full for cited provision; targeted FY2026 NDAA P.L. 119-60 amendment/repeal sweep. No claim of complete legislative currency through 2026-10-02; remaining 2026 delta needs counsel validation.
Review scope: Original research target October 2, 2026; no record-specific last-review date supplied. Publication is not legal-currentness certification.