---
title: "Protocol overview | Observatory Protocol"
description: "Observatory Protocol 0.1: the open specification of how an instrument joins a grid, proves what it is, keeps time and publishes what it measures…"
url: https://nexusobservatory.com/overview/
publisher: GCRI Canada
updated: 2026-11-18
---

Observatory Protocol 0.1 · overview

# The protocol at a glance.

How an instrument that has never met the grid joins it, proves what it is, keeps time and publishes what it measures, with provenance, uncertainty and quality on every value. Open to every implementer, changed in public.

**Version**: 0.1.0-draft
**Status**: Draft specification
**Specification**: CC BY 4.0
**Code**: Apache-2.0
**Steward**: GCRI Canada
**Source**: obsp-0.1-foundation

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

[Check a document](https://nexusobservatory.com/conformance/checker/)

## Status of this document

**Observatory Protocol 0.1.0-draft is a draft specification.** Any part of it may change before version 1.0, and until then a minor version may break compatibility.

Nothing on this site states that an implementation conforms to it. A conformance claim states its tested scope and cites its evidence.

Protocol development is stewarded by GCRI Canada, lead organisation of the Nexus Consortium.

## Conventions

The key words MUST, MUST NOT, REQUIRED, SHOULD, SHOULD NOT and MAY are used as in RFC 2119 and RFC 8174 when they appear in capitals.

Clauses and figures are numbered on every page. A clause marked Informative explains. Every other clause of the specification is normative.

## Start where your work is.

Read the text, explore the contracts, check a document, or build against the bindings.

- [Text **Specification** Scope, principles, functions, states, objects and flows.](https://nexusobservatory.com/spec/)
- [Explore **Schemas** Every object as an open JSON schema, field by field.](https://nexusobservatory.com/schemas/)
- [Check **Conformance checker** Validate a document against its schema, in your browser.](https://nexusobservatory.com/conformance/checker/)
- [Build **SDK quickstarts** Validate, compute digests and run the conformance suite.](https://nexusobservatory.com/sdk/)
- [Decide **Governance** How a proposal becomes part of the protocol.](https://nexusobservatory.com/governance/)
- [Join **Contribute** Propose a change, report a defect, translate, learn.](https://nexusobservatory.com/contribute/)

## A lineage of shared observation.

Every element of the protocol answers a problem that observing communities have already met: how to make measurements comparable, how to federate networks without surrendering them, how to agree on time, and how to keep the conditions of a measurement attached to its value.

Traditions the protocol continues

1. 1854 The observation as a public instrument Vice-Admiral Robert FitzRoy founded the Met Office in 1854. The national weather service that followed rested on a premise this specification inherits: an observation becomes useful to others only when the conditions of its making are known and shared. \[1\]
2. 1881–1884 Coordinated campaigns The International Polar Year, inspired by Karl Weyprecht, took place from 1881 to 1884 as a series of coordinated international expeditions to the polar regions. It established that comparable measurement across sites is a matter of agreed method before it is a matter of instruments. \[2\]
3. WMO Global observing as a system The World Meteorological Organization’s Global Observing System collects weather, climate, water and environmental data from satellites and surface stations, and is now part of WIGOS, the overarching framework for all WMO observing systems. WIS 2.0 carries the exchange of those data onto open standards and Web technologies. The protocol treats these frameworks as the reference for describing stations and publishing their data. \[3\]\[4\]\[5\]
4. Federations Networks of networks The International Federation of Digital Seismograph Networks unites the groups responsible for installing and maintaining seismographs in their own regions. The International GNSS Service has provided open access to high-quality GNSS data products since 1994, giving access to the global reference frame, the ITRF. Each shows that a federation keeps local ownership and still yields one coherent record. The protocol’s rule of one owner per fact, and its federation function, follow that model. \[6\]\[7\]\[8\]
5. 2000 Common standards, many builders Since Argo started in 2000, its profiling floats have been built by companies and research institutions alike, all held to common standards set by an international steering team. Replaceable providers behind one shared contract is the arrangement the protocol makes normative. \[9\]
6. 1972 Observation from orbit Landsat 1 launched on 23 July 1972 and began the longest-running Earth-observation satellite programme. Copernicus is the European Union’s Earth-observation programme. Space and ground observations meet in one product only when their time, geometry and quality are stated. The protocol requires that context on every value. \[10\]\[11\]
7. Time A shared clock Coordinated Universal Time is computed by the BIPM from data contributed by timing laboratories. IEEE 1588 defines the Precision Time Protocol, and ITU-T G.8275.1 profiles it for phase and time synchronisation across networks. In the protocol, time is a function in its own right: a measurement whose clock cannot be trusted cannot be published as trusted. \[12\]\[13\]\[14\]
8. 1984 End to end, rough consensus Saltzer, Reed and Clark argued that functions placed in the network can be completely and correctly implemented only with the knowledge of the end systems; RFC 1958 recorded the principle for the Internet’s architecture. The IETF’s working method, summarised in RFC 7282 as “rough consensus and running code”, sets the standard for how an open protocol should change. The protocol keeps authority at the site and changes only through open proposals. \[15\]\[16\]\[17\]
9. Semantics Shared vocabularies for sensing The OGC SensorThings API offers an open, geospatially enabled way to interconnect sensing devices, data and applications. The W3C Semantic Sensor Network ontology, a Recommendation since 2017, gives observations, sensors and samples a common meaning. The protocol describes instruments in these terms rather than in terms of its own. \[18\]\[19\]
10. 2013–2016 Provenance and reuse The W3C PROV documents (2013) define an interchange model for provenance. The FAIR Guiding Principles (2016) ask that data be findable, accessible, interoperable and reusable. The protocol attaches provenance, uncertainty, quality and correction state to every value, so that reuse never strips the conditions of measurement. \[20\]\[21\]
11. 2023 Attested identity The IETF RATS architecture (RFC 9334) describes how one party appraises evidence about the state of another. The protocol’s Join and Admit functions apply that model to instruments: a participant begins untrusted and is admitted on evidence, not on assertion. \[22\]
12. Observatory Protocol 0.1

Figure 1Traditions the protocol continues

## The principles every function is held to.

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.

**Zero implicit trust**: A participant starts untrusted. Trust is earned by attestation, admission and evidence, and lapses on expiry or revocation.
**One owner per fact**: Each fact family has exactly one authoritative owner. A site MAY cache and continue bounded state; it MUST NOT become a silent second source of truth.
**Local first, offline is not policy-free**: Approved local operation MUST continue through loss of upstream links for the autonomy window in the plan. Expired authority, revoked identity, compromised time or missing mandatory evidence MUST force quarantine even offline.
**Typed, receipted commands**: Every consequential command carries identity, purpose, policy, authority, repeat-safe key and a receipt.
**Products keep their context**: Every value carries provenance, time, uncertainty, quality, confidence and correction state.
**Replaceable providers**: Hardware, software, cloud, radio, satellite, model, data and service providers are replaceable behind typed contracts, with a tested exit path.
**Separated planes**: Control, data, evidence and exchange planes are separate. The exchange plane MUST NOT create an inbound management path into a site.
**Each step is its own evidence**: Installation is not qualification; qualification is not observation; observation is not assessment. No state is reached by wording.
**Correction without erasure**: Records are correction-addressable. Replacement never deletes history.
**Scoped proof**: A proof proves only the claim and scope in its evidence.
**No dependency on another party**: A conforming deployment MUST be operable by its owner without any service, data or approval from another organisation, unless the owner chooses to federate.

## From first contact to retirement, function by function.

Each function moves named objects between named actors and is drawn against open standards. Select a function to read its requirements.

Functions and the objects they hand on

Join Admit Describe Time Observe Qualify Federate Orchestrate Correct Exchange Prove Exit and decommission Hardware passport Attestation evidence Attestation result Node identity and manifest Policy bundle Node bootstrap bundle Signed plan Request context Provider declaration Qualification record Admission scope key Evidence record SBOM and provenance statement Observation record Calibration record Source manifest Time and position quality Observed-state receipt Event envelope Native source evidence Replay batch Quality flags and uncertainty Provenance and lineage Confidence and status Federation binding Authority lease Fleet projection Deployment plan Reconciliation receipt Controlled release record Correction notice Product manifest Map grounding receipt Proof receipt

Functions run in lifecycle order across the top; each object is a row, drawn from the first function that moves it to the last. Select a function to read its requirements.

Function 01 of 12

### Join

A node proves what it is, receives an identity and a policy, then a signed plan. A node MUST present attestation evidence (RATS, RFC 9334, passport model) rooted in a hardware root of trust where the device class has one (TPM 2.0, DICE or a secure element), or a software root explicitly marked SOFTWARE\_ROOT otherwise. A verifier MUST bind the result to a nonce and an expiry. Identity MUST be short-lived and renewable (X.509 SVID, SPIFFE-style URI). Long-lived shared secrets MUST NOT be used. The bootstrap bundle MUST be signed by the site's enrolment key and carry the trust anchors, policy reference and the initial plan digest. Evidence: enrolment receipt, attestation result, identity issuance record.

**Objects it moves**: **Standards it is drawn against**: **Domains that rely on it**: 5G core and edge computing, Positioning, navigation and timing, Edge hardware and runtime, IoT and low-power wireless, Security, identity and supply chain, Field deployment and operations

## Watch a station join the grid.

A simulated station runs the protocol from first contact to its first published observation. Drop its link or its clock to see how it recovers.

Sample data

**Station**: Sample node
**State**: Unenrolled
**Time**: None
**Link**: Up
**Outbox**: 0
**Applied once**: 0
**Run time**: 00:00.0

Enrolment sequence

1. 01 Unenrolled 00:00.0
2. 02 Discovered
3. 03 Attesting
4. 04 Identity issued
5. 05 Policy bound
6. 06 Plan staged
7. 07 Local ready

Exception

1. — Degraded

Telemetry

Clock offset

**None** 

Outbox

**0** 

Published per minute

**0** 

−30 s now

Event log

Simulated station: the values are generated in your browser to show the order of events. They are not measurements.

State: Unenrolled

Figure 2A simulated station runs the protocol from first contact to its first published observation.

## Participants and the objects they exchange.

Every role and every object the specification defines. Open one to see the functions that use it.

12 of 30

## States are entered on evidence, never on assertion.

Select a machine, then a state, to read its transitions and the evidence each one requires.

Node enrolment

OFF THE MAIN TRACK Unenrolled Discovered Attesting Identity issued Policy bound Plan staged Local ready Quarantined Degraded Revoked

Select or focus a state to read its transitions and the evidence each one requires.

State

### Unenrolled

Entry state.

Leads to

- **Discovered** when `hardware inventory recorded`
- **Quarantined** when `bootstrap integrity failure`

Reached from

- Entry state

Figure 3Select a machine, then a state, to read its transitions and the evidence each one requires.

## Messages, in order, between real actors.

Choose a flow and step through it. Each message names the object it carries.

Enrol a node

– of 11

01 Node → Node Boot with measurement and inventory hardware and firmware Hardware passport 02 Node → Attestation verifier Send evidence and endorsements Attestation evidence 03 Attestation verifier → Bootstrap authority Return attestation result Attestation result ATTESTATION 04 Bootstrap authority → Platform policy authority Enrolment request with request context Request context 05 Platform policy authority → Bootstrap authority Allow with obligations, or deny Policy bundle 06 Bootstrap authority → Node Node identity, trust bundle and signed bootstrap plan Node bootstrap bundle SIGNED 07 Node → Node agent Start minimum local runtime 08 Node agent → Fleet controller Advertise typed capabilities Node identity and manifest 09 Fleet controller → Node agent Signed deployment plan assignment Signed plan SIGNED 10 Node agent → Node agent Reconcile and self-test Reconciliation receipt 11 Node agent → Fleet controller Acceptance evidence bundle Evidence record

Figure 4Choose a flow and step through it. Each message names the object it carries.

## Composed from open standards.

3GPP, O-RAN, ITU-T timing, IETF attestation, WMO WIGOS, OGC and STAC: the standards the protocol is drawn against. They are design references, not claims of conformity.

12 of 48

## One set of functions across observing domains.

The functions on which each observing domain relies. Select a function to open it.

Functions each observing domain relies on

Join Admit Describe Time Observe Qualify Federate Orchestrate Correct Exchange Prove Exit and decommission Satellite and non-terrestrial links Ground stations and terminals Radio access network AI-RAN shared compute 5G core and edge computing Positioning, navigation and timing Edge hardware and runtime AI models and agents Earth observation GIS, maps and twins Sensors and instruments IoT and low-power wireless Power and energy Security, identity and supply chain Data, pipelines and exchange Field deployment and operations

Figure 5The functions on which each observing domain relies. Select a function to open it.

## An open specification, changed in the open.

The protocol is open. Any party may implement it, and changes are proposed and decided in public.

**Open governance**: The Observatory Protocol is an open protocol. Any party may implement it; changes are proposed upstream, in the open, before any implementation follows them.
**Versioning**: Protocol versions are written obsp/<major>.<minor>. Until 1.0 a minor version MAY break compatibility; from 1.0 only a major version does. Contract schemas carry their own schema version.
**Change proposals**: Changes are proposed in the open as Observatory Improvement Proposals: draft, review, accepted, implemented, or withdrawn. A proposal that changes a function updates the specification, the schemas and the conformance tests together.
**Conformance levels**: Declared, self-tested, lab-tested, qualified, with suspended and withdrawn. A level is reached only with the evidence the profile names. "Conformant" describes a tested scope only; it never means an outside body has approved it.
**Not a public authority**: Warnings, emergency dispatch, regulation, spectrum assignment, insurance, conformity assessment and law enforcement stay with competent external bodies. A protocol receipt creates no legal, regulatory or financial authority.
**No token**: The protocol defines no token, coin or tradable unit.
**Architecture**: Zero trust (NIST SP 800-207): every request is authenticated, authorised and logged; network position grants nothing.
**Device identity**: Attested; hardware root where the class has one; short-lived certificates; revocation within the site's offline window.
**Workload identity**: SPIFFE-style SVIDs, rotated; no shared secrets.
**Keys**: Site keys held by the grid operator; customer-held keys for upstream services; HSM or TPM-sealed where available.
**Supply chain**: SBOM, SLSA provenance, signed artifacts, TUF update metadata, SUIT for firmware.
**Time**: Authenticated time (P3, §5.4); time integrity gates receipts.
**OT environments**: IEC 62443 zones and conduits for industrial deployments.
**Privacy**: Observation data that can identify a person is a declared data class with its own policy; default is not to collect it.
**Break glass**: Logged, time-bound, receipted.

[How changes are decided](https://nexusobservatory.com/governance/)

[Contribute](https://nexusobservatory.com/contribute/)

## The protocol at work, explained.

Scroll stories drawn from the specification: each figure is the data of the protocol, not an illustration of it.

- [Explainer **How a node joins** Identity, attestation, policy and plan, step by step.](https://nexusobservatory.com/explainers/how-a-node-joins/)
- [Explainer **Data paths** One observation from instrument to product.](https://nexusobservatory.com/explainers/data-paths/)
- [Explainer **Conformance levels** Declared to qualified, each on evidence.](https://nexusobservatory.com/explainers/conformance-levels/)
- [Explainer **Federation** From one node to federated grids.](https://nexusobservatory.com/explainers/federation/)
- [Explainer **Lineage** The practice of shared observation the protocol continues.](https://nexusobservatory.com/explainers/lineage/)
- [Explainer **Open schemas** One contract, read the same way by every implementer.](https://nexusobservatory.com/explainers/open-schemas/)

## References

Sources for the historical and standards statements on this page.

1. Met Office. "Our history." [www.metoffice.gov.uk/about-us/who-we-are/our-history](https://www.metoffice.gov.uk/about-us/who-we-are/our-history)
2. NOAA Pacific Marine Environmental Laboratory. "The First International Polar Year: History." [www.pmel.noaa.gov/arctic-zone/ipy-1/History.htm](https://www.pmel.noaa.gov/arctic-zone/ipy-1/History.htm)
3. World Meteorological Organization. "Global Observing System (GOS)." [community.wmo.int/en/activity-areas/global-observing-system-gos](https://community.wmo.int/en/activity-areas/global-observing-system-gos)
4. World Meteorological Organization. "WMO Integrated Global Observing System (WIGOS)." [community.wmo.int/en/activity-areas/wigos](https://community.wmo.int/en/activity-areas/wigos)
5. World Meteorological Organization. "WMO Information System (WIS) and WIS 2.0." [community.wmo.int/en/activity-areas/wis](https://community.wmo.int/en/activity-areas/wis)
6. International Federation of Digital Seismograph Networks. "About the FDSN." [www.fdsn.org/about/](https://www.fdsn.org/about/)
7. International GNSS Service. "About the IGS." [igs.org/about/](https://igs.org/about/)
8. IGN, ITRF Product Center. "International Terrestrial Reference Frame." [itrf.ign.fr/en/homepage](https://itrf.ign.fr/en/homepage)
9. Argo Program. "About Argo." [argo.ucsd.edu/about/](https://argo.ucsd.edu/about/)
10. NASA. "Landsat 1." [landsat.gsfc.nasa.gov/satellites/landsat-1/](https://landsat.gsfc.nasa.gov/satellites/landsat-1/)
11. European Union. "Copernicus." [www.copernicus.eu/en](https://www.copernicus.eu/en)
12. Bureau International des Poids et Mesures. "Realizing and disseminating international reference time scales: UTC, UTCr and TT(BIPM)." [www.bipm.org/en/time-ftp](https://www.bipm.org/en/time-ftp)
13. IEEE Std 1588-2019. "IEEE Standard for a Precision Clock Synchronization Protocol for Networked Measurement and Control Systems." [doi.org/10.1109/IEEESTD.2020.9120376](https://doi.org/10.1109/IEEESTD.2020.9120376)
14. ITU-T Recommendation G.8275.1. "Precision time protocol telecom profile for phase/time synchronization with full timing support from the network." [www.itu.int/rec/T-REC-G.8275.1](https://www.itu.int/rec/T-REC-G.8275.1)
15. Saltzer, J. H., Reed, D. P., and Clark, D. D. (1984). "End-to-End Arguments in System Design." ACM Transactions on Computer Systems 2(4). [web.mit.edu/Saltzer/www/publications/endtoend/endtoend.pdf](https://web.mit.edu/Saltzer/www/publications/endtoend/endtoend.pdf)
16. Carpenter, B., ed. (1996). RFC 1958, "Architectural Principles of the Internet." IETF. [www.rfc-editor.org/rfc/rfc1958](https://www.rfc-editor.org/rfc/rfc1958)
17. Resnick, P. (2014). RFC 7282, "On Consensus and Humming in the IETF." IETF. [www.rfc-editor.org/rfc/rfc7282](https://www.rfc-editor.org/rfc/rfc7282)
18. Open Geospatial Consortium. "OGC SensorThings API." [www.ogc.org/standards/sensorthings/](https://www.ogc.org/standards/sensorthings/)
19. W3C (2017). "Semantic Sensor Network Ontology." W3C Recommendation, 19 October 2017. [www.w3.org/TR/vocab-ssn/](https://www.w3.org/TR/vocab-ssn/)
20. W3C (2013). "PROV-Overview: An Overview of the PROV Family of Documents." W3C Working Group Note, 30 April 2013. [www.w3.org/TR/prov-overview/](https://www.w3.org/TR/prov-overview/)
21. Wilkinson, M. D., et al. (2016). "The FAIR Guiding Principles for scientific data management and stewardship." Scientific Data 3, 160018. [doi.org/10.1038/sdata.2016.18](https://doi.org/10.1038/sdata.2016.18)
22. Birkholz, H., et al. (2023). RFC 9334, "Remote ATtestation procedureS (RATS) Architecture." IETF. [www.rfc-editor.org/rfc/rfc9334](https://www.rfc-editor.org/rfc/rfc9334)
23. Bradner, S. (1997). RFC 2119, "Key words for use in RFCs to Indicate Requirement Levels." IETF. [www.rfc-editor.org/rfc/rfc2119](https://www.rfc-editor.org/rfc/rfc2119)
24. Leiba, B. (2017). RFC 8174, "Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words." IETF. [www.rfc-editor.org/rfc/rfc8174](https://www.rfc-editor.org/rfc/rfc8174)

On this page

1. Status of this document
2. Conventions
3. Start where your work is.
4. A lineage of shared observation.
5. The principles every function is held to.
6. From first contact to retirement, function by function.
7. Watch a station join the grid.
8. Participants and the objects they exchange.
9. States are entered on evidence, never on assertion.
10. Messages, in order, between real actors.
11. Composed from open standards.
12. One set of functions across observing domains.
13. An open specification, changed in the open.
14. The protocol at work, explained.
15. References

- [View the source](https://nexusobservatory.com/development/text/)
- [Report a defect](https://nexusobservatory.com/development/take-part/)
- [Propose a change](https://nexusobservatory.com/development/proposals/)
- [Changes](https://nexusobservatory.com/governance/changes/)
