Observatory ProtocolNode registryOnboarding
Node onboarding
Follow a node through the twelve stages of the lifecycle, then check its documents against the protocol's own conformance cases. The check runs in your browser. Nothing you paste leaves the page.
- 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
The twelve stages
A node that has never met the grid joins it and proves what it is. It keeps time and publishes what it measures, with its metadata and quality. It is orchestrated, corrected, federated and finally retired. (OBSP 0.1 §1) Choose a stage to read its requirements. Use the arrow keys to move between stages.
§5.1 Join
A node proves what it is, receives an identity and a policy, then a signed plan. (OBSP 0.1 §5.1)
UNENROLLEDDISCOVEREDATTESTINGIDENTITY_ISSUEDPOLICY_BOUNDPLAN_STAGEDLOCAL_READY
Other states: DEGRADED QUARANTINED REVOKED
Requirements
- Transitions not in the table MUST be refused and recorded. (OBSP 0.1 §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)
Objects
node-manifestNodeManifestnode-bootstrap-bundleNodeBootstrapBundleattestation-evidenceAttestationEvidenceattestation-resultAttestationResultrequest-contextRequestContext
Profiles that include it
OBSP-NODE, OBSP-SITE, OBSP-GRID. (OBSP 0.1 §7.1)
Conformance cases
CT-NODE-001Join: node manifest, attestation evidence and the verifier's resultCT-NODE-002Join: bootstrap bundle received from the site cell
| Clause | Stage | What it does | Objects | Profiles | Contract |
|---|---|---|---|---|---|
| §5.1 | Join | A node proves what it is, receives an identity and a policy, then a signed plan. | node-manifest node-bootstrap-bundle attestation-evidence attestation-result request-context | OBSP-NODE, OBSP-SITE, OBSP-GRID | Contracted |
| §5.2 | Admit | Providers enter by manifest, rights, security and technical review, for a stated scope. | provider-manifest qualification-record source-manifest source-release model-manifest supply-chain-receipt | OBSP-SITE, OBSP-GRID, OBSP-PROVIDER | Contracted |
| §5.3 | Describe | Every instrument and observation carries what, where, how and by whom. | sensor-passport calibration-record observation-record source-manifest node-manifest | OBSP-NODE, OBSP-SITE, OBSP-GRID, OBSP-PROVIDER | Contracted |
| §5.4 | Time | One time base across the grid, with time quality as explicit state. | time-quality observed-state-receipt event-envelope | OBSP-NODE, OBSP-SITE, OBSP-GRID | Contracted |
| §5.5 | Observe | Streams and files move over whatever link the site has, with store and forward. | observation-record native-envelope event-envelope replay-batch replay-batch-result | OBSP-NODE, OBSP-SITE, OBSP-GRID | Contracted |
| §5.6 | Qualify | Quality flags, calibration and provenance travel with each value. | observation-record quality-flag provenance calibration-record qualification-record | OBSP-NODE, OBSP-SITE, OBSP-GRID | Contracted |
| §5.7 | Federate | Nodes form cells, cells form clusters, and clusters federate across trust domains. | fleet-projection | OBSP-GRID | Open gap G-FED-1 |
| §5.8 | Orchestrate | Software, configuration and upgrades roll out by signed plan, with evidence for every change. | system-pack plan reconciliation-assignment reconciliation-receipt observed-state-receipt | OBSP-NODE, OBSP-SITE, OBSP-GRID | Open gap G-ORCH-1 |
| §5.9 | Correct | An upstream correction marks dependants stale, triggers recompute and publishes a new version. | correction-notice event-envelope | OBSP-SITE, OBSP-GRID, OBSP-CONSUMER | Contracted |
| §5.10 | Exchange | Governed products reach people and applications through versioned APIs, events, maps and exports. | product-manifest | OBSP-GRID, OBSP-CONSUMER | Open gap G-EXCH-1 |
| §5.11 | Prove | Peers answer unpredictable challenges and emit signed proof receipts for an independent verifier. | proof-receipt | OBSP-SITE, OBSP-GRID | Open gap G-PROVE-1 |
| §5.12 | Exit and decommission | Every material provider has an open export and replacement path, and decommissioning closes the record. | provider-manifest decommission-record | OBSP-NODE, OBSP-SITE, OBSP-GRID, OBSP-PROVIDER | Contracted |
Check a node
Paste or build your node's documents and run the protocol's own conformance cases on them. (OBSP 0.1 §7) The check runs in your browser. Nothing you paste leaves the page, and nothing is stored. A result is a self-assessment against a draft specification, not a certificate. (OBSP 0.1 §7.2)
One document, an array of documents, or an object keyed by file name such as "time-quality.node01.json". A document is recognised by its kind, a fixture wrapper or its file name.
Result
Load an example or paste your documents, then run the check.
Reading the result
Each stage of the profile passes when every case that covers it passes. A schema case checks that each named document is present and valid. An invariant case also checks rules that span documents. The implementer carries out a procedure case and attests to it. (OBSP 0.1 §7.2)
- 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.
A passing check supports at most the self-tested level, and only with a conformance report that cites the digests of the tested artifacts. Higher levels need a qualified laboratory and field observation. (OBSP 0.1 §7.2)
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.nexustandards.com
- 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 §1: Purpose and scope Observatory Protocol 0.1 (draft), CC BY 4.0.
- OBSP 0.1 §5.1: Join Observatory Protocol 0.1 (draft), CC BY 4.0.
- OBSP 0.1 §7.1: Profiles Observatory Protocol 0.1 (draft), CC BY 4.0.
- OBSP 0.1 §7: Conformance Observatory Protocol 0.1 (draft), CC BY 4.0.
- OBSP 0.1 §7.2: Conformance levels Observatory Protocol 0.1 (draft), CC BY 4.0.