---
title: "Implementers: Observatory Protocol"
description: "For implementers of Observatory Protocol 0.1: the conformance profile for each kind of implementation, and the planes across which it communicates."
url: https://observatory.global/protocol/developers/
publisher: Nexus Observatory Inc.
updated: 2026-10-27
---

[Observatory Protocol](https://observatory.global/protocol/)

/

[Specification](https://observatory.global/protocol/)

/

**Implementers** 

# Profiles and planes for implementers.

What an implementation of each profile must provide, and the planes across which it communicates.

[Read the specification](https://observatory.global/protocol/)

[Contribute](https://observatory.global/open/)

**Functions**: 12
**State machines**: 11
**Objects**: 21
**Standards**: 48

## The practice this part continues.

**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. \[1\]\[2\]\[3\]

## What each implementation provides.

Choose the profile that matches what you build; it names the functions you must implement.

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

## Four ways into the specification.

[Specification The functionsThe twelve functions and their requirements.](https://observatory.global/protocol/functions/)

[Specification The state machinesTyped transitions and their evidence.](https://observatory.global/protocol/states/)

[Specification The wire bindingsOne open binding per plane.](https://observatory.global/protocol/sdks/)

[Specification ConformanceProfiles and levels.](https://observatory.global/protocol/conformance/)

## References

Sources for the historical and standards statements on this page.

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](https://web.mit.edu/Saltzer/www/publications/endtoend/endtoend.pdf)
2. 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)
3. 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)
4. 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)
5. 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)

## Read it, test it, propose a change.

The Observatory Protocol is an open specification stewarded by the Nexus Consortium. Any party may implement it, and every change is proposed and decided in public.

[Read the specification](https://observatory.global/protocol/)

[Contribute](https://observatory.global/open/)

[Nexus Observatory](https://observatory.global/)**Observatory Protocol** . One open protocol for the observing grid.[Talk to us](https://observatory.global/contact/)

Observatory Protocol

- [Specification](https://observatory.global/protocol/specification/)
- [Conformance](https://observatory.global/protocol/conformance/)
- [Governance](https://observatory.global/protocol/governance/)
- [Developers](https://observatory.global/protocol/developers/)
- [Changes](https://observatory.global/protocol/changes/)

Technologies

- [Device identity and attestation](https://observatory.global/technologies/security/device-identity-and-attestation/)
- [PKI, secure boot and updates](https://observatory.global/technologies/security/pki-secure-boot-and-updates/)
- [Ingest and streaming](https://observatory.global/technologies/data/ingest-and-streaming/)
- [Storage and data lakes](https://observatory.global/technologies/data/storage-and-data-lakes/)

Industries

- [All industries](https://observatory.global/industries/)

Service platforms

- [Protocol & Grid](https://observatory.global/grid-services/)
- [Software](https://observatory.global/software/)
- [Hardware & power](https://observatory.global/hardware/)
- [Sensors & instruments](https://observatory.global/sensors/)
- [Connectivity](https://observatory.global/connectivity/)
- [Edge compute & AI](https://observatory.global/edge-ai/)
- [Earth observation & GeoAI](https://observatory.global/earth-observation/)

© 2026 Nexus Observatory Inc.

[Privacy](https://observatory.global/legal/privacy/)

[Terms](https://observatory.global/legal/terms/)

[Accessibility](https://observatory.global/legal/accessibility/)

[Cookie settings](https://observatory.global/privacy-choices/)

[Data credits](https://observatory.global/credits/)