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
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.
- TextSpecificationScope, principles, functions, states, objects and flows.
- ExploreSchemasEvery object as an open JSON schema, field by field.
- CheckConformance checkerValidate a document against its schema, in your browser.
- BuildSDK quickstartsValidate, compute digests and run the conformance suite.
- DecideGovernanceHow a proposal becomes part of the protocol.
- JoinContributePropose a change, report a defect, translate, learn.
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.
- 1854The 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]
- 1881–1884Coordinated 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]
- WMOGlobal 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]
- FederationsNetworks 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]
- 2000Common 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]
- 1972Observation 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]
- TimeA 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]
- 1984End 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]
- SemanticsShared 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]
- 2013–2016Provenance 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]
- 2023Attested 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]
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.
- Join A node proves what it is, receives an identity and a policy, then a signed plan.
- Admit Providers enter by manifest, rights, security and technical review, for a stated scope.
- Describe Every instrument and observation carries what, where, how and by whom.
- Time One time base across the grid, with time quality as explicit state.
- Observe Streams and files move over whatever link the site has, with store and forward.
- Qualify Quality flags, calibration and provenance travel with each value.
- Federate Nodes form cells, cells form clusters, and clusters federate across trust domains.
- Orchestrate Software, configuration and upgrades roll out by signed plan, with evidence for every change.
- Correct An upstream correction marks dependants stale, triggers recompute and publishes a new version.
- Exchange Governed products reach people and applications through versioned APIs, events, maps and exports.
- Prove Peers answer unpredictable challenges and emit signed proof receipts for an independent verifier.
- Exit and decommission Every material provider has an open export and replacement path, and decommissioning closes the record.
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.
Participants and the objects they exchange.
Every role and every object the specification defines. Open one to see the functions that use it.
- Node A device running a conforming node agent: sensor host, edge computer, gateway, radio unit, tower.
- Site controller Local authority for a site: identity, policy, plan and buffer for its nodes; runs offline.
- Cluster Optional group of sites under one operator, sharing fleet, policy and release.
- Federation Peer A cluster or site that exchanges with another trust domain under a federation binding.
- Grid Operator The organisation that runs a site, cluster or grid and holds its keys.
- Provider Hardware, software, model, data, connectivity or service supplier entering by manifest.
- Verifier Appraises attestation evidence and proof challenges; issues receipts.
- Consumer An application or person reading products through the exchange plane.
- Steward Maintains this specification and its registries.
- NodeManifest Used in: Join, Describe.
- NodeBootstrapBundle Used in: Join.
- AttestationEvidence, AttestationResult Used in: Join.
- provider declaration Used in: Admit, Exit.
- SupplyChainReceipt (SBOM, SLSA provenance, SCITT receipt) Used in: Admit.
- QualificationRecord Used in: Admit, Qualify.
- SourceManifest, SourceRelease Used in: Describe, Admit.
- SensorPassport, CalibrationRecord Used in: Describe.
- TimeQuality Used in: Time.
- ObservationRecord Used in: Observe, Qualify.
- QualityFlag, Provenance Used in: Qualify.
- NativeEnvelope, EventEnvelope Used in: Observe, Exchange.
- ReplayBatch, ReplayBatchResult Used in: Observe.
- DeploymentPlan, Plan, SitePlan Used in: Orchestrate.
- ReconciliationAssignment, ReconciliationReceipt, ObservedStateReceipt Used in: Orchestrate.
- FleetProjection, Composition Used in: Federate.
- CorrectionNotice Used in: Correct.
- ProductManifest Used in: Exchange.
- ProofReceipt Used in: Prove.
- DecommissionRecord Used in: Exit.
- RequestContext Used in: All.
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 (node agent bootstrap) 10 states: UNENROLLED, DISCOVERED, ATTESTING, IDENTITY_ISSUED, POLICY_BOUND, PLAN_STAGED, LOCAL_READY, DEGRADED, QUARANTINED, REVOKED.
- Provider admission 10 states: DISCOVERED, MANIFEST_VALID, RIGHTS_REVIEWED, SECURITY_REVIEWED, TECHNICALLY_QUALIFIED, SOVEREIGNTY_QUALIFIED, ADMITTED_FOR_SCOPE, SUSPENDED, REVOKED, RETIRED.
- Data source admission 9 states: CANDIDATE, TERMS_REVIEWED, TECHNICALLY_PROBED, SCHEMA_PROFILED, RESPONSIBILITY_REVIEWED, CONNECTOR_VALIDATED, OBSERVING, OPERATIONALLY_ACCEPTED, SUSPENDED.
- Site connectivity and reconciliation 5 states: CONNECTED, OFFLINE, DEGRADED, RECONCILING, DISPUTED.
- Physical site lifecycle 10 states: SURVEY, DESIGN, CHAIN_OF_CUSTODY, INSTALL, POWER_NETWORK_RF_PNT_CHECKS, ENROL, ACCEPTANCE, OPERATE_MAINTAIN, REPLACE, DECOMMISSION.
- Site formation 7 states: WEDGE_NODE, PEERS_DISCOVERED, MUTUAL_TRUST, POLICY_AND_ROLES_ASSIGNED, CELL_MEMBERSHIP, SHARED_LOCAL_SERVICES, ACCEPTANCE_EVIDENCE.
- deployment plan compilation phases 14 states: parse, contract_validate, resolve_authority_refs, resolve_admitted_providers, resolve_capability_dependencies, evaluate_policy_sovereignty, construct_dependency_graph, evaluate_resources, evaluate_network_ran_timing, evaluate_data_rights_locality, evaluate_trust_prerequisites, compute_placement_candidates, assess_impact_and_exit, emit_plan.
- Reference component promotion 7 states: SCAFFOLD_ONLY, CONTRACT_BOUND, IMPLEMENTED, INTEGRATED, QUALIFIED_FOR_PROFILE, OBSERVED, ACCEPTED_FOR_SCOPE.
- Engineering promotion ladder 10 states: DECLARED, SCAFFOLDED, IMPLEMENTED, INTEGRATED, TESTED, LAB_OBSERVED, PILOT_OBSERVED, PRODUCTION_OBSERVED, INDEPENDENTLY_ASSESSED, ACCEPTED.
- Evidence and claim chain 11 states: requirement, architectureAllocation, authoredContract, implementationRevision, configuration, test, testArtifact, runtimeObservation, assessment, externalAcceptanceWhenApplicable, timeBoundedClaim.
- Model lifecycle 9 states: MODEL_ARTIFACT, RIGHTS_PROVENANCE, SUPPLY_CHAIN_SCAN, EVALUATION, RUNTIME_HARDWARE_MATCH, DEPLOY, INFERENCE, DRIFT_QUALITY, ROLLBACK_SUPERSEDE.
Messages, in order, between real actors.
Choose a flow and step through it. Each message names the object it carries.
- Enrol a node 11 messages.
- Admit a provider 10 messages.
- Publish an observation 7 messages.
- Compile a deployment plan and deliver the plan 7 messages.
- Federate sites or clusters 7 messages.
- Roll out a signed upgrade 9 messages.
- Quarantine and revoke 7 messages.
- Disconnect and replay 5 messages.
- Correct an upstream source 4 messages.
- Exit a provider 5 messages.
- Prove a peer service 5 messages.
- Authorize a request 5 messages.
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.
- IETF RATS (RFC 9334) Join and prove: reference architecture for attester evidence, verifier appraisal and attestation results.
- TCG TPM 2.0 Join: measured boot and platform root-of-trust candidate.
- DMTF SPDM Join: device authentication and measurement exchange candidate.
- DMTF MCTP and PLDM Join: platform management transport and inventory.
- SPIFFE/SPIRE Join: reference candidate for short-lived workload identity.
- SPDX Admit: software bill of materials and licence data.
- CycloneDX Admit: bill of materials and vulnerability exchange.
- SLSA Admit and orchestrate: build provenance levels.
- IETF SCITT (RFC 9943) Admit and prove: transparency receipts for statements about artifacts and evidence.
- Sigstore Orchestrate: signing and verification of released artifacts.
- in-toto Orchestrate: supply-chain step attestations.
- TUF Orchestrate: signed update metadata, named by the protocol page for upgrade roll-out.
- IETF SUIT Orchestrate: firmware update manifest architecture.
- Kubernetes Orchestrate: container scheduling baseline and dynamic resource allocation for accelerators.
- OCI image and runtime Orchestrate: portable container images and runtime.
- WMO WIGOS Describe: observing-system metadata, named by the protocol page as WIGOS metadata.
- OGC SensorThings API Describe and observe: sensing and tasking data model for sensors and observations.
- OGC API Connected Systems Describe: connected sensors, platforms and datastreams.
- OGC SensorML 3.0 Describe: sensor and procedure description.
- UCUM Describe: units of measure profile.
- IEEE 1588 (PTP) Time: precision time distribution across the grid.
- ITU-T G.8275.1 Time: telecom PTP profile with full timing support, named by the protocol page.
- IETF NTS (RFC 8915) Time: authenticated network time.
- NIST PNT cybersecurity profile Time: resilience of positioning, navigation and timing services.
- OASIS MQTT 5.0 Observe: lightweight publish and subscribe for sensor and IoT streams.
- OGC API Common Observe and exchange: shared building blocks for geospatial web APIs.
- W3C PROV-O Qualify: provenance vocabulary, named by the protocol page as W3C PROV.
- WMO-No. 8 Qualify: guide to instruments and methods of observation.
- FAIR principles Qualify: findable, accessible, interoperable and reusable data.
- 3GPP TS 23.501 Federate: 5G system architecture, named by the protocol page.
- ETSI MEC Federate: multi-access edge computing for local breakout and edge applications.
- 3GPP Release 20 Ran and core: 5G-Advanced baseline with 6G study watch.
- O-RAN Release 5 (R005) Ran: open fronthaul, E2, A1, O1 and O2 interfaces and AI/ML workflow services.
- AI-RAN Alliance publications AI-RAN: architecture and orchestration references for shared RAN and AI compute.
- CCSDS standards Satellite: candidate profiles for space mission links.
- LoRaWAN IoT: low-power wide-area gateways and devices.
- IETF QUIC Federate and prove: transport for peer and overlay links.
- OpenTelemetry OTLP Observability of every node and service through one open telemetry standard.
- CloudEvents Exchange and correct: event metadata for correction-aware subscriptions.
- AsyncAPI Exchange: event channel contracts.
- OpenAPI 3.1 Exchange: request and response API contracts.
- JSON Schema 2020-12 All functions: authored record contracts, fail-closed validation.
- STAC Exchange and describe: Earth observation asset catalogues.
- WMO WIS 2.0 Observe and exchange: weather and environmental data exchange.
- OPC UA Observe: industrial telemetry, read-only by default.
- IEC 62443 Security reference for industrial and OT integration.
- NIST SP 800-207 Security: zero-trust architecture reference.
- W3C WCAG 2.2 Operator and public surfaces: accessibility profile.
One set of functions across observing domains.
The functions on which each observing domain relies. Select a function to open it.
- Satellite and non-terrestrial links Admit, Time, Observe, Federate.
- Ground stations and terminals Admit, Describe, Observe, Qualify.
- Radio access network Admit, Time, Qualify, Orchestrate.
- AI-RAN shared compute Admit, Time, Qualify, Orchestrate.
- 5G core and edge computing Join, Admit, Federate, Orchestrate.
- Positioning, navigation and timing Time, Qualify, Join.
- Edge hardware and runtime Join, Admit, Orchestrate, Federate.
- AI models and agents Admit, Qualify, Orchestrate.
- Earth observation Describe, Observe, Qualify, Exchange.
- GIS, maps and twins Describe, Qualify, Exchange, Correct.
- Sensors and instruments Describe, Time, Observe, Qualify.
- IoT and low-power wireless Join, Admit, Observe, Orchestrate.
- Power and energy Observe, Orchestrate.
- Security, identity and supply chain Join, Admit, Orchestrate, Prove.
- Data, pipelines and exchange Describe, Observe, Qualify, Correct, Exchange.
- Field deployment and operations Join, Observe, Qualify, Exit and decommission.
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.
The protocol at work, explained.
Scroll stories drawn from the specification: each figure is the data of the protocol, not an illustration of it.
- ExplainerHow a node joinsIdentity, attestation, policy and plan, step by step.
- ExplainerData pathsOne observation from instrument to product.
- ExplainerConformance levelsDeclared to qualified, each on evidence.
- ExplainerFederationFrom one node to federated grids.
- ExplainerLineageThe practice of shared observation the protocol continues.
- ExplainerOpen schemasOne contract, read the same way by every implementer.
References
Sources for the historical and standards statements on this page.
- Met Office. "Our history." www.metoffice.gov.uk/about-us/who-we-are/our-history
- NOAA Pacific Marine Environmental Laboratory. "The First International Polar Year: History." www.pmel.noaa.gov/arctic-zone/ipy-1/History.htm
- World Meteorological Organization. "Global Observing System (GOS)." community.wmo.int/en/activity-areas/global-observing-system-gos
- World Meteorological Organization. "WMO Integrated Global Observing System (WIGOS)." community.wmo.int/en/activity-areas/wigos
- World Meteorological Organization. "WMO Information System (WIS) and WIS 2.0." community.wmo.int/en/activity-areas/wis
- International Federation of Digital Seismograph Networks. "About the FDSN." www.fdsn.org/about/
- International GNSS Service. "About the IGS." igs.org/about/
- IGN, ITRF Product Center. "International Terrestrial Reference Frame." itrf.ign.fr/en/homepage
- Argo Program. "About Argo." argo.ucsd.edu/about/
- NASA. "Landsat 1." landsat.gsfc.nasa.gov/satellites/landsat-1/
- European Union. "Copernicus." www.copernicus.eu/en
- Bureau International des Poids et Mesures. "Realizing and disseminating international reference time scales: UTC, UTCr and TT(BIPM)." www.bipm.org/en/time-ftp
- 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
- 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
- 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
- Carpenter, B., ed. (1996). RFC 1958, "Architectural Principles of the Internet." IETF. www.rfc-editor.org/rfc/rfc1958
- Resnick, P. (2014). RFC 7282, "On Consensus and Humming in the IETF." IETF. www.rfc-editor.org/rfc/rfc7282
- Open Geospatial Consortium. "OGC SensorThings API." www.ogc.org/standards/sensorthings/
- W3C (2017). "Semantic Sensor Network Ontology." W3C Recommendation, 19 October 2017. www.w3.org/TR/vocab-ssn/
- 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/
- 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
- Birkholz, H., et al. (2023). RFC 9334, "Remote ATtestation procedureS (RATS) Architecture." IETF. www.rfc-editor.org/rfc/rfc9334
- Bradner, S. (1997). RFC 2119, "Key words for use in RFCs to Indicate Requirement Levels." IETF. www.rfc-editor.org/rfc/rfc2119
- Leiba, B. (2017). RFC 8174, "Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words." IETF. www.rfc-editor.org/rfc/rfc8174