Operational View 2 — Node Connectivity. Part 1 (below through Symphony): what connects to what. Part 2 (Technical Flows): interconnected pipelines — what operation runs where, how data moves, latency budgets per hop.
Enacted: NDAA FY2017, Section 804
All major defense acquisition programs shall implement a modular open system approach. Systems must expose open, non-proprietary interfaces so any compliant component can be swapped or integrated without proprietary lock-in.
NDAA FY2021 Section 832 — mandated JADC2 strategy + 180-day implementation plan
DoD shall develop a framework to connect sensors from all services into a single network, enabling any sensor to task any shooter across all domains. Every new DoD system must demonstrate JADC2 interoperability.
DoD directed to establish an open architecture standard for Counter-UAS systems to prevent vendor lock-in and enable multi-vendor engagement solutions.
GET /api/cuas/open-architecture/scenario.Requires human judgment in decisions to apply lethal force. Systems must keep humans "in the loop" for all lethal autonomous actions.
POST /api/useif/killchains/:id/approve — no automated kinetic action, ever. This is Iron Rule 5.Loading external data sources…
Loading processing layers…
doctrine-corpus.json at runtime and includes a hitlGate field — human approval required before any kinetic action. Open Decision Intelligence Hub →
Loading decision tools…
Loading interconnect overview…
Loading technical flows…
Loading branch matrix…
This page works best with your current GPS location.