---
title: "Ecosystem | Observatory Protocol"
description: "Protocol development is stewarded by GCRI Canada, lead organisation of the Nexus Consortium."
url: https://nexusobservatory.com/ecosystem/
publisher: GCRI Canada
updated: 2026-11-18
---

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

# Open to every implementer.

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

[Take part](https://nexusobservatory.com/contribute/)

[Governance](https://nexusobservatory.com/governance/)

**Profiles**: 5
**Specification**: CC BY 4.0
**Code**: Apache-2.0

Implementers

## Who implements the protocol.

Each kind of implementation has its own profile.

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

Adopters

## Who the protocol is written for.

The organisations that run the use cases the protocol is written for.

- Cities, emergency management agencies and universities.
- Cities, public-health units, school districts.
- Indigenous organisations and Indigenous-owned service providers, remote communities.
- National meteorological and hydrological services, through their implementing entities.
- Electric utilities, provinces and states, counties.
- Cooperatives, insurers, extension services.
- Remote communities, utilities, Indigenous power producers.
- Electric utilities.
- Mining companies and their contractors.
- Oil and gas operators.
- Education ministries, UN country offices, school networks.
- Schools, hobbyists, municipalities and seismic agencies.
- Ports, coastal agencies, surf and fishing communities.
- Conservation organisations, parks and biodiversity project developers.
- Provinces and states, watershed boards.
- UN refugee agency, non-governmental organisations, emergency telecommunications cluster.
- Emergency management agencies, event organisers, utilities.
- Research infrastructures and universities.
- Universities, provinces and states.
- Resorts and road authorities.
- Renewable-energy developers.
- Departments and ministries of transportation.
- Venues and their operators.
- Provinces and states, carriers.
- Natural-resource and environment departments, northern communities.

Governance

## How the protocol is governed.

- **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.

Participants

## The roles the protocol defines.

- **Instruments, sensors and devices** Arbitrary qualified sensors and instruments whose measurements are ingested with calibration, units, geometry, time, custody and uncertainty; each sensor has a passport and calibration record.
- **Node** The minimum useful deployable unit: server, rugged appliance, radio node, sensor gateway, satellite terminal, AI, scientific, vehicle or virtual node.
- **Wedge node** The establishment profile that creates an observatory from little or no infrastructure: boots from signed media, inventories and attests hardware, establishes local identity, discovers links, enrols providers, forms encrypted peer links, accepts a signed deployment plan and emits an evidence bundle; it can stay alone or recruit more nodes.
- **Node agent** The minimum trusted local control component on a node.
- **Site** The minimum independently operable local governance and failure domain: one or more nodes plus local network, identity, policy, evidence, storage, products and operator surfaces.
- **Cluster** An optional scale or specialisation domain for scheduling, shared storage, accelerators or data locality.
- **Federation** An exchange of products, capabilities, events or work across approved, independently administered trust domains, using explicit trust, policy, data-locality, version and correction contracts.
- **Fleet controller** Coordinates plans, acknowledgements, convergence evidence, update campaigns and correction propagation across nodes and sites.
- **deployment plan compiler** Resolves a signed deployment plan against the provider and capability registry and policy, in deterministic phases, into an immutable plan.
- **Plan reconciler** Compares desired plan with observed state and proposes a convergence set; it never invokes external actuators and must not auto-substitute a provider or model where that changes validity, radio authorization, data rights, safety case or contract terms.
- **Bootstrap authority** Receives the attestation result, asks policy about enrolment and returns node identity, trust bundle and a signed bootstrap plan.
- **Attestation verifier** Appraises attester evidence against reference values, endorsements and appraisal policy and issues a scoped attestation result that gates workloads and secrets.

[All participants](https://nexusobservatory.com/spec/participants/)

Across the consortium

## Built with the networks of the consortium.

Each network relates to the protocol in its own way. Each is quoted from its own public page.

- [GCRI **The Global Centre for Risk and Innovation** Research, risk technology and programmes that deploy observing infrastructure and test it against evidence. The Global Centre for Risk and Innovation helps countries assess systemic risk, test new technology and build evidence to act, via GCRI Canada and GCRI US. therisk.global, 2026-11-12](https://therisk.global/)
- [GRF **The Global Risks Forum** Cooperation and dialogue among the institutions that operate and use shared observation. The Global Risks Forum (GRF) is a Swiss association that convenes leaders and institutions on shared risk and governs Universe, the annual programme. globalriskforum.com, 2026-11-12](https://globalriskforum.com/)
- [GRA **The Global Risks Alliance** Finance and readiness questions that depend on qualified, traceable observations. The Global Risks Alliance (GRA) turns evidence on physical, operational and technology risk into the questions banks, insurers and investors ask. globalriskalliance.com, 2026-11-12](https://globalriskalliance.com/)
- [Standards **Nexus Standards** Open standards to identify, describe, verify and cite risk information, which observations bound by the protocol can carry. Open, machine-readable standards that help institutions identify, describe, verify and cite risk information across sectors and borders. nexustandards.com, 2026-11-12](https://nexustandards.com/)
- [Index **The Global Risks Index** Country risk indicators that observations with provenance and quality can inform. The Global Risks Index (NXS-GRX): the open, multi-domain family of risk indices for every country, with intervals, systemic coupling, forecasts, scenarios. risksindex.com, 2026-11-12](https://risksindex.com/)
- [Academy **Risk Academy** Training for implementers and operators of observing systems. Free courses and learning by doing across every area of risk, with twins of real places, open data and research hubs. risksacademy.com, 2026-11-12](https://risksacademy.com/)
- [Reports **Reports at Nexus Standards** Published evidence with provenance, citation and corrections. Reports at Nexus Standards: every edition and output in every format, with provenance, citation and corrections. nexustandards.com, 2026-11-12](https://nexustandards.com/nexus-reports/)
- [Foundry **Foundry** The technical work environment where tools that implement the protocol are developed. Public gateway to the technical work environment while keeping project permissions and privileged services within Foundry. therisk.global, 2026-11-12](https://therisk.global/nexus-foundry/)

Take part

## Propose a change, report a defect, review a draft.

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

[Read the changes](https://nexusobservatory.com/governance/changes/)

[Governance and proposals](https://nexusobservatory.com/write-to-us/contact/?topic=general)
