---
title: "Technical | Observatory Protocol"
description: "The Observatory Protocol lets an instrument or computer that has never met the grid join it, prove what it is, keep time, publish what it measures with its metadata and quality, and be orchestrated, corrected, federated and finally retired, without trusting any single vendor, cloud or central service."
url: https://nexusobservatory.com/technical/
publisher: GCRI Canada
updated: 2026-11-18
---

1. [Observatory Protocol](https://nexusobservatory.com/)
2. Technical

# One contract, from first contact to retirement.

The Observatory Protocol lets an instrument or computer that has never met the grid join it, prove what it is, keep time, publish what it measures with its metadata and quality, and be orchestrated, corrected, federated and finally retired, without trusting any single vendor, cloud or central service.

[Read the specification](https://nexusobservatory.com/spec/)

[Explore the schemas](https://nexusobservatory.com/schemas/)

**Functions**: 12
**Objects**: 41
**Participants**: 33
**State machines**: 12
**Flows**: 12

Architecture

## Functions, planes and domains.

Functions say what happens; planes say how it travels; domains say where it runs.

1. **Join** A node proves what it is, receives an identity and a policy, then a signed plan.
2. **Admit** Providers enter by manifest, rights, security and technical review, for a stated scope.
3. **Describe** Every instrument and observation carries what, where, how and by whom.
4. **Time** One time base across the grid, with time quality as explicit state.
5. **Observe** Streams and files move over whatever link the site has, with store and forward.
6. **Qualify** Quality flags, calibration and provenance travel with each value.
7. **Federate** Nodes form cells, cells form clusters, and clusters federate across trust domains.
8. **Orchestrate** Software, configuration and upgrades roll out by signed plan, with evidence for every change.
9. **Correct** An upstream correction marks dependants stale, triggers recompute and publishes a new version.
10. **Exchange** Governed products reach people and applications through versioned APIs, events, maps and exports.
11. **Prove** Peers answer unpredictable challenges and emit signed proof receipts for an independent verifier.
12. **Exit and decommission** Every material provider has an open export and replacement path, and decommissioning closes the record.

Interfaces

## One binding per plane.

| Plane | Binding |
| --- | --- |
| Control | TLS 1.3 with mutual authentication; protobuf messages over gRPC or HTTP/2. |
| Data, in the field | MQTT 5 with Sparkplug B; connectors for LoRaWAN, OPC UA and instrument buses. |
| Data, site to upstream | At-least-once publication with repeat-safe keys over the control channel or NATS JetStream; QUIC MAY be used on lossy links. |
| Events | Event envelopes mapped to CloudEvents 1.0; channels described in AsyncAPI 3. |
| Exchange | OpenAPI 3.1; the OGC API family; SensorThings; STAC; WIS 2.0. |
| Evidence | DSSE-signed in-toto statements; SLSA provenance; SCITT transparency receipts. |
| Telemetry | OpenTelemetry OTLP. |

[Protocol of protocols](https://nexusobservatory.com/architecture/)

Data model

## What passes between participants.

- [**Objects** Every object the functions move, each a published schema. Objects41](https://nexusobservatory.com/spec/objects/)
- [**Participants** The roles the protocol defines. Participants33](https://nexusobservatory.com/spec/participants/)
- [**State machines** States are entered on evidence, never on assertion. State machines12](https://nexusobservatory.com/spec/states/)
- [**Flows** Messages, in order, between participants. Flows12](https://nexusobservatory.com/spec/flows/)
- [**Schemas** Every object as an open JSON schema, explored field by field.](https://nexusobservatory.com/schemas/)
- [**Standards** Composed from open standards. Open standards48](https://nexusobservatory.com/spec/standards/)

Technology domains

## Sixteen domains, one set of functions.

- [**Satellite and non-terrestrial links** Provider-neutral terminal and provider binding, PNT and time references, store-and-forward through outages, NET routing. Functions4 Use cases10](https://nexusobservatory.com/technical/domains/satellite/)
- [**Ground stations and terminals** Bind provider and terminal, validate metadata and checksums, deliver or buffer, measure quality and correct outage or ephemeris data. Functions4 Use cases0](https://nexusobservatory.com/technical/domains/ground/)
- [**Radio access network** Replaceable O-RAN functions with conformance evidence, time synchronization, rApp and xApp manifests under SMO workflows; no spectrum authority claimed. Functions4 Use cases6](https://nexusobservatory.com/technical/domains/ran/)
- [**AI-RAN shared compute** Model evaluation and admission, deadline classes ahead of best-effort AI, accelerator scheduling with policy and human guard. Functions4 Use cases0](https://nexusobservatory.com/technical/domains/airan/)
- [**5G core and edge computing** Bootstrap core trust and register network functions, admit edge applications, place at site with local breakout, relocate and withdraw. Functions4 Use cases13](https://nexusobservatory.com/technical/domains/core/)
- [**Positioning, navigation and timing** Source ensemble, holdover and TimeQuality propagation; timing integrity is a mandatory check before LOCAL\_READY and its failure quarantines. Functions3 Use cases0](https://nexusobservatory.com/technical/domains/timing/)
- [**Edge hardware and runtime** Hardware inventory and attestation, OEM admission, runtime update plans and rollback points, cluster placement without moving authority to a cloud. Functions4 Use cases7](https://nexusobservatory.com/technical/domains/edge/)
- [**AI models and agents** Model admission with rights and evaluation, drift observation, deployment binding and rollback; model capability never grants tool or institutional authority. Functions3 Use cases0](https://nexusobservatory.com/technical/domains/ai/)
- [**Earth observation** STAC catalogue and acquisition, checksum and rights, calibration and quality masks, analysis-ready products and export. Functions4 Use cases0](https://nexusobservatory.com/technical/domains/eo/)
- [**GIS, maps and twins** Spatial identity and CRS binding, spatial uncertainty, map grounding receipts, OGC and STAC publication, invalidation on correction. Functions4 Use cases0](https://nexusobservatory.com/technical/domains/gis/)
- [**Sensors and instruments** Sensor passport, calibration, sampling plan and procedure; timed observations buffered locally with quality and uncertainty. Functions4 Use cases23](https://nexusobservatory.com/technical/domains/sensors/)
- [**IoT and low-power wireless** Onboard devices with unique identity, qualify radio and region, route telemetry, update safely and retire. Functions4 Use cases9](https://nexusobservatory.com/technical/domains/iot/)
- [**Power and energy** Measure source quality and record energy and outage evidence; shed noncritical workloads and restore in priority order while keeping control and evidence services. Functions2 Use cases15](https://nexusobservatory.com/technical/domains/power/)
- [**Security, identity and supply chain** Workload and device identity, attestation, SBOM and provenance gates, signed releases, key rotation and revocation, scoped proofs. Functions4 Use cases0](https://nexusobservatory.com/technical/domains/security/)
- [**Data, pipelines and exchange** Source and distribution manifests, native evidence landing, quality reports and lineage, correction notices, governed APIs and events. Functions5 Use cases3](https://nexusobservatory.com/technical/domains/data/)
- [**Field deployment and operations** Enrol nodes and capture as-built evidence, offline field observation with local time quality, commissioning acceptance, decommission and data return. Functions4 Use cases11](https://nexusobservatory.com/technical/domains/field/)

Conformance

## Profiles and levels.

A level is reached only with the evidence the profile names, produced by the open conformance tool or a qualified laboratory. "Conformant" describes a tested scope only; it never means an outside body has approved it.

| Profile | Functions | For |
| --- | --- | --- |
| OBSP-NODE | Join, Describe, Time, Observe, Qualify, Orchestrate (apply), Exit | Node agents and devices |
| OBSP-SITE | OBSP-NODE plus Admit (local), Orchestrate (plan), Correct, Prove (verifier) | Site controllers |
| OBSP-GRID | OBSP-SITE plus Federate and Exchange | Cluster and grid control planes |
| OBSP-PROVIDER | Admit, Describe, Exit | Hardware, software, model and data providers |
| OBSP-CONSUMER | Exchange, Correct (subscribe) | Applications reading products |
