---
title: "Provider | Observatory Protocol"
description: "A hardware, software, model, data, connectivity or service supplier that enters by manifest for a stated scope and declares a tested exit path."
url: https://nexusobservatory.com/nodes/provider/
publisher: GCRI Canada
updated: 2026-11-18
---

[Observatory Protocol](https://nexusobservatory.com/)[Node registry](https://nexusobservatory.com/nodes/)Provider

# Provider

A hardware, software, model, data, connectivity or service supplier that enters by manifest for a stated scope and declares a tested exit path.

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

Provider role. (OBSP 0.1 §3) Presence, connectivity or a commercial relationship MUST NOT imply admission. (OBSP 0.1 §5.2) Every provider manifest MUST declare an exit path. (OBSP 0.1 §5.12)

**Class**: [Operators, providers and stewards](https://nexusobservatory.com/nodes/#c=actors) Organisations that run deployments, supply components or maintain the specification.
**Protocol role**: `PROVIDER` Provider. (OBSP 0.1 §3)
**Conformance profile**: `OBSP-PROVIDER` Hardware, software, model and data provider (OBSP 0.1 §7.1)
**Technology domains**: [Security, identity and supply chain](https://nexusobservatory.com/technical/domains/security/)

## 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 |
| --- | --- | --- |
| Admission | Provider manifest, SBOM and SLSA provenance; a SCITT receipt should be recorded | (OBSP 0.1 §5.2; SPDX; CycloneDX; SLSA 1.0; IETF SCITT) |

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

- [`provider-manifest`](https://nexusobservatory.com/schemas/#s=provider-manifest) ProviderManifest
- [`supply-chain-receipt`](https://nexusobservatory.com/schemas/#s=supply-chain-receipt) SupplyChainReceipt
- [`model-manifest`](https://nexusobservatory.com/schemas/#s=model-manifest) ModelManifest
- [`source-manifest`](https://nexusobservatory.com/schemas/#s=source-manifest) SourceManifest
- [`source-release`](https://nexusobservatory.com/schemas/#s=source-release) SourceRelease
- [`decommission-record`](https://nexusobservatory.com/schemas/#s=decommission-record) DecommissionRecord

### Accepts

- [`qualification-record`](https://nexusobservatory.com/schemas/#s=qualification-record) QualificationRecord
- [`request-context`](https://nexusobservatory.com/schemas/#s=request-context) RequestContext

## Lifecycle and conformance

`OBSP-PROVIDER` 3 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-PROVIDER-001 | Admit: provider manifest with supply-chain evidence | invariant | [`provider-manifest`](https://nexusobservatory.com/schemas/#s=provider-manifest) [`supply-chain-receipt`](https://nexusobservatory.com/schemas/#s=supply-chain-receipt) |
| CT-PROVIDER-002 | Describe: source releases and model manifests | schema | [`source-release`](https://nexusobservatory.com/schemas/#s=source-release) [`model-manifest`](https://nexusobservatory.com/schemas/#s=model-manifest) |
| CT-PROVIDER-003 | Exit: the provider names a data export and replacement path | invariant | [`provider-manifest`](https://nexusobservatory.com/schemas/#s=provider-manifest) |

[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 security model that apply to this role. (OBSP 0.1 §8)

**Architecture**: Zero trust (NIST SP 800-207): every request is authenticated, authorised and logged; network position grants nothing (OBSP 0.1 §8)
**Workload identity**: SPIFFE-style SVIDs, rotated; no shared secrets (OBSP 0.1 §8)
**Supply chain**: SBOM, SLSA provenance, signed artifacts, TUF update metadata, SUIT for firmware (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)

- [SPDX](https://spdx.dev/) Software Package Data Exchange ( SPDX )
- [CycloneDX](https://cyclonedx.org/specification/overview/) CycloneDX specification ( CycloneDX )
- [SLSA 1.0](https://slsa.dev/spec/v1.0/) Supply-chain Levels for Software Artifacts ( SLSA 1.0 )
- [IETF SCITT](https://datatracker.ietf.org/wg/scitt/about/) Supply Chain Integrity, Transparency and Trust working group ( IETF SCITT )
- [in-toto](https://in-toto.io/) in-toto supply chain framework ( in-toto )

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

The protocol lists no open gap for this type.

## 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. [nexustandards.com](https://nexustandards.com/)
**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.2: Admit](https://nexusobservatory.com/development/text/#c-5-2) Observatory Protocol 0.1 (draft), CC BY 4.0.
3. [OBSP 0.1 §5.12: Exit and decommission](https://nexusobservatory.com/development/text/#c-5-12) Observatory Protocol 0.1 (draft), CC BY 4.0.
4. [OBSP 0.1 §7.1: Profiles](https://nexusobservatory.com/development/text/#c-7-1) Observatory Protocol 0.1 (draft), CC BY 4.0.
5. [OBSP 0.1 §6: Wire bindings](https://nexusobservatory.com/development/text/#c-6) Observatory Protocol 0.1 (draft), CC BY 4.0.
6. SPDX Software Package Data Exchange [spdx.dev/](https://spdx.dev/) Checked 2026-11-12
7. CycloneDX CycloneDX specification [cyclonedx.org/specification/overview/](https://cyclonedx.org/specification/overview/) Checked 2026-11-12
8. SLSA 1.0 Supply-chain Levels for Software Artifacts [slsa.dev/spec/v1.0/](https://slsa.dev/spec/v1.0/) Checked 2026-11-12
9. IETF SCITT Supply Chain Integrity, Transparency and Trust working group [datatracker.ietf.org/wg/scitt/about/](https://datatracker.ietf.org/wg/scitt/about/) Checked 2026-11-12
10. 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
11. [OBSP 0.1 §4.3: Request context](https://nexusobservatory.com/development/text/#c-4-3) Observatory Protocol 0.1 (draft), CC BY 4.0.
12. [OBSP 0.1 §7.2: Conformance levels](https://nexusobservatory.com/development/text/#c-7-2) Observatory Protocol 0.1 (draft), CC BY 4.0.
13. [OBSP 0.1 §8: Security model](https://nexusobservatory.com/development/text/#c-8) Observatory Protocol 0.1 (draft), CC BY 4.0.
14. [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.
15. in-toto in-toto supply chain framework [in-toto.io/](https://in-toto.io/) Checked 2026-11-12

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/)
