Skip to content

OrbitFabric v0.2.2 — Payload Contract Release Alignment

Status: development preview
Release type: model and documentation alignment
Primary focus: Payload / IOD Payload Contract Model

Summary

OrbitFabric v0.2.2 consolidates the Payload / IOD Payload Contract Model introduced during the v0.2.x development line.

This release aligns the repository, public documentation, roadmap, changelog and package version around the new Payload Contract Model.

The main result is that OrbitFabric can now describe optional mission-specific and IOD payload contracts as part of the Mission Data Contract.

Highlights

  • Optional mission/payloads.yaml model domain.
  • PayloadContract model.
  • Payload profile support.
  • Minimal payload lifecycle model.
  • Payload semantic lint rules.
  • Payload reference checks.
  • Generated payload contract documentation.
  • Generated payloads.md.
  • Payload-aware scenario behavior.
  • Minimal lifecycle simulation: READY → ACQUIRING → READY.
  • Invalid payload contract fixtures and negative tests.
  • Public Payload Contract Model documentation.
  • Roadmap and changelog alignment.

What Payload Contracts Describe

Payload contracts may describe:

  • payload identity;
  • payload profile;
  • linked subsystem;
  • telemetry references;
  • command references;
  • event references;
  • fault references;
  • lifecycle states;
  • command preconditions;
  • expected effects;
  • scenario-level behavior;
  • generated documentation.

What Payload Contracts Do Not Describe

Payload contracts do not describe:

  • payload firmware;
  • payload drivers;
  • hardware buses;
  • onboard runtime services;
  • payload runtime execution;
  • physical instrument simulation;
  • payload data processing pipelines;
  • ground segment implementation.

Positioning

OrbitFabric remains a Mission Data Contract framework.

This release does not turn OrbitFabric into:

  • a flight software framework;
  • a payload runtime;
  • a payload driver framework;
  • a physical simulator;
  • a ground segment;
  • a CCSDS/PUS/CFDP implementation.

Compatibility

OrbitFabric is still pre-1.0.

The Mission Model and Payload Contract Model may evolve before v1.0.

Verification

Expected verification commands:

ruff check .
pytest
mkdocs build --strict