Skip to content

Many implementers, one open protocol: three different stations joined by one shared link ring. The loop, step by step: 1. Three member nodes and a shared hub. 2. Sensor, link, edge and console stand ready. 3. Each member publishes its own observations. 4. Each reading is stamped with time and place. 5. Records flow to the shared hub. 6. The relay forwards sealed packets untouched. 7. The edge verifies every signature first. 8. The hub merges them without changing any. 9. Only a confirmed result leaves the edge. 10. Each member sees the combined picture. 11. The alert arrives with its evidence attached. 12. New members join with one agreement. 13. Instruments confirm the response took effect. 14. Record, proof and action are archived together. 15. Everything settles back to idle.

01 / 15

Three member nodes and a shared hub

Open governance

Open protocol

Open, not owned.

The Observatory Protocol is governed in the open, independently of any company. The specification stays public, every change goes through a public process, and the name means the conformance tests were passed. Anyone can implement it. Nexus Observatory Inc. builds enterprise systems on it and contributes to it as one implementer among many; it does not own the protocol or set its course.

01Why open

Instruments outlive companies. Rules must too.

The observing systems that endure keep their rules with everyone who uses them. A protocol for the world’s instruments has to outlast any company, product cycle or government term.

Continuity

Built to outlast us

Instruments run for decades. The rules they speak must be kept in the open, for the protocol, not for the products built on it.

Neutrality

Fair to every implementer

Manufacturers, agencies, universities and communities implement the same text, pass the same tests and carry the same name on the same terms.

Trust

Changes made in the open

Every change is proposed, reviewed and decided in public, with its reasons and its compatibility impact recorded.

02What open governance covers

What the open process keeps, and nothing more.

Governance is deliberately narrow. It covers the protocol, not anyone’s instruments, data, products or prices.

01

Specification

The normative text: functions, states, objects, actors and flows.

Public, versioned

02

Conformance

The tests an implementation must pass to say it speaks the protocol.

Open test suite

03

Change process

How a proposal becomes part of the protocol, and who decides.

Proposal to implemented

04

Versioning

Release numbers, compatibility rules and the support window for old versions.

Compatibility first

05

Naming

When a product may say it implements the protocol, and how that is shown.

Conformance before claims

03Roles

Roles kept apart.

A company can contribute to the protocol and build on it. It cannot own it.

OBSERVATORY PROTOCOL

Open specification · conformance

OPEN PROCESS

Keeps the protocol in public

NEXUS OBSERVATORY INC.

Implements, contributes, builds on it

IMPLEMENTERS

Anyone may implement it

CONTRIBUTORS

Propose changes, keep their rights

contributes

implements

keeps

proposes

OPEN PROCESS

Public change process

Keeps the specification, the conformance suite, the change process, versioning and naming.

IMPLEMENTER

Nexus Observatory Inc.

Implements the protocol, contributes to it, gives builders access and support, and designs and builds systems on it.

IMPLEMENTERS

Anyone

Manufacturers, agencies, researchers and communities may implement the protocol and test against it.

CONTRIBUTORS

You

Propose changes in public. Your contribution comes in under an inbound licence; your rights stay yours.

04Change process

From proposal to protocol, in public.

A change lands only when review accepts it and its conformance tests pass against an implementation. Rejected and withdrawn proposals stay on record, with reasons.

Returned for changes

Tests pass

Proposal

Review

Accepted

Implemented

Withdrawn or rejected

StateMeaningLeaves when
ProposalWritten in the open with motivation, text, compatibility notes and a test plan.The author asks for review.
ReviewPublic review by implementers and contributors. Comments and answers are kept.Accepted, returned for changes, or rejected.
AcceptedAgreed in principle; scheduled for a release.Conformance tests pass against an implementation.
ImplementedPart of a released version of the protocol.Superseded by a later proposal.
Withdrawn or rejectedClosed, kept on record with its reasons.—

Decision rules, quorum and appeal are set by the charter.

05Separation

The protocol and commerce, kept apart.

The protocol belongs to no company; companies exist to build on it. These principles hold the line between them.

Separation principles

  1. No protocol funds to companiesMoney raised for the protocol does not flow to commercial companies, including Nexus Observatory Inc.
  2. Companies support the open workCommercial companies support open source and the protocol, and provide access and support to anyone building on it.
  3. Commercial lines are separateProducts, services and contracts are offered by the companies under their own terms, never in the protocol’s name.
  4. The same rules for every implementerThe specification, tests and naming rules apply equally to our products and to everyone else’s.

06Documents

The documents that govern the protocol.

What each one sets.

Charter

Purpose, scope, decision rules and appeal.

Membership

Who may take part and on what terms.

Change process

The full proposal process, templates and review rules.

Specification licence

The terms under which the specification text is published.

Inbound contribution licence

A developer certificate of origin or a licence-grant agreement, never a copyright assignment.

Naming and conformance policy

When and how an implementation may use the protocol’s name.

—Begin

Keep the observing grid open.

Read the specification, propose a change, or implement it in your instruments.

Read the protocolContribute
Open governanceOpen protocol

Open, not owned.

The Observatory Protocol is governed in the open, independently of any company. The specification stays public, every change goes through a public process, and the name means the conformance tests were passed. Anyone can implement it. Nexus Observatory Inc. builds enterprise systems on it and contributes to it as one implementer among many; it does not own the protocol or set its course.

01Why open

Instruments outlive companies. Rules must too.

The observing systems that endure keep their rules with everyone who uses them. A protocol for the world’s instruments has to outlast any company, product cycle or government term.

Continuity

Built to outlast us

Instruments run for decades. The rules they speak must be kept in the open, for the protocol, not for the products built on it.

Neutrality

Fair to every implementer

Manufacturers, agencies, universities and communities implement the same text, pass the same tests and carry the same name on the same terms.

Trust

Changes made in the open

Every change is proposed, reviewed and decided in public, with its reasons and its compatibility impact recorded.

02What open governance covers

What the open process keeps, and nothing more.

Governance is deliberately narrow. It covers the protocol, not anyone’s instruments, data, products or prices.

01Specification

The normative text: functions, states, objects, actors and flows.

Public, versioned
02Conformance

The tests an implementation must pass to say it speaks the protocol.

Open test suite
03Change process

How a proposal becomes part of the protocol, and who decides.

Proposal to implemented
04Versioning

Release numbers, compatibility rules and the support window for old versions.

Compatibility first
05Naming

When a product may say it implements the protocol, and how that is shown.

Conformance before claims
03Roles

Roles kept apart.

A company can contribute to the protocol and build on it. It cannot own it.

OBSERVATORY PROTOCOL Open specification · conformance OPEN PROCESS Keeps the protocol in public NEXUS OBSERVATORY INC. Implements, contributes, builds on it IMPLEMENTERS Anyone may implement it CONTRIBUTORS Propose changes, keep their rights contributes implements keeps proposes
OPEN PROCESS

Public change process

Keeps the specification, the conformance suite, the change process, versioning and naming.

IMPLEMENTER

Nexus Observatory Inc.

Implements the protocol, contributes to it, gives builders access and support, and designs and builds systems on it.

IMPLEMENTERS

Anyone

Manufacturers, agencies, researchers and communities may implement the protocol and test against it.

CONTRIBUTORS

You

Propose changes in public. Your contribution comes in under an inbound licence; your rights stay yours.

04Change process

From proposal to protocol, in public.

A change lands only when review accepts it and its conformance tests pass against an implementation. Rejected and withdrawn proposals stay on record, with reasons.

StateMeaningLeaves when
ProposalWritten in the open with motivation, text, compatibility notes and a test plan.The author asks for review.
ReviewPublic review by implementers and contributors. Comments and answers are kept.Accepted, returned for changes, or rejected.
AcceptedAgreed in principle; scheduled for a release.Conformance tests pass against an implementation.
ImplementedPart of a released version of the protocol.Superseded by a later proposal.
Withdrawn or rejectedClosed, kept on record with its reasons.—

Decision rules, quorum and appeal are set by the charter.

05Separation

The protocol and commerce, kept apart.

The protocol belongs to no company; companies exist to build on it. These principles hold the line between them.

Separation principles

  1. No protocol funds to companiesMoney raised for the protocol does not flow to commercial companies, including Nexus Observatory Inc.
  2. Companies support the open workCommercial companies support open source and the protocol, and provide access and support to anyone building on it.
  3. Commercial lines are separateProducts, services and contracts are offered by the companies under their own terms, never in the protocol’s name.
  4. The same rules for every implementerThe specification, tests and naming rules apply equally to our products and to everyone else’s.
06Documents

The documents that govern the protocol.

What each one sets.

Charter

Purpose, scope, decision rules and appeal.

Membership

Who may take part and on what terms.

Change process

The full proposal process, templates and review rules.

Specification licence

The terms under which the specification text is published.

Inbound contribution licence

A developer certificate of origin or a licence-grant agreement, never a copyright assignment.

Naming and conformance policy

When and how an implementation may use the protocol’s name.

—Begin

Keep the observing grid open.

Read the specification, propose a change, or implement it in your instruments.