OSOIX

Draft specification · Research stage

Portable evidence for orbital events.

The OSOIX Evidence Package is a transport-neutral container for verified event records, original source references, decision provenance, integrity material and explicit limitations. It is intended to make mission evidence independently inspectable rather than platform-dependent.

Required package components

Manifest

Package identity, specification version, creation time, producer identity, included records and cryptographic hashes.

Event records

One or more verifiable event envelopes describing observed states, verification decisions and unresolved discrepancies.

Source index

References to signed telemetry, sensor output, mission-control logs, images, third-party observations and calibration records.

Decision record

Verification rules, thresholds, software versions, reviewer identities, approvals, exceptions and timestamps.

Integrity material

Content hashes, signatures, certificate chains, revocation information and optional trusted timestamp evidence.

Disclosure record

Known gaps, confidence limits, excluded sources, conflicting observations and restrictions on downstream use.

Package lifecycle

  1. STEP 01
    Create package manifest and immutable package identifier
  2. STEP 02
    Attach original source references without rewriting them
  3. STEP 03
    Add normalized event records and transformation provenance
  4. STEP 04
    Record automated checks and human review decisions
  5. STEP 05
    Seal package with hashes and authorized signatures
  6. STEP 06
    Validate package independently before downstream reliance
  7. STEP 07
    Archive, supersede or revoke with a traceable status record

Evidence Package · Draft 0.1

Minimum package manifest

{
  "spec_version": "osoix-evidence-draft-0.1",
  "package_id": "evidence_...",
  "created_at": "2026-08-03T00:00:00Z",
  "producer": {
    "identity": "did:example:...",
    "authority_scope": ["mission.review"]
  },
  "mission_id": "mission_...",
  "event_ids": ["evt_..."],
  "artifacts": [
    {
      "media_type": "application/json",
      "uri": "urn:osoix:artifact:...",
      "sha256": "...",
      "source_identity": "did:example:..."
    }
  ],
  "verification_summary": {
    "status": "review_required",
    "confidence": 0.0,
    "unresolved_discrepancies": 0
  },
  "signatures": [],
  "limitations": [],
  "supersedes": null,
  "revocation_status": "active"
}

The package may be stored in signed object storage, regulated document infrastructure, conventional databases or permissioned ledgers. Portability and independent validation are more important than any particular storage technology.

Current boundary

This is a draft data architecture, not a certified evidence standard. No regulator, insurer, customer or aerospace operator has approved this format. The next engineering step is an open reference package produced from simulated mission telemetry and independently validated by a separate verifier.