Observatory ProtocolOpen developmentGovernance
Governance and decisions
Who decides what about the protocol, how a decision is recorded, and the rules that keep it neutral and open.
- 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
Bodies and decisions
The bodies that maintain the specification, how a change is decided and how releases are made. (Observatory Protocol, Governance)
The charter (CHARTER.md) sets the mission, stewardship and principles. This document sets who does what and how a change is decided. The rules are in policies/governance.md.
Bodies
| Body | Who | Does |
|---|---|---|
| Secretariat | GCRI Canada, lead institution and steward for the Nexus Consortium | Runs the repository, gateways, calendar and records; publishes releases; routes contributions; holds the name and release keys in trust |
| Editors | Appointed by the Secretariat on the Consortium's behalf from active contributors; recuse on their own proposals | Hold the pen on the specification and registers; review and merge; dispose of comments with reasons |
| Conformance reviewers | Appointed like the editors, independent of the claim under review | Rerun the suite on submitted evidence; list or refuse claims |
| Security response | Editors named in MAINTAINERS.md | Handle private vulnerability reports |
| Nexus Standards bodies | Global Standards Council, technical committee TC-SYS, working groups WG-DEV and WG-CNF | Decide normative changes under NS-13 once constituted; until then the Secretariat runs the interim procedure below |
The Global Risks Forum and The Global Risks Alliance take part in review, dialogue and adoption through their gateways and through their seats in the Nexus Standards bodies.
Change process: Observatory Improvement Proposals
| Stage | What happens | Minimum time |
|---|---|---|
DRAFT | An OIP is opened as a pull request from oips/0000-template.md | |
REVIEW | Editors, implementers and anyone else comment; the OIP names the sections, schemas, fixtures, conformance cases and registers it changes | |
LAST_CALL | Public comment window, announced on the Nexus Standards site | 90 days for a new function or profile; 30 days for a revision, register or policy change; 14 days for errata |
ACCEPTED | Merged when every comment has a disposition and every check passes; the same pull request updates the specification, schemas with positive and negative fixtures, conformance cases, registers and CHANGELOG.md | |
IMPLEMENTED | At least one implementation in IMPLEMENTATIONS.md shows the change at SELF_TESTED or higher |
An OIP may be WITHDRAWN at any stage. Editorial fixes such as typos and broken links need no OIP. A security fix may take an expedited OIP (SEC-2).
Interim procedure. Until the Global Standards Council charters the protocol's working group, the editors decide by consensus on the public record. The Secretariat confirms ACCEPTED. Any participant may appeal a process decision to the Secretariat (GOV-5).
Versions and releases
See policies/versioning.md, policies/deprecation.md and docs/guides/releasing.md.
Licences and contributions
| Item | Terms |
|---|---|
| Specification, schemas, registers, policies, documentation | CC-BY-4.0 |
| Tools, SDK, conformance suite | Apache-2.0 |
| Contributions | Same licences; Developer Certificate of Origin sign-off on each commit (PAR-3) |
| Patents | Contributors disclose known essential claims and license them royalty-free to conforming implementations (IPR-2, IPR-3) |
| The protocol name | Used only to state a claim that meets policies/conformance-claims.md (CNF-5) |
File-level licences are recorded in REUSE.toml.
Governance and decisions
Who decides what about the protocol, and how a decision is recorded. (Observatory Protocol policy, Governance and decisions)
GOV-1- GCRI Canada is the lead institution and steward of the protocol for the Nexus Consortium and runs the Secretariat; it holds the repository, the names and the release keys in trust for the Consortium.
GOV-2- Technical decisions are taken by the editors on the public record after review and, for normative changes, through the Nexus Standards development process (NS-13). Consensus comes first; votes happen only after consensus fails.
GOV-3- No organisation, sponsor, provider or operator holds a veto or a reserved seat on technical decisions because of funding, hosting or infrastructure.
GOV-4- Every decision is a public record with its reasons, the comments received and their disposition, except undisclosed vulnerabilities and personal matters.
GOV-5- A process decision can be appealed to the Secretariat and, once constituted, to the appeals body of the Nexus Standards programme.
Neutrality
Keep the protocol usable by every operator and free of commercial capture. (Observatory Protocol policy, Neutrality)
NEU-1- The specification, schemas and registers name roles, never organisations, products, vendors or endpoints.
NEU-2- No contribution may promote a company, product or paid service; requirements name capabilities, never vendors.
NEU-3- Every external dependency of a conforming deployment is replaceable behind a typed contract with a tested exit path (principle P6).
NEU-4- Consortium systems that implement the protocol hold no privileged role in it; any operator can replace any of them.
NEU-5- The repository check (tools/validate.py, group neutrality) runs on every change and fails on a denied term.
Intellectual property and licences
The terms on which the protocol is open to everyone. (Observatory Protocol policy, Intellectual property and licences)
IPR-1- The specification, schemas, registers, policies and documentation are licensed CC-BY-4.0; tools, SDK and conformance suite are licensed Apache-2.0 (REUSE.toml).
IPR-2- Contributors license their contributions under the same licences and disclose any patent claim they know to be essential to a draft.
IPR-3- Contributors commit to license essential patent claims royalty-free to every conforming implementation.
IPR-4- Implementing the protocol requires no fee, membership, account or permission.
References
Sources cited on this page, in order of first citation. Addresses were last checked on the date shown.
- Observatory Protocol, Governance: GOVERNANCE.md Observatory Protocol 0.1 (draft), CC BY 4.0.
- Observatory Protocol policy, Governance and decisions: registers/policies.yaml governance Observatory Protocol 0.1 (draft), CC BY 4.0.
- Observatory Protocol policy, Neutrality: registers/policies.yaml neutrality Observatory Protocol 0.1 (draft), CC BY 4.0.
- Observatory Protocol policy, Intellectual property and licences: registers/policies.yaml ipr-and-licensing Observatory Protocol 0.1 (draft), CC BY 4.0.