Connect integrations with Gateway Fabric
Place external protocol adapters at the Mission boundary while preserving independent entity, event, and telemetry paths.
Deploy the integration adapter as a separately authorized peer near the sensor, on the Gateway Fabric host, or on another approved host. The adapter translates external data into Mission types. Sharing a host does not remove its identity and authorization requirements.
Choose the product boundary
| Integration goal | Product and ownership |
|---|---|
| Build a separate application with its own entities and authority | Platform. The application owns its schema and capabilities |
| Make observations visible as Tracks in Atlas Mission | Mission. The adapter maps to Mission Track types and scope |
| Exchange an external wire format such as Cursor on Target | An application-owned protocol adapter. Neither gateway startup nor peer encryption performs the translation |
| Consume Mission detections and telemetry | An authorized Mission peer with its own event and stream subscriptions |
An independent Platform application can run an always-on peer without Mission admission or Gateway Fabric. Platform transports defines that boundary.
Keep the three data paths independent
Use these paths to distinguish a synchronization failure from a notification or telemetry failure:
External sensor
|
Application-owned adapter and Mission identity
|
+-- Local durable Track save -- peer synchronization -- saved state
|
+-- Detection with entity and optional stream reference -- notification
|
+-- Advertised telemetry -- authorized consumer subscription -- live samples
Each path can use a direct authorized peer route. Gateway Fabric participates when the selected topology and policy use it for persistence, forwarding, or an allowed fallback. It is not a mandatory round trip before a detection or subscription.
The Platform event and stream chapters define publication outcomes, descriptor ownership, authorization, cancellation, and reconnect behavior. Mission supplies TrackDetected, TrackTelemetryV1, and their domain meaning.
Consume without blocking other detections
A consumer handles the detection's observation immediately. It schedules entity resolution and live subscription as separate bounded tasks. It does not await one Track's entire telemetry lifetime inside the event receive loop.
Every consumer opens its own authorized subscription. The event carries a descriptor reference, not a shared active subscription or secret. Canceling one consumer's subscription does not cancel another consumer's work.
A notification without a stream reference still supports notification handling and asynchronous entity resolution. Absence of that reference does not revoke a previously opened subscription. An explicit end or descriptor replacement controls that lifetime.
After disconnection, read current durable state and discover a current stream. Missed live samples and notifications do not automatically become replayable database records. Report unavailable live delivery when no allowed route exists.
Transport selection is not protocol translation
The Fabric WebSocket listener carries the Atlas protocol over a stream. The embedded MQTT broker uses Atlas identity and topic rules. Neither listener accepts arbitrary sensor JSON and converts it into Mission entities.
An external sensor that does not speak Atlas needs an adapter. The adapter owns parsing, input authentication, schema mapping, stable external-ID mapping, unit conversion, timestamp handling, and local error handling. Atlas identity on the adapter's peer connection does not authenticate the original sensor automatically.
For each deployment, record:
- The external protocol and schema revision.
- The adapter's identity and allowed Mission scope.
- The mapping to durable state, notification payloads, and telemetry samples.
- The direct route and any approved gateway or relay fallback.
- Buffer limits, input rejection behavior, and cancellation ownership.
- The exact product versions or documentation contract edition used.
Adapter execution and ownership
The integration application owns the adapter process, external credentials, input validation, subscriptions, lifecycle, and outbound connection policy. Gateway Fabric does not register a hardware driver or start an adapter from a guessed plugin entry.
Use the Mission SDK's Rust or Dart surface for Mission types. Platform supports Rust, Python, Kotlin, Swift, browser TypeScript, and Dart for independent applications. Carrier portability does not add Mission bindings.
Bound input queues, source mappings, pending publications, and consumer workers separately. On receiver reject-overflow, report CapacityExceeded once, discard pending receiver items, and end delivery. Later receives return Closed. Cancel the receiver and cancel and join its owned workers without stopping other consumers.
On shutdown, stop input admission, close owned stream publishers, cancel consumer subscriptions, and join adapter workers. Retain committed state and stable source mappings according to policy.
Gateway Fabric HTTP boundary
The operator interfaces are the documented health, readiness, and monitoring routes. They are not an entity or team CRUD service.
Do not infer /v1 entity or team routes from an integration example, a PDF, an unused interface, or a listener name. Use the selected product's SDK reference and gateway configuration for the actual interface contract. Any separate HTTP integration contract needs its own reviewed operations, schemas, errors, authorization, and version provenance before a client depends on it.
A software consumer receiving telemetry does not prove physical effector control. Hardware integration, action authorization, fail-safe behavior, and operator approval remain explicit external responsibilities. A data subscription is not an action command.