---
title: "Edge compute node | Observatory Protocol"
description: "An edge computer that runs a node agent and workloads at the site. It applies signed plans in the smallest reversible step and records what it applied."
url: https://nexusobservatory.com/nodes/edge-compute/
publisher: GCRI Canada
updated: 2026-11-18
---

[Observatory Protocol](https://nexusobservatory.com/)[Node registry](https://nexusobservatory.com/nodes/)Edge compute node

# Edge compute node

An edge computer that runs a node agent and workloads at the site. It applies signed plans in the smallest reversible step and records what it applied.

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

[Onboard a node](https://nexusobservatory.com/onboarding/)

[Explore the schemas](https://nexusobservatory.com/schemas/)

## Role

The specification lists an edge computer as a node. (OBSP 0.1 §3) The node agent applies the smallest reversible step and rolls back on failure. (OBSP 0.1 §5.8)

**Class**: [Compute, relay and control](https://nexusobservatory.com/nodes/#c=compute) Edge computers, relays, site cell controllers, clusters and federation peers.
**Protocol role**: `NODE` Node. (OBSP 0.1 §3)
**Conformance profile**: `OBSP-NODE` Node agent and device. In this profile, orchestrate here means applying a signed plan, not compiling one (OBSP 0.1 §7.1)
**Technology domains**: [Edge hardware and runtime](https://nexusobservatory.com/technical/domains/edge/)
**Sectors**: [Government and public safety](https://nexusobservatory.com/applied/sectors/public-safety/), [Cities](https://nexusobservatory.com/applied/sectors/cities/), [Communities and rural](https://nexusobservatory.com/applied/sectors/communities/), [Industrial](https://nexusobservatory.com/applied/sectors/industrial/), [Sports and events](https://nexusobservatory.com/applied/sectors/sports-events/), [Development and humanitarian](https://nexusobservatory.com/applied/sectors/humanitarian/), [Scientific](https://nexusobservatory.com/applied/sectors/scientific/), [Environment and climate](https://nexusobservatory.com/applied/sectors/environment/), [Energy](https://nexusobservatory.com/applied/sectors/energy/), [Transport](https://nexusobservatory.com/applied/sectors/transport/), [Education](https://nexusobservatory.com/applied/sectors/education/)

## Interfaces

The planes and bindings this type uses. Bindings are normative for OBSP 0.1; radio and link layers follow their own standards. (OBSP 0.1 §6)

| Interface | Binding | Sources |
| --- | --- | --- |
| Control | TLS 1.3 with mutual authentication, protobuf messages in obsp.v1 | (OBSP 0.1 §6) |
| Updates | Signed plans with TUF metadata; SUIT manifests for device firmware | (OBSP 0.1 §5.8; TUF; IETF RFC 9019) |
| Platforms | Kubernetes, lightweight edge Kubernetes and plain Linux, on x86\_64 and arm64 | (OBSP 0.1 §13) |

## Schemas it emits and accepts

Each document is a JSON Schema 2020-12 contract. Open one in the schema explorer. (JSON Schema 2020-12) Every request, command and event also carries a request context. (OBSP 0.1 §4.3)

### Emits

- [`node-manifest`](https://nexusobservatory.com/schemas/#s=node-manifest) NodeManifest
- [`attestation-evidence`](https://nexusobservatory.com/schemas/#s=attestation-evidence) AttestationEvidence
- [`time-quality`](https://nexusobservatory.com/schemas/#s=time-quality) TimeQuality
- [`observed-state-receipt`](https://nexusobservatory.com/schemas/#s=observed-state-receipt) ObservedStateReceipt
- [`reconciliation-receipt`](https://nexusobservatory.com/schemas/#s=reconciliation-receipt) ReconciliationReceipt
- [`observation-record`](https://nexusobservatory.com/schemas/#s=observation-record) ObservationRecord
- [`decommission-record`](https://nexusobservatory.com/schemas/#s=decommission-record) DecommissionRecord

### Accepts

- [`node-bootstrap-bundle`](https://nexusobservatory.com/schemas/#s=node-bootstrap-bundle) NodeBootstrapBundle
- [`attestation-result`](https://nexusobservatory.com/schemas/#s=attestation-result) AttestationResult
- [`plan`](https://nexusobservatory.com/schemas/#s=plan) Plan
- [`reconciliation-assignment`](https://nexusobservatory.com/schemas/#s=reconciliation-assignment) ReconciliationAssignment
- [`system-pack`](https://nexusobservatory.com/schemas/#s=system-pack) SystemPack
- [`request-context`](https://nexusobservatory.com/schemas/#s=request-context) RequestContext

## Lifecycle and conformance

`OBSP-NODE` 7 of 12 functions. (OBSP 0.1 §7.1) A level is reached only with the evidence it names. (OBSP 0.1 §7.2)

5.1 Join 5.2 Admit 5.3 Describe 5.4 Time 5.5 Observe 5.6 Qualify 5.7 Federate 5.8 Orchestrate 5.9 Correct 5.10 Exchange 5.11 Prove 5.12 Exit and decommission

Figure 1The twelve stages of the lifecycle. The stages in the type's profile are marked.

### Conformance cases that apply

| Case | What it tests | Kind | Evidence |
| --- | --- | --- | --- |
| CT-NODE-001 | Join: node manifest, attestation evidence and the verifier's result | invariant | [`node-manifest`](https://nexusobservatory.com/schemas/#s=node-manifest) [`attestation-evidence`](https://nexusobservatory.com/schemas/#s=attestation-evidence) [`attestation-result`](https://nexusobservatory.com/schemas/#s=attestation-result) [`request-context`](https://nexusobservatory.com/schemas/#s=request-context) |
| CT-NODE-002 | Join: bootstrap bundle received from the site cell | schema | [`node-bootstrap-bundle`](https://nexusobservatory.com/schemas/#s=node-bootstrap-bundle) |
| CT-NODE-003 | Describe: sensor passports and the calibration records they cite | invariant | [`sensor-passport`](https://nexusobservatory.com/schemas/#s=sensor-passport) [`calibration-record`](https://nexusobservatory.com/schemas/#s=calibration-record) |
| CT-NODE-004 | Time: time quality reported as explicit state | invariant | [`time-quality`](https://nexusobservatory.com/schemas/#s=time-quality) |
| CT-NODE-005 | Observe: observation records and event envelopes | schema | [`observation-record`](https://nexusobservatory.com/schemas/#s=observation-record) [`event-envelope`](https://nexusobservatory.com/schemas/#s=event-envelope) |
| CT-NODE-006 | Observe: store and forward replay with its result | schema | [`replay-batch`](https://nexusobservatory.com/schemas/#s=replay-batch) [`replay-batch-result`](https://nexusobservatory.com/schemas/#s=replay-batch-result) |
| CT-NODE-007 | Qualify: quality flags and provenance travel with values | schema | [`quality-flag`](https://nexusobservatory.com/schemas/#s=quality-flag) [`provenance`](https://nexusobservatory.com/schemas/#s=provenance) |
| CT-NODE-008 | Orchestrate: a signed plan applied with a reconciliation receipt | schema | [`plan`](https://nexusobservatory.com/schemas/#s=plan) [`reconciliation-receipt`](https://nexusobservatory.com/schemas/#s=reconciliation-receipt) [`observed-state-receipt`](https://nexusobservatory.com/schemas/#s=observed-state-receipt) |
| CT-NODE-009 | Exit: decommission with revoked identities and a full export | invariant | [`decommission-record`](https://nexusobservatory.com/schemas/#s=decommission-record) |

[Run these cases in the onboarding check](https://nexusobservatory.com/onboarding/#check)

### Levels

**Declared**: Signed self-declaration naming profile, version and scope.
**Self-tested**: Conformance report (obsp conformance run) produced by the participant, with digests of the tested artifacts.
**Lab-tested**: Conformance report (obsp conformance run) and lab test record from a qualified lab.
**Qualified**: Lab report plus field observation for the declared scope and a qualification-record.
**Suspended**: Suspension notice with reason.
**Withdrawn**: Withdrawal notice.

## Identity, attestation and security

Requirements of the join function and of the security model. (OBSP 0.1 §5.1; OBSP 0.1 §8) Attestation follows the RATS architecture, passport model. (IETF RFC 9334 §5.1)

- A node MUST present attestation evidence (RATS, RFC 9334, passport model) rooted in a hardware root of trust where the device class has one (TPM 2.0, DICE or a secure element), or a software root explicitly marked SOFTWARE\_ROOT otherwise. ( OBSP 0.1 §5.1 )
- A verifier MUST bind the result to a nonce and an expiry. ( OBSP 0.1 §5.1 )
- Identity MUST be short-lived and renewable (X.509 SVID, SPIFFE-style URI spiffe://<trust-domain>/node/<uni>). ( OBSP 0.1 §5.1 )
- Long-lived shared secrets MUST NOT be used. ( OBSP 0.1 §5.1 )
- The bootstrap bundle MUST be signed by the site cell's enrolment key and carry the trust anchors, policy reference and the first plan digest. ( OBSP 0.1 §5.1 )

Root-of-trust classes the attestation evidence schema accepts: `TPM2`, `DICE`, `SECURE\_ELEMENT`, `SOFTWARE\_ROOT`. (OBSP 0.1 §5.1)

A hardware root follows TPM 2.0 or DICE where the device class has one. (TCG TPM 2.0; TCG DICE)

**Architecture**: Zero trust (NIST SP 800-207): every request is authenticated, authorised and logged; network position grants nothing (OBSP 0.1 §8)
**Device identity**: Attested; hardware root where the class has one; short-lived certificates; revocation within the site cell's offline window (OBSP 0.1 §8)
**Workload identity**: SPIFFE-style SVIDs, rotated; no shared secrets (OBSP 0.1 §8)
**Keys**: Site cell keys held by the grid operator; customer-held keys for upstream services; HSM or TPM-sealed where available (OBSP 0.1 §8)
**Supply chain**: SBOM, SLSA provenance, signed artifacts, TUF update metadata, SUIT for firmware (OBSP 0.1 §8)
**Time**: Authenticated time (P3, §5.4); time integrity gates receipts (OBSP 0.1 §8)
**OT environments**: IEC 62443 zones and conduits for industrial deployments (OBSP 0.1 §8)
**Privacy**: Observation data that can identify a person is a declared data class with its own policy; default is not to collect it (OBSP 0.1 §8)

## Interoperability profile and standards

The primary standards this type draws on. Alignment with a standard is stated as alignment. It is not an approval by the standards body. (OBSP 0.1 §13)

- [TUF](https://theupdateframework.io/) The Update Framework ( TUF )
- [IETF RFC 9019](https://www.rfc-editor.org/rfc/rfc9019.html) A Firmware Update Architecture for Internet of Things (SUIT) ( IETF RFC 9019 )
- [IETF RFC 9124](https://www.rfc-editor.org/rfc/rfc9124.html) A Manifest Information Model for Firmware Updates in IoT Devices (SUIT) ( IETF RFC 9124 )
- [ETSI MEC](https://www.etsi.org/technologies/multi-access-edge-computing) Multi-access Edge Computing ( ETSI MEC )
- [TCG TPM 2.0](https://trustedcomputinggroup.org/resource/tpm-library-specification/) Trusted Platform Module Library Specification ( TCG TPM 2.0 )

## Not yet defined

What the protocol does not define for this type in version 0.1, stated as the specification states it. Nothing here is filled in from elsewhere.

- Plan signing with TUF is an open gap in OBSP 0.1 (G-ORCH-1). ( OBSP 0.1 §9 )
- `G-ORCH-1` Plan signing path and TUF update metadata (Orchestrate). ( OBSP 0.1 §9 )

## Across the consortium

Related pages on the consortium's other networks, in their own words.

**Standards Nexus Standards**: Open standards to identify, describe, verify and cite risk information, which observations bound by the protocol can carry. [Early Warning and Anticipatory Action](https://nexustandards.com/early-warning/)[Hazards and Disaster Risk Reduction](https://nexustandards.com/hazards/)[Cities and the Built Environment](https://nexustandards.com/cities/)[Communities, Learning and Contribution](https://nexustandards.com/communities/)[Industry, Trade and Supply Chains](https://nexustandards.com/industry-trade/)[Humanitarian Action and Development](https://nexustandards.com/humanitarian/)[Data and Evidence](https://nexustandards.com/data/)[Climate and Earth Systems](https://nexustandards.com/climate/)[Energy and Critical Infrastructure](https://nexustandards.com/energy-infrastructure/)[Open Infrastructure and Developers](https://nexustandards.com/open-infrastructure/)
**Index The Global Risks Index**: Country risk indicators that observations with provenance and quality can inform. [risksindex.com](https://risksindex.com/)
**Academy Risk Academy**: Training for implementers and operators of observing systems. [risksacademy.com](https://risksacademy.com/)
**Reports Reports at Nexus Standards**: Published evidence with provenance, citation and corrections. [nexustandards.com/nexus-reports](https://nexustandards.com/nexus-reports/)

## References

Sources cited on this page, in order of first citation. Addresses were last checked on the date shown.

1. [OBSP 0.1 §3: Participant roles](https://nexusobservatory.com/development/text/#c-3) Observatory Protocol 0.1 (draft), CC BY 4.0.
2. [OBSP 0.1 §5.8: Orchestrate](https://nexusobservatory.com/development/text/#c-5-8) Observatory Protocol 0.1 (draft), CC BY 4.0.
3. [OBSP 0.1 §7.1: Profiles](https://nexusobservatory.com/development/text/#c-7-1) Observatory Protocol 0.1 (draft), CC BY 4.0.
4. [OBSP 0.1 §6: Wire bindings](https://nexusobservatory.com/development/text/#c-6) Observatory Protocol 0.1 (draft), CC BY 4.0.
5. TUF The Update Framework [theupdateframework.io/](https://theupdateframework.io/) Checked 2026-11-12
6. IETF RFC 9019 A Firmware Update Architecture for Internet of Things (SUIT) [www.rfc-editor.org/rfc/rfc9019.html](https://www.rfc-editor.org/rfc/rfc9019.html) Checked 2026-11-12
7. [OBSP 0.1 §13: Sovereign deployment for every operator and environment](https://nexusobservatory.com/development/text/#c-13) Observatory Protocol 0.1 (draft), CC BY 4.0.
8. JSON Schema 2020-12 JSON Schema draft 2020-12 [json-schema.org/draft/2020-12](https://json-schema.org/draft/2020-12) Checked 2026-11-12
9. [OBSP 0.1 §4.3: Request context](https://nexusobservatory.com/development/text/#c-4-3) Observatory Protocol 0.1 (draft), CC BY 4.0.
10. [OBSP 0.1 §7.2: Conformance levels](https://nexusobservatory.com/development/text/#c-7-2) Observatory Protocol 0.1 (draft), CC BY 4.0.
11. [OBSP 0.1 §5.1: Join](https://nexusobservatory.com/development/text/#c-5-1) Observatory Protocol 0.1 (draft), CC BY 4.0.
12. [OBSP 0.1 §8: Security model](https://nexusobservatory.com/development/text/#c-8) Observatory Protocol 0.1 (draft), CC BY 4.0.
13. IETF RFC 9334 Remote ATtestation procedureS (RATS) Architecture [www.rfc-editor.org/rfc/rfc9334.html](https://www.rfc-editor.org/rfc/rfc9334.html) Checked 2026-11-12
14. TCG TPM 2.0 Trusted Platform Module Library Specification [trustedcomputinggroup.org/resource/tpm-library-specification/](https://trustedcomputinggroup.org/resource/tpm-library-specification/) Checked 2026-11-12
15. TCG DICE Device Identifier Composition Engine architectures [trustedcomputinggroup.org/work-groups/dice-architectures/](https://trustedcomputinggroup.org/work-groups/dice-architectures/) Checked 2026-11-12
16. IETF RFC 9124 A Manifest Information Model for Firmware Updates in IoT Devices (SUIT) [www.rfc-editor.org/rfc/rfc9124.html](https://www.rfc-editor.org/rfc/rfc9124.html) Checked 2026-11-12
17. ETSI MEC Multi-access Edge Computing [www.etsi.org/technologies/multi-access-edge-computing](https://www.etsi.org/technologies/multi-access-edge-computing) Checked 2026-11-12
18. [OBSP 0.1 §9: Gaps register](https://nexusobservatory.com/development/text/#c-9) Observatory Protocol 0.1 (draft), CC BY 4.0.

On this page

1. Role
2. Interfaces
3. Schemas it emits and accepts
4. Lifecycle and conformance
5. Identity, attestation and security
6. Interoperability profile and standards
7. Not yet defined
8. Across the consortium
9. References

- [View the source](https://nexusobservatory.com/development/text/)
- [Report a defect](https://nexusobservatory.com/development/take-part/)
- [Propose a change](https://nexusobservatory.com/development/proposals/)
- [Changes](https://nexusobservatory.com/governance/changes/)
