Skip to content

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.

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. JoinA node proves what it is, receives an identity and a policy, then a signed plan.
  2. AdmitProviders enter by manifest, rights, security and technical review, for a stated scope.
  3. DescribeEvery instrument and observation carries what, where, how and by whom.
  4. TimeOne time base across the grid, with time quality as explicit state.
  5. ObserveStreams and files move over whatever link the site has, with store and forward.
  6. QualifyQuality flags, calibration and provenance travel with each value.
  7. FederateNodes form cells, cells form clusters, and clusters federate across trust domains.
  8. OrchestrateSoftware, configuration and upgrades roll out by signed plan, with evidence for every change.
  9. CorrectAn upstream correction marks dependants stale, triggers recompute and publishes a new version.
  10. ExchangeGoverned products reach people and applications through versioned APIs, events, maps and exports.
  11. ProvePeers answer unpredictable challenges and emit signed proof receipts for an independent verifier.
  12. Exit and decommissionEvery material provider has an open export and replacement path, and decommissioning closes the record.

Interfaces

One binding per plane.

PlaneBinding
ControlTLS 1.3 with mutual authentication; protobuf messages over gRPC or HTTP/2.
Data, in the fieldMQTT 5 with Sparkplug B; connectors for LoRaWAN, OPC UA and instrument buses.
Data, site to upstreamAt-least-once publication with repeat-safe keys over the control channel or NATS JetStream; QUIC MAY be used on lossy links.
EventsEvent envelopes mapped to CloudEvents 1.0; channels described in AsyncAPI 3.
ExchangeOpenAPI 3.1; the OGC API family; SensorThings; STAC; WIS 2.0.
EvidenceDSSE-signed in-toto statements; SLSA provenance; SCITT transparency receipts.
TelemetryOpenTelemetry OTLP.

Protocol of protocols

Data model

What passes between participants.

Technology domains

Sixteen domains, one set of functions.

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.

ProfileFunctionsFor
OBSP-NODEJoin, Describe, Time, Observe, Qualify, Orchestrate (apply), ExitNode agents and devices
OBSP-SITEOBSP-NODE plus Admit (local), Orchestrate (plan), Correct, Prove (verifier)Site controllers
OBSP-GRIDOBSP-SITE plus Federate and ExchangeCluster and grid control planes
OBSP-PROVIDERAdmit, Describe, ExitHardware, software, model and data providers
OBSP-CONSUMERExchange, Correct (subscribe)Applications reading products