Skip to content

Open to every implementer.

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

Profiles
5
Specification
CC BY 4.0
Code
Apache-2.0

Implementers

Who implements the protocol.

Each kind of implementation has its own profile.

ProfileForFunctions
OBSP-NODENode agents and devicesJoin, Describe, Time, Observe, Qualify, Orchestrate (apply), Exit
OBSP-SITESite controllersOBSP-NODE plus Admit (local), Orchestrate (plan), Correct, Prove (verifier)
OBSP-GRIDCluster and grid control planesOBSP-SITE plus Federate and Exchange
OBSP-PROVIDERHardware, software, model and data providersAdmit, Describe, Exit
OBSP-CONSUMERApplications reading productsExchange, 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 governanceThe Observatory Protocol is an open protocol. Any party may implement it; changes are proposed upstream, in the open, before any implementation follows them.
  • VersioningProtocol 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 proposalsChanges 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 levelsDeclared, 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 authorityWarnings, 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 tokenThe protocol defines no token, coin or tradable unit.
  • ArchitectureZero trust (NIST SP 800-207): every request is authenticated, authorised and logged; network position grants nothing.
  • Device identityAttested; hardware root where the class has one; short-lived certificates; revocation within the site's offline window.
  • Workload identitySPIFFE-style SVIDs, rotated; no shared secrets.
  • KeysSite keys held by the grid operator; customer-held keys for upstream services; HSM or TPM-sealed where available.
  • Supply chainSBOM, SLSA provenance, signed artifacts, TUF update metadata, SUIT for firmware.
  • TimeAuthenticated time (P3, §5.4); time integrity gates receipts.
  • OT environmentsIEC 62443 zones and conduits for industrial deployments.
  • PrivacyObservation data that can identify a person is a declared data class with its own policy; default is not to collect it.
  • Break glassLogged, time-bound, receipted.

Participants

The roles the protocol defines.

  • Instruments, sensors and devicesArbitrary qualified sensors and instruments whose measurements are ingested with calibration, units, geometry, time, custody and uncertainty; each sensor has a passport and calibration record.
  • NodeThe minimum useful deployable unit: server, rugged appliance, radio node, sensor gateway, satellite terminal, AI, scientific, vehicle or virtual node.
  • Wedge nodeThe 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 agentThe minimum trusted local control component on a node.
  • SiteThe minimum independently operable local governance and failure domain: one or more nodes plus local network, identity, policy, evidence, storage, products and operator surfaces.
  • ClusterAn optional scale or specialisation domain for scheduling, shared storage, accelerators or data locality.
  • FederationAn exchange of products, capabilities, events or work across approved, independently administered trust domains, using explicit trust, policy, data-locality, version and correction contracts.
  • Fleet controllerCoordinates plans, acknowledgements, convergence evidence, update campaigns and correction propagation across nodes and sites.
  • deployment plan compilerResolves a signed deployment plan against the provider and capability registry and policy, in deterministic phases, into an immutable plan.
  • Plan reconcilerCompares 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 authorityReceives the attestation result, asks policy about enrolment and returns node identity, trust bundle and a signed bootstrap plan.
  • Attestation verifierAppraises attester evidence against reference values, endorsements and appraisal policy and issues a scoped attestation result that gates workloads and secrets.

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

Take part

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