Governance & Program Info
All-Source Intelligence Fusion — Governance
Cross-builder institution context and per-item ownership, due dates, status, and next actions for the governance-relevant checklist items in this builder.
Institution context
Program info
Applies across every builder in the app. Stored locally; nothing leaves the browser.
Checklist governance
Items (0 of 15 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
Implement ICD 710 classification management on model outputs
Derivative classification, marking, and declassification rules apply to AI-generated product exactly as they apply to analyst product.
05 · Governance & Compliance
Implement ICD 501 discovery and dissemination controls
Make intelligence discoverable to those who need it, within authorities and caveats — the positive duty, not just the negative one.
05 · Governance & Compliance
Integrate cross-domain solution (CDS) posture
Any flow across classification levels must transit an NSA-evaluated CDS — no model-layer workarounds.
05 · Governance & Compliance
Enforce foreign-disclosure review on releasable output
REL TO caveats and FVEY / bilateral release decisions must pass a formal disclosure review, not a model toggle.
05 · Governance & Compliance
Handle CUI per DoDI 5200.48 and NIST SP 800-171
CUI intermediate products (training data, evaluation outputs) must be marked, protected, and disposed of per the CUI program.
05 · Governance & Compliance
Complete DoD / IC ATO package for the AI stack
Full A&A documentation under RMF — system categorization, control tailoring, continuous monitoring plan.
05 · Governance & Compliance
Align with DoD AI Ethics Principles
Responsible, equitable, traceable, reliable, and governable — the five DoD AI Ethics Principles apply to every AI system used by DoD personnel.
05 · Governance & Compliance
Confirm DoD 3000.09 non-applicability for non-weapon use
DoD Directive 3000.09 governs autonomy in weapon systems. If the fusion model does not inform a weapon function, document that boundary explicitly.
05 · Governance & Compliance
Coordinate with IG / OGC on civil liberties and privacy review
ODNI CLPO and IC element civil liberties officers review AI systems for civil liberties and privacy impact.
05 · Governance & Compliance
Document model purpose, scope, limitations, and known failure modes
The model card / model documentation is an ATO artifact and a tradecraft artifact — keep it current with the production model.
05 · Governance & Compliance
Conduct independent model validation
Validation by a team independent of development — often the IC element's model risk function or an external red team.
05 · Governance & Compliance
Retain complete decision audit trail
Every inference — inputs, retrieved chunks, generated output, analyst disposition — retained for audit and re-evaluation.
05 · Governance & Compliance
Define model change management and version control
Who approves model updates, what testing is required, how are changes versioned, what is the rollback path.
05 · Governance & Compliance
Map IC FY24 $76.4B budget lane to the program
ODNI publicly disclosed the FY24 IC NIP request at $76.4B — understand which program element your effort sits under.
05 · Governance & Compliance
Benchmark scale against Maven Smart System and NGA Luno A/B ceilings
Publicly reported ceilings — Maven Smart System $480M (CDAO) and NGA Luno A/B at $290M each (announced May 2024) — bound the enterprise scale envelope.