For each echelon × consuming PoR pair: the PEO that owns it, the CDD/CPD it slots into, the fielding window, the authority lane (IL5 / IL6 / SIPR / JWICS), our engagement status, and the provenance level for the row. Reviewers respect "we know what we know and don't know" more than they respect blanket optimism — this page reflects that.
| Echelon | PoR | PEO / Owner | CDD / CPD | Fielding | Authority | Status | Provenance | Evidence | Notes |
|---|---|---|---|---|---|---|---|---|---|
| SQUAD | ATAK / iTAK | PEO C3T (TAK PMO under PdM Tactical Network) | Soldier Lethality CDD adjuncts; TAK is fielded under continuous capability drop | Continuous | IL5 / SIPR |
PROSPECT | PUBLIC_VERIFIED | Official TAK Product Center repos at github.com/TAK-Product-Center (Apache 2.0): ATAK-CIV, TAK Server CIV, Plugin SDK. ATLAS kill-chain bridge runs against either FreeTAKServer or TAK Server CIV without code change. We can develop, test, and demo on our own timeline — no DoD sponsorship required for civilian-build integration. | PROSPECT, not ENGAGED — no PEO C3T relationship. But feasibility is unblocked: 100% of the integration code can be written and validated against the official Apache 2.0 codebase before any PMO conversation. ATAK plugin path documented at /atak-plugin. |
| SQUAD | JBC-P | PEO C3T (PdM Mission Command) | Mission Command CDD | Continuous | IL5 / SIPR |
PROSPECT | PUBLIC_VERIFIED | JBC-P fielding under PEO C3T (PdM Mission Command) is public. CoT bus protocol is the integration surface; same protocol as TAK. JBC-P operational instance access requires PMO engagement; lab-side validation against TAK Server CIV (Apache 2.0, github.com/TAK-Product-Center) gives us 80% confidence that an operational JBC-P would consume identically. | PROSPECT. Same feasibility unblock as ATAK row via TAK Server CIV. |
| PLT-CO | WinTAK | PEO C3T | Mission Command CDD | Continuous | IL5 / SIPR |
PROSPECT | PUBLIC_VERIFIED | WinTAK-CIV is on github.com/TAK-Product-Center alongside ATAK-CIV (Apache 2.0). Same CoT bus protocol. Plugin SDK for WinTAK is less mature than ATAK's but exists. | PROSPECT. Identical pattern to ATAK row. ATAK is the right v1 plugin surface — see /atak-plugin Appendix B. |
| MULTI | Booz Allen Sit(x)® (commercial TAK federation; AWS GovCloud) | Commercial vendor — Booz Allen Hamilton (not a DoD PMO; SitX is BAH IP) | n/a — commercial product, not a CDD-driven PoR | Commercial GA; BAH-operated SaaS in AWS GovCloud | FedRAMP via AWS GovCloud |
PROSPECT | PUBLIC_VERIFIED | boozallen.com/expertise/products/sitx-situational-awareness-in-real-time.html — Sit(x) Bridge Adapters explicitly support 'third-party integrations [that] can send and receive data to TAK without having to develop a TAK plugin application.' BAH (via Greg, 2026-05-04) has indicated partnership interest in ATLAS as a bridge-adapter data producer. | Surfaced 2026-05-04 on BAH guidance. Path to fielded TAK consumption that is materially faster than building a native ATAK plugin (~2 weeks of API work vs ~8 weeks of Android dev). Commercial terms TBD. Documented as Architecture D in /atak-plugin. |
| BN-BCT | MSS (Maven Smart System / Mission Software variants) | Likely PEO IEW&S coord (program-office assignment varies by component) | DCGS-A modernisation pathway / MSS adoption | FY26 ongoing per public reporting | IL6 / SIPR |
PROSPECT | INFERRED | Maven Smart System publicly named (NGA, OUSD I&S). 'MSS' as a singular Army program of record is industry shorthand; precise PEO assignment not confirmed by us via .mil source. warfighter SME CAPES feedback named MSS as agentic-workflow consumer — that is one informal feedback session, not a PMO relationship. | Downgraded from ENGAGED → PROSPECT in 2026-05-04 audit. SME feedback is the warmest contact in this row but does not constitute PMO engagement. |
| BN-BCT | NGIC2 | NGIC (National Ground Intelligence Center, Charlottesville) | NGIC modernisation programme — exact CPD designation unverified | FY26–FY28 phased per industry reporting | IL6 / SIPR |
PROSPECT | UNKNOWN | NGIC is a real Army intelligence center (publicly named). 'NGIC2' as a precise program name is not verified by us against an authoritative .mil source. Treat naming as best-available shorthand pending verification. | Surface is plausible (analyst dashboards consuming external JSON); program-of-record name needs ground-truth validation before claiming it in a submission. |
| BN-BCT | Palantir AIP | Palantir Technologies (commercial); Army adoption via OTA + AAIC pathway | OTA — no CDD required for tool-spec consumption | FY26 (now) | IL5 → IL6 in flight |
PROSPECT | PUBLIC_VERIFIED | Palantir AIP is a real, generally-available product; tool-call spec ingest is documented Palantir capability. ATLAS ships /api/atlas/foundry-actions.json (OpenAPI 3.1, live and curl-able). NO Palantir FDE has confirmed consumption to us; spec-publication is one-way. | Downgraded from ENGAGED → PROSPECT in 2026-05-04 audit. ENGAGED would require a confirmed FDE wiring it into a customer workspace. |
| DIV-CORPS | Palantir Foundry | Palantir Technologies (commercial); Army adoption via OTA / Army G-2 partnerships | OTA + Phase II SBIR pathway | Continuous | IL5–IL6 / SIPR |
PROSPECT | PUBLIC_VERIFIED | Foundry is real, fielded across multiple DoD components. Same OpenAPI 3.1 spec inherits. Same one-way publication caveat. | Downgraded from ENGAGED → PROSPECT in 2026-05-04 audit. |
| DIV-CORPS | Maven Smart System (NGA) | NGA + OUSD(I&S) | Maven CPD | FY26 ongoing | IL6 / SIPR / JWICS |
PROSPECT | PUBLIC_VERIFIED | Maven Smart System public, NGA + OUSD I&S leadership documented in DoD reporting and congressional testimony. | OSINT swarm + DIME/PMESII synthesis are Maven-shaped inputs at the operational echelon. No NGA program-office engagement yet. |
| ASCC-JOINT | CJADC2 reference architecture | OUSD(R&E) / Joint Staff J-6 | CJADC2 reference architecture (portfolio governance, not a CDD per se) | FY26–FY30 phased | SIPR / JWICS |
PROSPECT | PUBLIC_VERIFIED | CJADC2 named DoD strategy (announced Feb 2024, OUSD R&E and Joint Staff). Sense/Make Sense/Decide/Act lane decomposition per public DoD documentation. | ATLAS lane mapping at /cjadc2-alignment is correct against the public reference architecture. Specific BAH framing pending verbatim from user. |
| ASCC-JOINT | Anduril Lattice | Commercial — DIU OTA pathway | OTA / DIU prototype-to-production | Continuous | IL5–IL6 |
OPEN | PUBLIC_VERIFIED | Anduril Lattice OS is a real fielded product with public API (developer.anduril.com). | Lattice API published; ATLAS tracks become Lattice entities once relationship opens. DIU Point Break submission is the warm-up move. |
| ASCC-JOINT | Gemini Enterprise (SIPR) | Google Public Sector / DISA | TBD — SIPR availability per industry reporting | FY27 estimated | IL6 / SIPR |
OPEN | INFERRED | Gemini Enterprise is a real Google Public Sector product. SIPR availability date and DISA acceptance pathway are inferred from industry reporting; we do not have a Google Public Sector confirmation. | ATLAS becomes a workflow node once Gemini Enterprise lands on SIPR. Timeline estimate is soft. |
| ACQ | SAM.gov | GSA (open) | N/A | Continuous | UNCLASS |
ENGAGED | PUBLIC_VERIFIED | SAM.gov is a real GSA service; sam-watcher agent is running in production against the live SAM.gov feed (curl-replicable today). This is the only ENGAGED row in the strong sense — live consumer, not just a published spec. | intel-CUB acquisition variant rolls SAM.gov hits into the daily 0500Z brief with PEO portfolio routing. |
This page works best with your current GPS location.