Staff administration and handover tools (optional)

Iron Major’s Friend is an authenticated administrative workspace for tasks, evidence, approvals and colleague sharing. It is not a substitute for service command-and-control authority.

Joint DoD · Service branches · Approved interagency missions

One mission picture. Different service needs. People remain in command.

U.S. Navy tactical aircraft conducting flight operations, illustrative of airspace mission needs
AIR
U.S. Army soldiers participating in air assault training, illustrative of land operations
LAND
U.S. Navy carrier deck operations aboard USS Ronald Reagan, illustrative of maritime missions
SEA
NASA Apollo 17 astronaut exploring the lunar surface, historic research image
SPACE
From awareness
to action
People  |  Data  |  Decisions  |  Mission outcomesExplore evidence-backed capabilities →
Integrated Services & Solutions LLC · SecureAssure · ATLAS

Make information useful across the joint force—without replacing existing systems.

ATLAS is a software integration and decision-support layer for Army, Navy, Marine Corps, Air Force, Space Force, joint commands and other authorized mission partners. The goal is to connect source evidence and operational context, show uncertainty, support responsible decisions and document verified handoffs. Existing programs of record and commanders retain control; integration and field performance must be independently demonstrated.

WHO WE ARE

Veteran-led ISS LLC: operational experience, implementation science, software engineering and evidence-centered delivery.

WHAT WE DO

Complement service-owned sensors, C2 tools and staff workflows with authorized, role-specific operational context across land, sea, air, space and supporting missions.

WHY WE DO IT

Disconnected data and workflows delay coordination, hide uncertainty and make decisions harder to reconstruct.

HOW IT WORKS

Ingest, check provenance, reconcile differences, offer options, require human approval, share authorized results and audit outcomes.

The same morning, two outcomes

A joint task force can confront conflicting reports, a disrupted data link, an aircraft or maritime contact, and delayed coordination at the same time. The Navy, Army, Marine Corps, Air Force and Space Force bring distinct systems and decision authorities. This notional comparison shows the integration gap ATLAS seeks to address; it is not a live DoD demonstration or proof of field acceptance.

THE MORNING WITHOUT IT · ILLUSTRATIVE
  • A report goes to one channel, and the picture stays split across the systems that saw it.
  • Each echelon sees its own fragment; the staff rebuilds the whole picture by hand, by phone, by message traffic.
  • The drone link degrades — and what it saw degrades with it, silently.
  • A decision gets made, and reconstructing who knew what, and when, becomes an archaeology project.
WITH AN AUTHORIZED ATLAS INTEGRATION · TEST HYPOTHESIS
  • The report enters one system and is fused with the other sources on the event — error and confidence stated, not implied.
  • The picture says plainly what it has lost when a source drops out.
  • The packet is written for the decision at hand — sources, weights, thresholds — and for the role and echelon that has to act on it.
  • A person releases or holds, and the record shows the decision and its basis.

The design objective is a shared, source-linked decision record whose presentation varies with the authorized role and mission—not disconnected copies of reality. The Army’s six warfighting functions are one service-specific lens; maritime, air, space and joint staffs require their own doctrinal mappings. The software training experience is a rehearsal, not evidence of operational certification. Compare service mission functions and program offices →

The morning shown is a notional exercise through the real seats. Most live feeds are not yet connected — the platform shows exactly which. No program-of-record integration or authority to operate is claimed.

One mission, multiple operating pictures

Choose a domain to explore an existing ATLAS surface. Public photographs show real military or space activity; they do not depict an ATLAS installation or government endorsement.

U.S. Navy aircraft launching from an aircraft carrier, illustrative of air operations
AIRAirspace awareness, track inputs, counter-UAS context.Open air picture →Photo: U.S. Navy / Defense Department.
U.S. Army Soldiers disembarking from a CH-47 helicopter during air assault training
LANDGround force common operating picture, movement, protection and sustainment.Open land / joint COP →Photo: U.S. Army / USARPAC.
Sailor signals aircraft launch readiness aboard USS Ronald Reagan in August 2020
SEAMaritime awareness, vessel feeds, expeditionary coordination.Open sea picture →Photo: U.S. Navy / Defense Department.
Apollo 17 astronaut working on the lunar surface in historic NASA photograph
SPACE / LUNARResearch pathways for governed autonomy and resilient mission assurance.Explore architecture →Photo: NASA Apollo 17; LUNAR SENTINEL remains research-stage.

Systems of systems, not another disconnected dashboard

1 · Discover & integrate

Existing feeds, sensors, staff tools, TAK / CoT and available partner interfaces.

2 · Diagnose & compare

Provenance, quality, competing explanations, gaps, and operational context.

3 · Decide with HIL

Authorized personnel review options and approve consequential actions.

4 · Deliver & learn

Route approved information, record custody, assess results, and adapt.

DiD / triple differences (DDD) require genuine comparison groups, baseline periods and observed outcomes. Where those inputs are absent, ATLAS must show “not established,” not a made-up effect.

Built DDIL-first: designed to keep working when the network doesn't

Denied, disrupted, intermittent and limited connectivity is the expected condition, not the exception. ATLAS treats offline operation as a first-class capability with explicit custody at every step — and states plainly what each piece has and hasn't proven.

OFFLINE NAVIGATION

Map area packs from an authorized offline-capable provider can be downloaded and their cached coverage checked; device-local waypoints provide GPS distance/bearing and SafeWalk breadcrumb trails. Public OpenStreetMap tiles are not an offline-download source. No turn-by-turn routing is claimed.

STORE-FORWARD QUEUE

Operator actions authored offline are held in a durable outbox, submitted with idempotency keys to an authenticated server queue (PostgreSQL + encrypted spool), and replayed with per-action receipts. Queued is never shown as delivered.

DEGRADE LOUDLY

Cached data carries its age; dropped sources are declared, not silently backfilled; offline writes that cannot be safely queued return an explicit refusal with a receipt instead of a fake success.

DEVICE PREPARATION & DELIVERY

Provision the PWA before disconnecting, then use Check Offline Readiness to verify the app shell, cached map coverage and storage status. The edge proxy can select a healthy configured origin; standby hosting still requires account configuration and live verification.

Evidence is software acceptance: service-worker, outbox, tile-pack and queue-lifecycle tests plus a proven server-restart recovery. Field, contested-RF and congested-spectrum certification is not established and is stated as such wherever these capabilities appear.

Joint mission functions, with doctrine and ownership defined by each service

Command and control, intelligence, fires and effects, movement, protection, sustainment, and training are comparable needs across DoD—but no branch is presumed to use Army doctrine. Open the service-by-service WFF/program-office crosswalk to see candidate integration owners, source evidence and what still needs government approval.

Integration and evidence differ by module; one functioning endpoint does not establish field certification across the whole platform.

Designed for stakeholders; adoption must be earned through evidence

Potential users and collaborators span commanders and staff, all service branches and the National Guard, emergency managers, analysts, operators, acquisition offices, technical evaluators, systems integrators, universities and research partners. Engagement does not imply endorsement.

The public deployment is an unclassified evaluation environment. DoD operational ATO, IL-5 hosting, OEM integrations and classified-network authority are not established.

Symphony on a chassis

One coordination workflow, with specialized tools and views that retain the same source, task and decision context.

SecureAssure hosts ATLAS — one decision platform with four front doors. SHIELD is only the personal-safety lane.

Start with the work you need to finish. Choose the relevant role and mission view, inspect its sources and follow the next authorized step. · Naming FAQ · Full chassis story · Compose intent

Pick your mission — click any door to see what's inside before you enter. Every door shows what ATLAS does for that mission independently, what it does jointly, and how far down the echelon it reaches. Locked demos keep language, APIs, and RAG in-lane.

Includes access-level checks when SITE_ACCESS_MODE=private · Unlock via door badge or change front door
Not sure where to start? → Mission fit check Two-minute fit check for EM, joint, and federal missions — then pick your door above for a guided demo.
Inspect engineering wiring status (not field readiness)

Module and integration tests describe code registration and technical checks. They do not establish live DoD endpoints, operational delivery, authorization or field acceptance. Read each probe’s exact evidence and freshness.

Select your mission door

Each door is a distinct orientation; protected work requires sign-in and program approval. See the scoped Army vehicle rehearsal only if that is your mission.

PROGRAM OFFICE? START HERE
Start with the branch, the mission owner and the existing system. Compare what ATLAS can actually prove.
Army vehicle protection is one example. Navy, Marine Corps, Air Force, Space Force and joint program pathways have distinct missions and evidence gates.

First visit? Know where to start in 30 seconds.

Select your role, learn what this page means, and follow a real five-minute walkthrough. Day-one and week-one training are included, with help available when you need it.

Start my training guide
Civilian / dual-use entrance — separate operating environment

Community health, civilian emergency support, infrastructure and business operations. A separate security environment is required; this entrance never passes along military data or credentials.

Open the civilian entrance

Full door catalog · ~45s video previews · 6-min walkthrough

Full story /fork · Door catalog /doors · Per-door demos /walkthrough · C2 integration TDP /c2-tdp · Staff and mission command /staff · Symphony (one score, many sections) /symphony · change front door