SHIELD/ATLAS · Technical Data Package · TDP-C2-001 · Rev A · 2026-10-06

Third-Party C2 Integration — Technical Data Package

Prepared for platform OEMs, sensor-node providers, C-UAS exercise integrators, and government C2 evaluators. Machine-readable catalog: /api/c2-tdp. Live proof index below — every link is checkable right now.

Scope — read this first. SecureAssure (SHIELD/ATLAS) is the C2 / COP integration and decision layer: multi-source ingestion, fused single picture, human authority gates, custody and audit, and third-party C2 handoff. We are not an airframe, sensor, effector, or hardware-node prime, and this package makes no such claim.

Integration roles

Platform OEM teammate — you own the aircraft/vehicle and payloads; we own the C2/COP decision layer and the third-party C2 interface your platform plugs into.
Sensor-node provider — your node's feeds enter through the admission gate; the fused picture and custody chain are ours.
C-UAS exercise integrator — we bring the common picture, track custody, and evidence capture to an exercise; you bring the fielded systems and range.
Government C2 evaluator — every claim on this page links to a live endpoint you can verify yourself; no claims without proof.

Data flow (integration architecture)

1 · Source feed
(ADS-B / AIS / TAK-CoT / sensor) → 2 · Admission gate
(accept / refuse + reason) → 3 · Custody ledger
(source, time, provenance) → 4 · Fused single picture
(multi-modal track fusion) → 5 · Human authority gate
(approval before effect) → 6 · External C2 / SDK handoff
(TAK/CoT, RAS C2 SDK)

Steps 2 and 3 are the custody spine: every track carries where it came from, when it was admitted, and what was refused — the audit trail an evaluator or accreditation officer asks for first.

Interface catalog — live proof endpoints

Proof point	Endpoint	What it demonstrates
Platform health	`GET /api/health`	Operational status, module count, deployed git SHA (verifies you are looking at the real build)
Orchestration status	`GET /api/platform/symphony-status`	Module orchestration and subsystem state
RAS C2 SDK lane	`GET /api/ras/c2-sdk/status`	Robotics and Autonomy Systems C2 SDK integration status (Army UAS Marketplace lane)
Agentic decision proof	`GET /api/genome/session-start`	Schema-driven, human-controlled decision session start (Army SBIR R6 agentic decision management mapping)
Fusion engine	`GET /api/fusion/status` · `GET /api/fusion/tracks`	Multi-modal track fusion status and the current fused track set
TAK/CoT bridge	`GET /api/tak/statistics` · `GET /api/tak/snapshot`	Cursor-on-Target interoperability statistics and current snapshot
Evidence packets	`GET /api/packet/em`	Signed evidence-packet generation (custody/audit artifact)
Operator surfaces	`/cop` · `/fires` · `/workspace` · `/swarm-c2`	Common Operating Picture, fires loop, workspace, swarm C2 console
Evaluator view	`/evaluate/reviewer`	Reviewer-facing evidence and scoring surfaces

Opportunity mapping — what we fit, and what we do not

Pursuit	Fit	Honest position
Army SBIR R6 — Agentic-AI, Schema-Driven Decision Management (ARM26BX06-NV012)	FIT	Schema-driven, signer-ready decision packages with human control, custody, and audit. Proof: `/api/genome/session-start`.
AFRL AI & NGC2 BAA (distributed C2, decision support)	FIT	Decision/integration layer is the core product; third-party C2 interfaces documented above.
Army UAS Marketplace — C2 SDK lane (RAS)	FIT	RAS C2 SDK status, swarm C2 console, and this TDP form the integration package. Proof: `/api/ras/c2-sdk/status`, `/swarm-c2`.
xTech\|Search 10 / JIATF CMO C2	FIT	C2/COP decision layer with evidence custody; this TDP strengthens the evaluator package.
DAF26BX06-DP027 — C-sUAS D2P2	PARTIAL	Single-track fusion: supported as software architecture and live proof (`/api/fusion/tracks`). External API commands: supported. Medusa C2: adapter target only — not integrated (third-party C2 mapping). Hardware/environmental node requirements: partner or evidence gap we do not claim.
Project Flytrap 6.0 (C-UAS exercise)	PARTIAL	We bring the picture, custody, and evidence capture; exercise participation still requires a concrete fielded C-UAS demo package.
DIU LC-ISR Prize Challenge	TEAMMATE ONLY	Teammate lane only — third-party C2 TDP, MOSA/AVO attributes. No airframe, no fly-off claim. This page is what a platform OEM evaluates us on.

How a platform OEM integrates

Feed contract — send tracks/events over TAK/CoT or JSON to the admission gate; the gate accepts or refuses with a machine-readable reason.
Custody — every admitted item is ledgered (source, time, provenance) before it can influence the picture.
Fusion — your feed fuses into the single picture alongside the other modalities; per-source contribution stays inspectable.
Authority — effects-producing actions queue behind the human authority gate; nothing fires on model output alone.
Handoff — approved actions and picture updates flow out via the external C2/SDK surface (TAK/CoT out, RAS C2 SDK).

Security and honesty boundaries

CUI boundary: this public instance carries demo/live public-source data only — no classified, no CUI. A CUI enclave is a separate deployment conversation.
TLS posture: TAK/CoT endpoints with unverifiable TLS are refused, not bypassed — failure is surfaced, never silently accepted.
Labels: data surfaces carry DEMO / LIVE / TRAINING labels so an evaluator never mistakes synthetic for real.
Human control: harm-capable actions require explicit human approval; the authority gate is the last step, not a rubber stamp.
No-vaporware rule: anything on this page without a working link is labeled a gap (see the PARTIAL rows above). We do not claim Medusa C2, DP027 compliance, flight readiness, or hardware-node validation.

SHIELD/ATLAS · Integrated Services & Solutions LLC · TDP-C2-001 Rev A · 2026-10-06 · Machine-readable catalog: /api/c2-tdp · Gateway: secureassure.app · Door catalog: /doors

BRIEF CHEATSHEET

TRAINING SCENARIO · ONE FIGHT · 9 STEPS

UNCLASSIFIED // FOR OFFICIAL USE ONLY

Reusable unclassified ATLAS demonstration · 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

Internal pursuit notes — confirm current status and permissions before sharing with external evaluators.

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: "Prototype integration can be demonstrated without access to cryptographic keys; operational deployment still requires agency approval, interface validation, and applicable security authorization."

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 — the live RAG corpus (verify current corpus inventory), 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

Third-Party C2 Integration — Technical Data Package

Integration roles

Data flow (integration architecture)

Interface catalog — live proof endpoints

Opportunity mapping — what we fit, and what we do not

How a platform OEM integrates

Security and honesty boundaries

What This Page Is

What To Do First

Need Help?

Use My Location?