---
title: "Protocol of protocols | Observatory Protocol"
description: "The Observatory Protocol replaces none of the standards that carry signals, time, identity and data. It names the standard it uses for each part, adds only what none of them covers, and binds them with common rules for identity, time, provenance, quality and governance."
url: https://nexusobservatory.com/architecture/
publisher: GCRI Canada
updated: 2026-11-18
---

1. [Observatory Protocol](https://nexusobservatory.com/)
2. [Technical](https://nexusobservatory.com/technical/)
3. Protocol of protocols

# One protocol over the protocols that already work.

The Observatory Protocol replaces none of the standards that carry signals, time, identity and data. It names the standard it uses for each part, adds only what none of them covers, and binds them with common rules for identity, time, provenance, quality and governance.

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

[Wire bindings](https://nexusobservatory.com/spec/wire-bindings/)

**Layers**: 8
**Open standards**: 48

The stack

## Every layer, and what binds it.

Select a layer to see the functions and objects that bind it, the standards the protocol text cites for it, and the other open standards that work at the same layer.

### Governance and conformance

Binding functions

- [Prove](https://nexusobservatory.com/spec/functions/)

Objects it carries

- [ConformanceClaim](https://nexusobservatory.com/schemas/)
- [ConformanceReport](https://nexusobservatory.com/schemas/)
- [QualificationRecord](https://nexusobservatory.com/schemas/)
- [ProofReceipt](https://nexusobservatory.com/schemas/)

Standards the protocol text cites

| Standard | Role in the protocol |
| --- | --- |
| IETF RATS (RFC 9334)\[1\] | Join and prove: reference architecture for attester evidence, verifier appraisal and attestation results. |
| IETF SCITT (RFC 9943)\[2\] | Admit and prove: transparency receipts for statements about artifacts and evidence. |
| JSON Schema 2020-12\[3\] | All functions: authored record contracts, fail-closed validation. |

At scale

## From one node to federated grids.

Scale comes from federation, not from a central service. Each grid keeps its own authority and exchanges products under explicit trust and policy rules.

1. **Join**
2. **Admit**
3. **Describe**
4. **Time**
5. **Observe**
6. **Qualify**
7. **Federate**
8. **Orchestrate**
9. **Correct**
10. **Exchange**
11. **Prove**
12. **Exit and decommission**

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

A level is reached only with the evidence the profile names, produced by the open conformance tool or a qualified laboratory. "Conformant" describes a tested scope only; it never means an outside body has approved it.

[From one node to federated grids](https://nexusobservatory.com/explainers/federation/)[Conformance](https://nexusobservatory.com/conformance/)

References

## Sources cited on this page.

1. [https://www.rfc-editor.org/rfc/rfc9334.html](https://www.rfc-editor.org/rfc/rfc9334.html)
2. [https://www.rfc-editor.org/info/rfc9943/](https://www.rfc-editor.org/info/rfc9943/)
3. [https://json-schema.org/draft/2020-12](https://json-schema.org/draft/2020-12)
