Observatory ProtocolNode registryGrid operator
Grid operator
The organisation that runs a site cell, cluster or grid and holds its keys. Where it is not the publisher of the software, the operator sovereignty overlay applies.
- 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
Role
Grid operator role. (OBSP 0.1 §3) Operator sovereignty profile. (OBSP 0.1 §12) Every operator class can run every function in the environments it chooses. (OBSP 0.1 §13)
- Class
- Operators, providers and stewards
Organisations that run deployments, supply components or maintain the specification. - Protocol role
GRID_OPERATORGrid operator. (OBSP 0.1 §3)- Conformance profile
- An operator runs implementations that claim profiles. The operator sovereignty overlay OBSP-SOV applies on top of them.
- Technology domains
- Field deployment and operations
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 |
|---|---|---|
| Keys | Site cell keys held by the grid operator; HSM or TPM-sealed where available | (OBSP 0.1 §8) |
| Updates | Signed releases from a mirror the operator controls | (OBSP 0.1 §12) |
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
participant-manifestParticipantManifestconformance-claimConformanceClaimdecommission-recordDecommissionRecord
Accepts
conformance-reportConformanceReportqualification-recordQualificationRecord
Lifecycle and conformance
An operator runs implementations that claim profiles. The operator sovereignty overlay OBSP-SOV applies on top of them.
| Clause | Stage | In a profile | Contract |
|---|---|---|---|
| §5.1 | Join | No | Contracted |
| §5.2 | Admit | No | Contracted |
| §5.3 | Describe | No | Contracted |
| §5.4 | Time | No | Contracted |
| §5.5 | Observe | No | Contracted |
| §5.6 | Qualify | No | Contracted |
| §5.7 | Federate | No | Open gap G-FED-1 |
| §5.8 | Orchestrate | No | Open gap G-ORCH-1 |
| §5.9 | Correct | No | Contracted |
| §5.10 | Exchange | No | Open gap G-EXCH-1 |
| §5.11 | Prove | No | Open gap G-PROVE-1 |
| §5.12 | Exit and decommission | No | Contracted |
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)
- NIST SP 800-207Zero Trust Architecture(NIST SP 800-207)
- ISA/IEC 62443Security for industrial automation and control systems(ISA/IEC 62443)
- TUFThe Update Framework(TUF)
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
- Open standards to identify, describe, verify and cite risk information, which observations bound by the protocol can carry.Early Warning and Anticipatory ActionHazards and Disaster Risk ReductionCities and the Built EnvironmentCommunities, Learning and ContributionWater and Food SystemsHumanitarian Action and DevelopmentData and EvidenceClimate and Earth SystemsEnergy and Critical InfrastructureOpen Infrastructure and Developers
- Index
- Country risk indicators that observations with provenance and quality can inform.risksindex.com
- Academy
- Training for implementers and operators of observing systems.risksacademy.com
- Reports
- Published evidence with provenance, citation and corrections.nexustandards.com/nexus-reports
References
Sources cited on this page, in order of first citation. Addresses were last checked on the date shown.
- OBSP 0.1 §3: Participant roles Observatory Protocol 0.1 (draft), CC BY 4.0.
- OBSP 0.1 §12: Operator sovereignty profile (`OBSP-SOV`) Observatory Protocol 0.1 (draft), CC BY 4.0.
- OBSP 0.1 §13: Sovereign deployment for every operator and environment Observatory Protocol 0.1 (draft), CC BY 4.0.
- OBSP 0.1 §6: Wire bindings Observatory Protocol 0.1 (draft), CC BY 4.0.
- OBSP 0.1 §8: Security model Observatory Protocol 0.1 (draft), CC BY 4.0.
- JSON Schema 2020-12 JSON Schema draft 2020-12 json-schema.org/draft/2020-12 Checked
- OBSP 0.1 §4.3: Request context Observatory Protocol 0.1 (draft), CC BY 4.0.
- NIST SP 800-207 Zero Trust Architecture csrc.nist.gov/pubs/sp/800/207/final Checked
- ISA/IEC 62443 Security for industrial automation and control systems www.isa.org/standards-and-publications/isa-standards/isa-iec-62443-series-of-standards Checked
- TUF The Update Framework theupdateframework.io/ Checked