National Defence

FOI via central portal; open.canada.ca org page attempt returned 404

Current this library's internal records: Department of National Defence and the Canadian Armed Forces 2026-27 Departmental Plan (2027)

Completeness

• Document shelf: 46 rows (44 archived · 2 staged · 0 pending · 0 missing)
• Backgrounder: on file
• Strategy-evolution brief: on file
• Custody audit: 36 of 46 row(s) audited, all clean
• Last verified: 2026-08-06 · this org has NOT had a full discovery-verification pass (our discovery-verification log)

Endpoints

• Website
• Open data: not yet verified
• API: not yet verified
• RSS
• Newsroom
• FOI / access requests: not yet verified

Document shelf (46 rows)

Backgrounder

Source: this library's internal records — a mechanical research draft, not independently reviewed for publication; reproduced as-is.

National Defence - backgrounder

Backgrounder / 2026-07-30 / registry row: fed-national-defence (this library's government-document registry) / lens file for this org's series briefs

Mandate & statutory basis

The Department of National Defence (DND) is governed by the National Defence Act (R.S.C., 1985, c. N-5), consolidated and current to 2026-06-14 at laws-lois.justice.gc.ca (https://laws-lois.justice.gc.ca/eng/acts/N-5/, fetched and verified directly). Part I ("Department of National Defence") establishes the Department at section 3; Part II ("The Canadian Forces") constitutes the Canadian Armed Forces at section 14 (same source). This registry row's url_status is flagged ⚠️ still being checked in the registry (registry row: fed-national-defence).

Roles, responsibilities & scope

DND supports the Canadian Armed Forces (Navy, Army, Air Force, and Special Forces) "to defend Canadians' interests at home and abroad," covering military operations, equipment procurement, base infrastructure, and personnel management, governed internally by Defence Administrative Orders and Directives (DAOD) and Queen's/King's Regulations and Orders (QR&O) (https://www.canada.ca/en/department-national-defence.html, fetched via text-rendering proxy). The Military Police Complaints Commission (registry: fed-military-police-complaints-commission-canada) provides independent oversight of military police conduct under Part IV of the same Act (https://laws-lois.justice.gc.ca/eng/acts/N-5/).

Governance & reporting line

DND/CAF is led by the Minister of National Defence (the Honourable David J. McGuinty per the department's current public-facing page) (https://www.canada.ca/en/department-national-defence.html, fetched via text-rendering proxy). ⚠️ still being checked - the Deputy Minister and Chief of the Defence Staff, the department's civilian/military dual-leadership structure, were not confirmed by name against a fetched official source this review, though the National Defence Act's Part I/Part II split (department vs. armed forces) is confirmed directly (https://laws-lois.justice.gc.ca/eng/acts/N-5/).

Budget scale

⚠️ not yet confirmed against an original source. Repeated attempts to fetch DND's 2026-27 Departmental Plan financial pages (canada.ca) returned HTTP 403 errors this review; no planned-spending figure was extracted from a successfully fetched source. Registry strategy_current_title: "Department of National Defence and the Canadian Armed Forces 2026-27 Departmental Plan" (registry row: fed-national-defence).

Institutional history

⚠️ still being checked - the National Defence Act (R.S.C., 1985, c. N-5) confirms the Department (Part I, s. 3) and Canadian Forces (Part II, s. 14) as currently constituted (https://laws-lois.justice.gc.ca/eng/acts/N-5/), but a specific founding date and the commonly cited 1968 unification of the three armed services were not confirmed against an official source fetched this review.

Strategy evolution brief

Source: this library's internal records — a mechanical research draft, not independently reviewed for publication; reproduced as-is.

Department of National Defence - strategy evolution

2026-08-02 / registry: fed-national-defence / grounded in archived copies (cited document id + sha256) / read through our research file for that body

TL;DR: Of a 46-row registry spanning 1999-2026, only 7 documents in the archived subset actually yield readable content — the two most recent (Departmental Plan 2025-26 and Departmental Results Report 2024-25) plus five earlier partial captures that turn out to be tables-of-contents only. The biggest priority addition the readable record can support is "Culture Evolution" as a named, tracked standing priority alongside Operations/Reconstitution/Modernization/Stewardship in the department's 2024-25 and 2025-26 top-line priority lists, backed by a five-year "Comprehensive Implementation Plan" (announced June 2024) addressing recommendations from external reviews of workplace conduct. The biggest structural change the record can see is the shift from the pre-2015 "Strategic Outcome / Program Activity Architecture" reporting framework to the current six "Core Responsibilities" framework, though the exact transition year is unreadable (see gaps). The most load-bearing number is total planned spending of $35,665,011,698 for FY 2025-26 (dp-2026, sha256-12 318b5624a7d5), up from $33,924,795,251 actual spending reported for FY 2024-25 (drr-2025, sha256-12 0bbf1f0bbfb4). One open question: whether and how the department's "readiness has continued to decline" admission (drr-2025) for Ready Forces — its single largest spending line — is addressed in the next available document, which this series does not reach.

Backgrounder summary

Per the backgrounder (our research file for that body), DND is governed by the National Defence Act (R.S.C., 1985, c. N-5): Part I establishes the Department (s.3), Part II constitutes the Canadian Armed Forces (s.14). DND/CAF supports Navy, Army, Air Force, and Special Forces operations, procurement, infrastructure, and personnel management. The backgrounder flags the registry row's url_status as ⚠️ still being checked, and could not confirm Deputy Minister/Chief of the Defence Staff names or a budget baseline against a live-fetched source that session — this brief's own reading below fills some of that gap from the archived documents themselves (Minister named in-document as a matter of institutional record, per guardrail; Deputy Minister/CDS not named in the text actually read). The backgrounder's institutional-history section is also ⚠️ still being checked for founding-date specifics; nothing in the readable archived series resolves that either.

Series inventory

_index.json: 7 ok / 27 stub-suspected / 0 extract-failed.

Registry (our document registry) carries 46 rows for this org spanning 1999-2026; 34 are archived and appear below (matching the 34 entries in _index.json, since the extraction dir covers the archived subset), 12 are staged and 0 are missing — those 12 staged years are not analyzable from the archive and are treated as gaps, not as disclosure choices. The 12 staged rows cluster tightly: departmental-plan and results-report pairs for 2007-2011, plus a lone dp-2013, all carrying ⚠️ Still being checked: dead-url-wayback-only and repeated fetch-failed flags in the registry.

TRUE usable count: 2 (dp-2026, drr-2025). The five other ok-flagged rows (dp-2015, dp-2016, dp-2017, drr-2014, drr-2015) passed the char-count floor but on direct read contain only Program Alignment Architecture section headers (a nested outline running to hundreds of sub-sub-program lines) with no priority narrative, budget figures, or discussion text — the actual report content lived in a linked PDF that this capture pass did not retrieve. They are functionally identical in kind to the confirmed stubs, just longer, because deeply nested outline text pushed them over the floor. This brief treats them as structural inventory only (confirms report titles, dates, and the PAA→Core Responsibilities framework existed) and does not cite them for any priority, budget, or narrative claim.

Priority evolution

With only 2 documents carrying real narrative content — both from the same recent two-year window (FY2024-25 and FY2025-26) — this record cannot show evolution across the 1999-2026 span the registry covers. What the two usable documents DO establish, side by side:

• FY2024-25 (drr-2025, 0bbf1f0bbfb4): the department's five named 2024-25 priorities were "Operations and Readiness; Reconstitution; Culture Evolution; Modernization; and Stewardship and Compliance." The reporting frame used is the six-"Core Responsibility" structure (Operations, Ready Forces, Defence Team, Future Force Design, Procurement of Capabilities, Sustainable Bases/IT/Infrastructure) plus Internal Services.
• FY2025-26 (dp-2026, 318b5624a7d5): the same six-Core-Responsibility structure is retained unchanged. The Minister's message foregrounds Canada's April 2024 defence policy update "Our North, Strong and Free" (ONSAF), Arctic/NORAD modernization, CAF "reconstitution" (personnel growth), "Culture evolution," and a stated commitment to reach 2% of GDP in defence spending.
• Both documents describe "Culture Evolution" as an active, tracked, multi-year program (Culture Evolution Strategy, Culture Evolution Implementation Plan, network of "Culture Evolution Coordinators"), tied to a five-year, four-phase "Comprehensive Implementation Plan" (CIP) announced June 2024 that implements recommendations from external reviews of CAF workplace conduct, plus continuing work on "Independent Comprehensive External Review" (IECR) recommendations and a legislative package tied to a "Third Independent Review of the National Defence Act." All of this is reported institutionally (committees, plans, indicator tables); this brief does not name any individual associated with a review, complaint, or grievance, per guardrail.
• Whether "Culture Evolution" or "Reconstitution" as named standing priorities existed before FY2024-25 cannot be determined — no earlier document in the readable set carries a comparable priorities list. The five ToC-only "ok" documents (2014-2017 window) show the pre-2015/2016-era reporting ran on a different framework ("Strategic Outcomes" and numbered "Program Activities"/"Programs," e.g., "STRATEGIC OUTCOME 1: DEFENCE OPERATIONS AND SERVICES IMPROVE STABILITY AND SECURITY..." in dp-2015/2016/2017; "RESOURCES ARE DELIVERED TO MEET GOVERNMENT DEFENCE EXPECTATIONS" in drr-2014/2015), but since only their section headers were captured, this brief cannot say what priorities or budget figures sat under those headings, only that the framework name differed from today's "Core Responsibilities."

Priorities added, dropped, renamed

The record supports only structural, not evolutionary, claims: - Reporting-framework rename (era bounded, not dated precisely): "Strategic Outcomes" / "Program Alignment Architecture" (seen in dp-2015 8f68e41e5eed, dp-2016 cc9735199061, dp-2017 b5c3af89b78a, drr-2014 25ce0e013aa1, drr-2015 d516decff828 — headers only) gives way to the current "Core Responsibilities" framework (confirmed narrative use in drr-2025 0bbf1f0bbfb4 and dp-2026 318b5624a7d5). ⚠️ Still being checked: the exact transition year — no document in the readable set bridges the gap; Treasury Board government-wide reporting reforms of the mid-2010s are the likely cause but that is outside-record context, not sourced to a DND document read here. - Cannot establish "added/dropped/renamed" for any specific priority line item (e.g., when "Culture Evolution" first appeared as a named top-line priority, or what if anything it replaced) because only two documents, one year apart, carry priority-list narrative at all.

Budget & mandate inflection points

• FY2024-25 actual spending: $33,924,795,251; staff (FTE, including internal services): 92,674 (drr-2025, 0bbf1f0bbfb4, "At a glance").
• FY2025-26 planned spending: $35,665,011,698 across six Core Responsibilities plus Internal Services (dp-2026, 318b5624a7d5, Table under "Planned spending and human resources"). Note the department's own three-year comparison table in dp-2026 separately shows FY2024-25 "Forecast spending" as $33,741,361,702 — a slightly different figure from the $33,924,795,251 "actual" cited in drr-2025's own "at a glance" summary; both are the department's own numbers from two different documents/purposes (forecast vs. final actual) and are reported here as such, not reconciled.
• April 2024 — Canada's defence policy update "Our North, Strong and Free" (ONSAF) released, cited in both usable documents as the current policy anchor, including a stated $8.1 billion over five years (from FY2024-25) and $73 billion over twenty years (drr-2025, 0bbf1f0bbfb4).
• Budget 2024 — $1.4 billion over five years allocated to replenish military equipment supplies (drr-2025, 0bbf1f0bbfb4, Minister's message).
• June 2024 — Comprehensive Implementation Plan (five-year, four-phase) announced for workplace-conduct/culture-related external-review recommendations (drr-2025, 0bbf1f0bbfb4).
• 2025 Speech from the Throne — government commitment cited to "rebuilding, rearming, and reinvesting in the CAF," including joining "ReArm Europe" (dp-2026, 318b5624a7d5, Minister's message). ⚠️ Still being checked: this is the department's own characterization of a government-wide announcement, not independently confirmed here.
• March 2025 — $6 billion partnership announced with Australia for Over-the-Horizon Radar technology, framed as part of a $38.6 billion, 20-year NORAD modernization program "the largest investment in Canada's NORAD capabilities in decades" per the department's own framing (drr-2025, 0bbf1f0bbfb4) — per that batch’s own build note §A4, this superlative is bounded to this document's publication date; no later document in this series exists to check it against.
• No inflection point before FY2024-25 can be dated from readable content; the pre-2018 record in this archive is either interstitial stubs or ToC-only captures.

Ontario/Toronto relevance

Indirect. Neither usable document (dp-2026, drr-2025) names a Toronto-specific installation; the Ontario-relevant infrastructure named in dp-2026's Minister's message and elsewhere in the readable text is national/multi-provincial (e.g., work at Canadian Forces Bases named are Gagetown, Petawawa, Esquimalt, Halifax — none in the Toronto area, per drr-2025 0bbf1f0bbfb4). DND/CAF is a federal institution whose mandate, budget, and Arctic/NATO/NORAD priorities apply nationally; Toronto/GTA relevance runs through general federal presence (recruiting, reserve units, cadet programs referenced institutionally) rather than any documented Toronto-specific footprint in the two documents actually read. This is a one-sentence, indirect-relevance call per the format rule — no inflation of boilerplate national-scope language into local presence.

Residuals & gaps

• Registry gap, per that batch’s own build note §A1: 12 of 46 registry rows are staged (queued/failed capture), not archived: departmental-plan and results-report pairs for 2007, 2008, 2009, 2010, and 2011, plus a lone departmental-plan for 2013. All twelve carry the registry flag ⚠️ Still being checked: dead-url-wayback-only plus repeated fetch-failed entries from 2026-07-30 through 2026-08-02. These years are not analyzable from the archive; this is a capture gap, not evidence the department stopped publishing.
• The batch's hardest archival case, as flagged in the boot brief: of the 34 archived rows, only 7 passed the char-count floor, and of those 7, direct reading shows only 2 (dp-2026, drr-2025) actually carry narrative/budget content. The other 5 "ok" rows are Program Alignment Architecture tables of contents that happened to be long enough (deeply nested sub-sub-program outlines) to clear the 3,000-character floor without containing any substantive prose. This is a detector-QA finding worth flagging explicitly for one of this library's own engineering records: the char-count floor is not a reliable substantive-content signal for this org's document family, because canada.ca's "this page has been archived" wrapper pattern preserves the full navigational ToC/outline (which can run to 150+ lines for DND's granular Program Alignment Architecture) while dropping all body prose into a separately-hosted, uncaptured PDF. A ToC-length false positive is possible wherever an org's outline structure is unusually deep.
• Detector-QA verdicts, explicit, per doc:
• fed-national-defence-dp-2014 (2,399 chars, the specific case flagged for scrutiny in this boot brief): agree with stub-suspected. Confirmed by direct read: pure ToC + one boilerplate archival notice, zero body content. Correctly caught despite the "plausibly real-but-thin landing page" concern in the boot brief — this is not a thin landing page, it is a wrapper with no page-specific content at all.
• fed-national-defence-drr-2012 (2,668 chars) and fed-national-defence-drr-2013 (2,687 chars): agree with stub-suspected, same pattern.
• fed-national-defence-dp-2020 (1,813 chars) and fed-national-defence-drr-2024 (930 chars): agree with stub-suspected, same pattern, sampled from opposite ends of the sub-floor range.
• fed-national-defence-dp-2004, -dp-2005, -drr-1999, -drr-2001, -drr-2002, -drr-2005, -drr-2006 (all exactly 804 chars): agree with stub-suspected — confirmed bilingual publications.gc.ca/LAC interstitial wrapper, zero report content, sampled dp-2004 directly.
• Disagreement, direction: detector too lenient (false "ok"): fed-national-defence-dp-2015 (8,802 chars), -dp-2016 (8,711 chars), -dp-2017 (9,576 chars), -drr-2014 (6,863 chars), -drr-2015 (8,572 chars) are all marked ok by the char-count floor but on direct full read contain no report body content — only a nested Program Alignment Architecture table of contents (100+ line items in some cases) plus, for dp-2017, a two-paragraph budgetary-erratum notice. These should arguably be reclassified as stub-suspected (or a new category, "toc-only") rather than ok, since "content read? yes" would overstate what was actually recovered. This brief treats them as structural-only evidence and does not cite them for any substantive claim, but the underlying _index.json status is, in this lane's judgment, wrong in the lenient direction for these five.
• ⚠️ Still being checked: the year the reporting framework changed from "Strategic Outcomes/Program Alignment Architecture" to "Core Responsibilities" — unrecoverable from this series; likely mid-2010s Treasury Board policy change but not sourced to a DND document read here.
• ⚠️ Still being checked: reconciliation of drr-2025's "actual" FY2024-25 spending figure ($33,924,795,251) against dp-2026's "forecast" FY2024-25 figure ($33,741,361,702) — both are the department's own numbers, not an error found by this lane, just two different reporting bases not reconciled in either document.
• ⚠️ Still being checked: outcome/current status of the Comprehensive Implementation Plan's later phases (Phase 2 of 4 was reported complete as of drr-2025); no later document exists in this archive to check against.
• No archive_status=missing rows apply to this org (0 of 46); all non-archived rows are staged.