OSOIX EXPERIMENTAL PROTOCOL · VERSION 1

Reality Boundary
Protocol

RBP-1

Provenance tells us how data came to exist. RBP-1 declares what kind of relationship a machine claim has to reality now.

A system should never display a stronger relationship to reality than its evidence can support.
THE PROBLEM

Digital twins often collapse different realities into one interface.

01

Reported becomes observed

A source record is presented as though the interface measured it directly.

02

Calculated becomes current truth

A deterministic state is displayed without its source epoch, model or transformation chain.

03

Projected becomes inevitable

A future model state appears without an explicit horizon or uncertainty boundary.

04

Inference becomes authority

A comparison or AI conclusion silently acquires operational meaning it does not possess.

THE REALITY SPECTRUM

Seven classes. No hidden promotion.

A reality class is not a confidence score. It declares the relationship between a claim and its evidence.

01

OBSERVED

A direct measurement from an identified sensor or observation process is included.

02

REPORTED

A source supplied a record, statement or metadata item.

03

CALCULATED

A declared transformation produced the value for the evaluation time.

04

PROJECTED

A model produced a value for a later time.

05

INFERRED

A conclusion was derived by comparing or combining other claims.

06

SYNTHETIC

The value was generated for simulation, testing or augmentation.

07

UNKNOWN

The available evidence cannot establish the claim or the required evidence is absent.

NEW RBP-1 CONCEPT

Epistemic survivability

RBP-1 does not stop at provenance. It removes a source conceptually, follows dependency edges, and identifies which claims remain derivable.

  • What survives without CelesTrak?
  • What survives without Space-Track?
  • Does a current state still exist?
  • Does the future projection still exist?
This is dependency analysis—not reliability probability, truth probability or safety authority.
SOURCECELESTRAK
SOURCESPACE-TRACK
REPORTEDELEMENT SETS
CALCULATEDCURRENT STATES
INFERREDCROSS-SOURCE DELTA
PROJECTEDFUTURE STATE
THE MACHINE CONTRACT

Every claim carries its own boundary.

{
  "protocol": "osoix.rbp.v1",
  "profile": "osoix.rbp.orbital-state.v1",
  "claim": {
    "realityClass": "PROJECTED",
    "sources": ["celestrak"],
    "dependencies": ["claim:reported-elements:celestrak"],
    "temporalBasis": {
      "sourceEpoch": "...",
      "evaluatedAt": "...",
      "horizonSeconds": 21600
    },
    "uncertainty": {
      "mode": "proxy",
      "covarianceIncluded": false
    },
    "authority": {
      "level": "research",
      "commandPath": false
    }
  }
}
Provenance
Sources and claim dependencies
Temporal basis
Source epoch, evaluation time and horizon
Transformation
Declared algorithm, version and reference frame
Uncertainty
Formal, proxy or unavailable
Authority
None, research, advisory or operational
Integrity
Claim and capsule SHA-256 digests
Open the normative JSON Schema →
WHAT RBP-1 IS NOT

Stricter language creates safer systems.

NOT A TRUTH SCORE

RBP-1 classifies evidence relationships. It does not assign the probability that a statement is true.

NOT COLLISION PROBABILITY

The orbital profile cannot replace covariance, CDMs, hard-body radius or authoritative safety-of-flight products.

NOT COMMAND AUTHORITY

Using an authoritative source does not create uplink, scheduling, transmission or spacecraft-control rights.

NOT A REPLACEMENT FOR PROV

W3C PROV remains the provenance foundation. RBP-1 is a claim-boundary layer above it.

FIRST LIVE PROFILE

Orbital Evidence Capsules inside OSOIX Mission Control.

The private implementation compiles reported public GP records, calculated current states, projected future states, cross-source deltas, cryptographic claim chains and source-removal scenarios for a selected NORAD object.

Open private implementationRead the complete specification