SEC
Secure by design
Condor authenticates peers and protects network traffic. MMGR applies identity, permission, and authority checks to mission operations.
Technology
Local communications. Distributed mission services.
BLK_MTN combines field radios, multi-hop networking, self-hosted mission services, and operator software. The architecture places communications, operational data, and trust decisions within the deployment.
MR
MarmotField hardware and edge capability
DeployCN
CondorResilient multi-hop communications
ConnectMM
MMGRTrusted mission services and coordination
CoordinateBC
BasecampOperator context and common operating picture
OperateConceptual platform relationship — not an implementation or protocol diagram.
Architecture
Local services and explicit state across changing connections.
The stack separates radio transport, mission authority, persistent state, and the operator interface. Each layer tracks its own responsibilities as peers, services, and external connections change.
INF
Infrastructure independent
The deployment architecture hosts networking and mission services locally, with external internet access as a separate dependency.
MOD
Modular architecture
Hardware, networking, mission services, and operator software remain distinct layers that can evolve together.
SH
Self-hosted capable
Organizations can retain control of operational infrastructure, services, and data.
Resilient Networking
Condor adapts multi-hop paths as links change.
Condor authenticates peers, maintains link and routing information, and selects multi-hop paths across available connections. Its delivery logic responds to changing topology and link conditions while protecting network metadata and payloads.
Conceptual reroute view
Degraded-Network Semantics
Local intent, transport progress, and confirmed outcomes are distinct.
BLK_MTN separates local intent, transport progress, delivery state, and authoritative outcome. Operators can distinguish work that is drafted, queued, transmitting, delivered, confirmed, failed, or expired instead of treating intermittent connectivity as a binary online/offline condition.
Transport stateIllustrative
Message · Team Alpha12:42:08Confirmed
Task update · Sector 312:42:33Transmitting
Plan revision · Northstar12:43:17Queued
Position request · Node 1112:43:25Queued
Distributed Trust & Authority
MMGR separates local permissions from privileged authority.
The MMGR federation architecture assigns explicit permissions to trusted sites. Local policy governs authorized work during interruptions, while current authority and trust state govern privileged changes.
01 / Identity
Authenticated participants
Operations are tied to explicit identities and assigned permissions rather than implicit network location.
02 / Authority
Controlled privilege
Privileged changes depend on current authority rather than simply accepting whichever server happens to be reachable.
03 / Recovery
State reconciliation
The recovery model reconciles trust and mission state when sites reconnect before restoring privileged access.
Federated Operation
Trusted MMGR sites share a defined administrative environment.
Multiple trusted MMGR sites can participate in one administrative environment with delegated authority, controlled handoff, and reconciliation after interruption.
MMGR Site ALocal authority
MMGR Site BTrusted peer
MMGR Site CIntermittent link
Explicit
trust state
trust state
Conceptual federation — not a consensus or certificate diagram.
Infrastructure Independence
Mission services and operational data reside within the deployment.
MMGR hosts mission services and operational state on locally controlled infrastructure. Marmot supplies field compute and radio hardware. Basecamp mapping development includes cached map packages and mission-area pinning for offline access.
Mission servicesLocal / self-hosted
Operational dataLocally controlled
Mission AO map packagePinned / offline
Remote map serviceOptional / unavailable
External internetNot assumed
Integrated from Edge to Operator
Four layers. One operational model.
Marmot brings capability into the field. Condor moves information across changing links. MMGR provides trusted mission services and authority. Basecamp turns those capabilities into an operational interface. The layers remain distinct, but they are designed to work together.
01
Deploy
Marmot provides portable field hardware for users, sites, and future airborne roles.
02
Connect
Condor provides authenticated, resilient multi-hop communications across available links.
03
Coordinate
MMGR provides identity, mission state, policy, durable coordination, and federation.
04
Operate
Basecamp provides mapping, planning, messaging, tasking, and network-aware context.
BLK_MTN Technology
Resilience is a system property, not a single feature.
Condor handles communications, MMGR governs mission state and authority, and Basecamp presents operational context. Hardware integration, offline map packaging, federation workflows, and end-to-end qualification remain under active development.