Start here · 6-minute evaluator orientation

One system. Many missions.
One decision trail.

ATLAS is a joint DoD-ready design proposition for multiple services and defense agencies—not an Army-only platform or a replacement for existing military systems. It helps authorized people gather evidence, understand what changed, compare alternatives, coordinate responsibilities, and preserve the record of decisions and outcomes.

Joint DoD frequently asked questions, AI and GPU →Walk through six VBK-representative training scenarios →No government hardware or track accuracy claimed. Authenticated live source workflow remains separate.
What is working in ATLAS software differs from what has been tested on a fielded government system. A page link or simulated exercise is never evidence of VBK integration, accreditation, operational identity determination, an effects interface, or measured field performance.
What the Soldier and commander actually receive

Not just “a sensor sends something.” Here is the usable output.

1 · Crew receives a fact with limitations

What was reported? Which sensor? When? Sound, direction, distance and speed only where measured. Missing values remain UNKNOWN. The crew sees if the information is old or uncorroborated.

2 · Commander receives a decision brief

What we know, what we do not know, who should verify, and what coordination is appropriate. No unverified aircraft identity or autonomous effect approval.

3 · Program office sees what is proven

Which source actually exchanged data? Was the recipient's receipt verified? What accuracy was measured? Which VBK/TAK/partner integration still requires authorization and physical testing?

If no authorized sensor is connected, the display explicitly says so. The page does not insert fictional readings to manufacture an impressive demonstration.

01ConnectReceive authorized sensor, operator and enterprise records without replacing their owners.
02UnderstandShow source identity, freshness, uncertainty and relevant operational context.
03CompareReview bounded response options and dependencies without claiming autonomous authority.
04CoordinateHuman-reviewed handoffs to a named recipient with status and receipts where supported.
05EvaluateShow precisely which code, real data exchange, partner endpoint and field test supports a claim.
Mission first—not a software menu

Whose problem are we solving?

Select a stakeholder. The explanation, available application links, current evidence limits and next acceptance gate change to match that mission.

Who it serves

Vehicle crew → formation → protection staff

The real problem

What ATLAS adds

What this does not claim

Open the existing software

Follow a real workflow

Required next test

What software does what, for whom, and why

Six components, not hundreds of unexplained tabs

Every other module is a capability within one of these six jobs. Different users see different views over the same principles of ownership, evidence and decision authority.

Connector / USEIF

What: Input contracts, source identity, data validation.
For: OEM interfaces, sensor partners, units, authorized feeds.
How: Approved HTTP/CoT/SensorThings or purpose-built adapter; each connection and use case needs its own authority.

Inspect source workspace ↗

Evidence and Fusion

What: Attribute, reconcile and qualify observations.
For: Intelligence and operational staff.
How: Validation, freshness and provenance; do not infer unobserved data or turn a classification hypothesis into a fact.

Explore fusion software ↗

Common Operating Picture

What: Role-specific situational context.
For: Crews, commanders, emergency managers.
How: Present the approved sources relevant to each echelon, with unknowns and stale data visible.

Open COP ↗

Planning and Support

What: Compare draft courses of action, dependencies and consequences.
For: Fires, maneuver, sustainment and protection staffs.
How: Bounded synthetic rehearsal first; real operational use requires validated data and permissions.

See ground-support rehearsal ↗

Human Decision and Handoff

What: Named responsibility, approval and reported outcome.
For: Staff owners and recipients.
How: Existing authenticated source-linked administrative handoff; this does not authorize weapon, jammer or VBK effects.

See handoff/receipt chain ↗

Evaluator and Partner Interfaces

What: Acceptance evidence and external display contracts.
For: PMs, engineers, primes, Unity/XR/TAK consumers.
How: Versioned schemas, source evidence, tests and independent partner/client validation.

Open partner/Unity contract ↗
Department of Defense mission ecosystem

One decision chassis; service-specific missions and authorities

The Army vehicle example below is a deliberately bounded evaluation wedge—not the definition of ATLAS. A joint sponsor must select the system of record, source rights, operational authority, releasability, deployment boundary, acceptance tests, and recipient for every service or agency use case.

Army & Marine Corps

Maneuver, expeditionary operations, force protection, fires coordination and contested sustainment. Existing tactical systems keep control and record ownership.

Navy

Maritime common picture, surface and subsurface observations, afloat sustainment and joint handoffs. No claim of authenticated shipboard or certified fleet-system integration.

Air Force & Space Force

Air operations and ISR coordination, installation protection, PNT resilience and space-domain context. Native operational feeds require sponsor-approved interfaces and independent trials.

Joint commands & defense agencies

Multi-echelon coordination, evidence fusion, logistics and geospatial/cyber support; share only with verified organization, unit and releasability authority.

Guard, Coast Guard & partners

Defense support and interagency/coalition handoffs remain separately authorized. Coast Guard service status and National Guard command authority depend on mission and legal context.

How to challenge the fit

Measure gaps against existing DoD programs. If the current system already delivers equivalent timely, reliable, secure outcomes, ATLAS should not create redundant infrastructure.

Review the full joint-DoD evaluator FAQ →
Find the right mission owner before choosing a product

Joint DoD warfighting-function / program-office crosswalk

The Navy, Marine Corps, Air Force and Space Force are not forced into Army doctrine. Compare the actual function, service program portfolio, existing system, operator impact and proof required for each pilot. Candidate offices are not sponsors.

Example pilot · PAE Maneuver Ground · grounded in Army acquisition priorities

Scoped Army vehicle-protection evaluation example

The Army's current PAE Maneuver Ground emphasizes taking care of Soldiers, being a great teammate, and delivering formation-based capabilities. Its Assistant Capability Program Executive publishes Futures, Adaptive Squad Architecture, Soldier Integration Facility and Soldier Enhancement Program as lines of effort. These are Army-described priorities and LOEs. The application mapping below is **ISS analysis**, not an Army endorsement.

Army priority / published LOESHIELD contribution and existing mission ownerTruthful evaluation question
Deliver formation-based capabilitiesMounted crew → dismount → platoon/company shared evidence, role-relevant views, human reviewCan two verified users receive consistent source meaning while the vehicle changes position and communications vary?
Take care of our peopleReduced transcription burden and clearer failure indication; protection awareness before additional dashboard complexityDoes crew workload improve against current process in a representative supervised trial?
Be a great teammateComplement VBK, installed computers, TAK and the Government's chosen C2 backbone; retain OEM data rights and ownershipCan one approved read-only data product be connected without altering safety-critical control?
Futures / Adaptive Squad ArchitectureDigital interface contract and operator/echelon filtering, documented adaptations; no claim of Army plug-in certificationCan a modular software adapter be introduced and independently tested under existing MOSA processes?
Soldier Integration FacilityInstrumented end-to-end field configuration and human-factors acceptanceCan a witnessed actual-device test reproduce the claimed latency, data quality and handoff?
Soldier Enhancement Program / industryGovernment and industry-owned joint evaluation with ISS as a candidate software component, rather than a replacement platformWho sponsors the requirements and test protocol, and who owns transition?
PM XM30 Digital Trinity: MOSA, digital engineering, DevSecOpsVersioned interfaces, regression evidence, change and release controlsCan the software satisfy the actual program interface, cyber and configuration criteria?

Primary Army references: PAE Maneuver Ground mission and priorities · Assistant Capability Program Executive LOEs · PM XM30 digital acquisition.

No black box

Which kind of proof is this?

Code existsA function or route is implemented. Not proof of a physical connection.
Software executedTest or runtime proves a bounded behavior, with version and conditions.
Data exchangedA source record was obtained and its actual origin, time and hash persisted.
Recipient acknowledgedA distinct authorized user received and acknowledged the exact reviewed content.
Field acceptedGovernment sponsor witnessed the installed configuration, limitations and safety/operational behavior.
ATLAS has code-backed interfaces and some authenticated, persisted workflow evidence. ISS has not established Government-witnessed VBK, VIPERS, MAF, IBCS, AFATDS or classified-network field integration. Signal Sights is an active prospective Unity/XR teaming relationship; the code-backed partner interface is not proof of an approved or fielded Signal Sights installation.
The 90-second explanation Mia can repeat

We make existing systems work together, then prove the value.

“Start with the Soldier, not the catalog. A crew or sensor already knows something, but another staff element may not see it in time or understand its limitations. ATLAS's first job is an authorized, trustworthy connection. Its second is to show the evidence in the language of the person who needs it. Its third is to support a human choice and preserve a verified handoff. We would test that chain against the sponsoring DoD organization's actual process. The Army VBK example does not replace VBK, TAK, the vehicle computer or the commander, and Navy, Air Force, Marine Corps, Space Force and joint-command trials require their own source and acceptance contracts. We will show exactly what works today, what is a software rehearsal, what requires an interface agreement, and what must be proven on an actual moving vehicle.”

ISS LLC · CAGE 9VKK3. No external deployment, fielded partner connection, military command handoff, target engagement or award is implied by this site navigation guide. Exact endpoint reachability, authorization and source freshness must be checked during each evaluation.