HUMANITARIAN & NGO COORDINATION LAYER

SHIELD/ATLAS is not a single-service, single-mission, or single-agency platform. The same global feeds, reunification workflows, hospital and EMS coordination, anonymous reporting intake, and broadcast capability that serve a combatant commander serve a Red Cross logistics planner trying to route a relief convoy or an MSF medical coordinator trying to deconflict from nearby military activity. This page is the humanitarian-facing lens. Access is read-mostly. The kinetic surface (fire-mission generator, ballistic solver, operator-detection) is not exposed to humanitarian users by role policy.

Read-Mostly Access Same Platform, Different Lens No Kinetic Surface Exposed Deconfliction-Aware

Red Cross / IFRC

Disaster logistics & family reunification

Same NOAA / USGS / FIRMS feeds and AIS port status the warfighter uses, but framed for disaster response. Family reunification workflows for displaced-persons response. Hospital surge coordination for medical teams.

ARCIFRCICRC

Wildfire (FIRMS) NWS Alerts Earthquake (USGS)

MSF / Medical NGOs

Medical-mission deconfliction & hospital ops

Awareness of nearby military activity (at appropriate classification) prevents tragedies like the Kunduz hospital strike. Hospital and EMS coordination workflows, patient handoff, surge-capacity tracking, mass-casualty planning.

MSFIRCPIHMercy Ships

Hospital / EMS Coord. Sea Lane Status

UN Agencies

OCHA / WFP / UNHCR / WHO operational picture

Theater-wide disaster picture for OCHA cluster coordinators. Logistics corridor (road, port, air) status for WFP. Refugee-flow context for UNHCR. Outbreak / health-system feeds for WHO.

OCHAWFPUNHCRWHOUNICEF

Common Op Picture Logistics Corridors

USAID / OFDA

US humanitarian assistance & disaster response

Disaster Assistance Response Team (DART) operational picture in unstable theaters. Deconfliction with US military activity. Coordination with State / DoS regional bureaus. SAR / SUR funding-stream alignment.

USAIDOFDA / BHADART

Theater COP Air Corridor Status

Faith-Based & Local NGOs

Salvation Army, Samaritan's Purse, World Vision, Catholic Relief, local FBOs

Lightweight access for the long tail of locally-trusted responders. Anonymous reporting intake lets community-trusted intermediaries surface ground-truth without attribution. Public-information broadcast for emergencies.

Salvation ArmySamaritan's PurseWorld VisionCRSLocal FBOs

Anon Reports Public WX

State EM / FEMA Region Liaison

Civilian EM tier that bridges to NGOs

FEMA Regional Administrators, state EM directors (TDEM, CalOES), city OEM, and tribal EM offices use the same dashboards as the warfighter, with NGO partners coordinated through the NGO Activation Workflow. One platform = one training pipeline, civil + military.

FEMATDEMCalOESTribal EM

EOC COP Mass-Casualty Wildfires

Capability × Feed Matrix

Humanitarian Capability	ATLAS Module	Underlying Live Feed
Wildfire awareness for relief routing	/wildfires — FIRMS map, hot-spot density, fire-line trend	NASA FIRMS (MODIS / VIIRS) + USFS InciWeb
Severe weather for evacuation timing	/weather — NWS active alerts, hurricane tracks	NOAA NWS / NHC / SPC
Earthquake / tsunami / volcano picture	/hazards — USGS event feeds, magnitude / depth filters	USGS Earthquake Hazards Program
Port disruption for relief logistics	/maritime — AIS port-call status, vessel anomaly detection	AIS (global), 56 port advisories, 21 risk zones
Air-corridor status for relief flights	/airspace — ADS-B over the operating area	ADS-B Exchange (global)
Hospital surge / mass-casualty coordination	/cram-dashboard — bed counts, EMS handoff, MCI workflows	Operator-entered + EMS-system pulls (where available)
Family reunification for displaced persons	Reunification workflow inside CRAM and EOC dashboards	Operator-entered intake + cross-NGO matching
Anonymous ground-truth reporting	/anonymous-reports — intake API for trusted intermediaries	Inbound REST; no caller-attribution stored
Theater situational awareness for cluster lead	/cop and /dod-cop — COP at appropriate classification	Multi-source fusion (read-only role for NGO)
Common training across civil + military responders	/sandbox — exercise mode, same code path as live	Same platform, "train as we fight"

What NGO / Humanitarian Roles GET

Read access to global open-source feeds: ADS-B, AIS, NOAA, USGS, FIRMS, NWS, NHC.
Read access to the Common Operating Picture at appropriate classification (un-redacted humanitarian / open-coalition tiers).
Write access to the reunification workflow (NGOs are often the first to register displaced persons).
Write access to the anonymous-reports intake (locally-trusted intermediaries surface ground-truth without attribution).
Read & comment access to the hospital / EMS coordination dashboard (medical NGOs need to see and contribute to the operating picture).
Read access to the public-broadcast queue (so NGO field teams can hear what's being told to the population).
Read access to the deconfliction overlay where it intersects their area of operations.
Same training pipeline as government partners — exercise mode is the same code path as live.

What Humanitarian Roles DO NOT GET

No fire-mission generator. The /api/firemission and CFF/AFATDS/VMF generation surfaces are not exposed to humanitarian roles.
No ballistic solver UI. /ballistics is gated to military / interagency roles only.
No operator-detection capability. /operator-detection and /api/operator/search are not exposed; humanitarian users do not need (and must not have) operator back-projection tooling.
No targeting layer. The kill-web and kill-chain-simulation surfaces are not exposed.
No engagement-authority workflows. The dual-key Engagement Safety Gate is not visible.
No classified-source-attributed feeds. Where ATLAS ingests classified material at higher-tier deployments, humanitarian roles see only open-source-equivalent layers.
This separation is enforced by the role-based access policy (ECHELON_ACCESS, see server/public/js/global-nav.js) and by route-level middleware on the kinetic endpoints.

Coalition & STANAG Interoperability

When humanitarian operations occur alongside coalition military activity, deconfliction context is shared via the same NATO STANAG-cited modules ATLAS uses internally:

STANAG 4082 — standard ballistic met-message format (so weather data crosses cleanly between coalition and humanitarian operations).
STANAG 4355 — NATO Modified Point Mass trajectory model (military side; not exposed to NGO roles, but cited so coalition partners know we're coherent).
STANAG 4633 — thermal signature standard (relevant where NGOs operate near search-and-rescue or military thermal sensors).
STANAG 4586 / 5516 / 4676 — UAS / Link 16 / NATO ground-track interoperability.
CoT / TAK / ATAK / WinTAK / iTAK — lightweight track exchange that NGO field teams can join with a tablet.
MIL-STD-2525D — standard symbology so coalition and NGO operators see the same symbols.

Doctrine anchor: ATLAS Platform Scope — Strategic / Operational / Tactical / Joint / NGO (v1.0) · covers strategic, operational, tactical, joint multi-service, interagency (CBP / DEA / DHS / FBI / DoS / FEMA / USAID), NGO & humanitarian, and coalition reach. The humanitarian section of that doctrine is the canonical source for what is and is not exposed at the humanitarian access tier.

Why this layer exists: NGOs operate in many of the same physical spaces as militaries and disaster-response agencies. Humanitarian organizations cannot accept being near a system that gives them a fire-mission button, even by accident — so the kinetic surface is firewalled from this access tier. At the same time, humanitarian organizations save lives faster when they can see the same disaster picture, route logistics on the same port and weather data, and reunite families using the same workflow as their government partners. ATLAS is built so both can be true at once.

BRIEF CHEATSHEET

TF DAGGER · ONE FIGHT · 9 STEPS

UNCLASSIFIED // FOR OFFICIAL USE ONLY

Greg Funk Teams brief · 29 APR 2026 1000 EDT · ISS LLC / Dr. Terry Flood / CAGE 9VKK3

OPENING (30 sec)

"One fight, one screen. TF DAGGER, hostile UAS swarm bearing 270, 22km. PTDS-1 has it. ALPHA-1 through 8 are airborne, BRAVO-6 is C-RAM, CHARLIE-1 is on shore, LOG-1 is the tail. I'm going to walk you the kill chain end to end — sensor to shooter to BDA — in nine steps."

THE 9 STEPS · CLICK EACH

1. DETECT — Swarm C2

"PTDS-1 picks up 4 hostile UAS. ALPHA-1..8 receive cue at H+0."

2. CLASSIFY — CRAM Dashboard

"BRAVO-6 confirms hostile UAS, declares THREATCON RED at H+1."

3. FUSE — DoD Common Op Picture

"All four domains on one screen. Land/air/sea/cyber. No swivel-chair."

4. EXTEND — Maritime Domain

"CHARLIE-1 sees the surface threat. AIS + radar + visual cross-cue."

5. PRIORITIZE — Commander Dashboard

"Critical/High/Med/Low live counts. Commander sees the queue."

6. ASSESS — DIME-PMESII

"Operational Environment overlay. Diplomatic / Info / Mil / Econ options."

7. LOCATE — Peer Geolocation

"GPS-denied. Multi-node TDOA. Covariance ellipse on the map."

8. DECIDE — Intel Fusion

"AI never authors lethal numbers. Human-in-loop for every kinetic call."

9. ACT + BDA — Brief Runbook (full script)

"LOG-1 closes the loop. BDA back to PTDS-1. One fight, one screen."

SLIDE QUICK-JUMP · DEFENSE BRIEFING DECK

Echelon Break — Strategic / Op / Tactical / Edge

Navy / USMC — EABO, Stand-In Force, POSEIDON

Army — ADOC complement, BCT-down, ATAK

Air Force — ABMS, ACE, AOC-edge node

Space Force — SDA, LEO-PNT, Spectrum/EW

Firestorm Labs — xCell + Tempest + Swarm C2

Link 16 / J-Series / COMSEC posture (plain English)

This Week · What's Done / In Flight / On Deck

Single source of truth post-Greg-Funk brief. POC targets (Jaded Thunder Visceral, Booz Allen, EUD) tracked here, not as sales slides.

IF ASKED: LINK 16 / COMSEC — PLAIN ENGLISH

If you only remember one line:
"We don’t transmit on Link 16, and we don’t hold the secret keys. We read a translated unclassified copy that the unit’s government-owned translator box hands us."

If pressed for more:
• Link 16 is the military’s classified group-chat for jets, ships, ground — you need an encrypted radio (MIDS) and the day’s secret keys to talk on it. We have neither. We don’t need either.
• The unit’s person who safeguards those keys (the COMSEC custodian) keeps that job. We change nothing about their security setup.
• The unit also has a government-owned translator box that copies Link 16 messages to the unclassified side. We read from that box. We never write back into the secret side.
• What we add: we mix those tracks with our 9,500+ aircraft and 12,000+ ship feeds onto one map and give the commander a clean picture with a decision queue.
• If the translator goes dark we keep running on commercial feeds and clearly label the Link 16 picture as stale. No silent failures.

Why it matters to them: "Days to stand up, not 18 months. No new accreditation. No new keys. No new custodian. Their security chain is unchanged."

HARD RULES — SAY THESE

• "No FedRAMP, no IL-5, no CAC, no SIPRNET, no FIPS, no ATO — this is unclas commercial."
• "AI never authors ballistic numbers. Lethal calls are human-in-loop."
• "Grounded on our in-house intel engine — — docs in the live RAG floor (count from /api/intel/corpus/stats), fed by 30+ purpose-built ingest adapters (CIA Factbook 261 countries, NOAA/USGS hazards, CISA KEV cyber, AISStream maritime, DoD DSIP, NSF/DARPA pipelines, USAspending, GDELT, drone-intel, more). Every claim is [GREEN]/[AMBER]/[RED] tagged with verbatim citations — this is the anti-hallucination floor."
• "CAGE 9VKK3."

CLOSING (15 sec)

"That's the kill chain. One screen, nine steps, every domain. Vendor-locked battle-management software gives you a map; we give you the fight. Cost? A fraction of a prime program. Standards? Open. Schedule? Today. Let me know what you want to drill into."

Press ESC or click X to close · Drawer is overlay-only, won't navigate away