Governance & Program Info

Command & Control Decision Support — Governance

Cross-builder institution context and per-item ownership, due dates, status, and next actions for the governance-relevant checklist items in this builder.

← Back to checklist
Institution context
Program info
Applies across every builder in the app. Stored locally; nothing leaves the browser.
Checklist governance
Items (0 of 12 marked complete)
Annotate ownership, due date, status, and next action. Items on the left come from the builder's governance / compliance phases.
05 · Governance & Compliance
Map the system to the DoD AI Ethics Principles
required
Responsible, Equitable, Traceable, Reliable, Governable — every principle mapped to an architectural or process control.
05 · Governance & Compliance
Confirm DoDD 3000.09 applicability and posture
required
If the system could influence kinetic effects, 3000.09 applies. Legal / OGC concurrence is required before fielding.
05 · Governance & Compliance
Document intended vs. unintended use cases
required
What the system is accredited for, and what it is explicitly not accredited for — published to operators, not buried in the ATO package.
05 · Governance & Compliance
Obtain ATO for the inference environment
required
RMF-aligned ATO against NIST SP 800-171 (CUI) or applicable DoD Cloud SRG level for IL5/IL6 enclaves.
05 · Governance & Compliance
Establish cross-domain solution path where required
required
If the system spans enclaves, an accredited CDS and data-labeling regime must be in place — not a workaround.
05 · Governance & Compliance
Manage mission-partner releasability under DoDI 8110.01
recommended
If outputs cross into mission partner enclaves, data labeling and release authority must be architectural, not manual.
05 · Governance & Compliance
Confirm classification-of-training-data lineage
required
Every training sample, fine-tune corpus, and evaluation set classified correctly — training data provenance is audited at ATO.
05 · Governance & Compliance
Apply ICD 203 analytic standards to model-derived products
recommended
Confidence language, source sufficiency, alternative hypotheses — if the system produces finished-intelligence-shaped output, ICD 203 applies.
05 · Governance & Compliance
Complete program-level AI model documentation
required
Purpose, training data, assumptions, limitations, known failure modes — the model card and the ATO both reference the same document set.
05 · Governance & Compliance
Document model change management and version control
requiredtrinidy
Who approves model updates, what testing is required, how changes are versioned and rolled back, what the audit trail looks like.
05 · Governance & Compliance
Plan for continuous ATO / ongoing authorization
recommended
Model retrains and feed changes must flow through cATO / ongoing authorization — not re-submit a full ATO package every quarter.
05 · Governance & Compliance
Track JADC2 / CJADC2 program alignment
recommended
The JADC2 Implementation Plan (Mar 2022) and CJADC2 guidance shape the data fabric and interface conventions the system must compose with.