OrbitFabric v1.1.0 - Candidate Integration Surface Consolidation¶
Release date: 2026-06-13
Status: Released
Scope: Core post-v1 candidate integration surface consolidation
Summary¶
OrbitFabric v1.1.0 is the current public release after v1.0.0 - Stable Mission Data Contract.
It keeps the v1.0.0 Mission Data Contract stable while consolidating a narrow set of post-v1 Core-owned candidate integration surfaces:
dashboard_summary.json
scenario_run_index.json
coverage_summary.json
simulation JSON structured expectation accounting
This release does not turn OrbitFabric Core into a dashboard backend, ground segment, runtime framework, flight software framework, Studio API or OpenOBSW/OpenSVF-specific generator.
Stable v1.0.0 surface remains unchanged¶
The original stable v1.0.0 Core-owned structured surface chain remains:
model_summary.json
entity_index.json
relationship_manifest.json
The Mission Model remains the source of truth.
The v1.1.0 consolidation does not add, remove or rename Mission Model fields.
Candidate surfaces consolidated in v1.1.0¶
The post-v1 candidate surface chain is:
dashboard_summary.json -> dashboard-ready aggregation of existing Core facts
scenario_run_index.json -> simulation JSON report run index
coverage_summary.json -> limited coverage derived from Core structured outputs
simulation JSON expectations -> additive structured expectation accounting
These surfaces are Core-owned because Core defines, computes and emits them.
They remain candidate because they were introduced after v1.0.0 and have not yet been promoted to the original stable compatibility class.
Generated artifact defaults¶
Mission-based CLI commands resolve omitted generated artifact output paths under the mission workspace.
For example:
orbitfabric gen ground examples/demo-3u/mission/
writes by default to:
examples/demo-3u/generated/ground/generic/
and:
orbitfabric export dashboard-summary examples/demo-3u/mission/
writes by default to:
examples/demo-3u/generated/reports/dashboard_summary.json
Explicit user-provided output paths remain explicit.
Compatibility posture¶
v1.1.0 preserves:
Mission Model semantics
v1.0.0 stable structured surface posture
legacy simulation JSON failed_expectations compatibility
explicit user-provided CLI output paths
Core as the Mission Data Contract authority
Structured expectation accounting is additive.
The top-level failed_expectations compatibility list remains available.
Explicit non-goals¶
v1.1.0 does not introduce:
Projection Profiles implementation
OSRA/SAVOIR implementation
OpenOBSW/OpenSVF-specific generation
Studio-specific APIs
mission health scoring
model completeness scoring
flight readiness scoring
runtime telemetry behavior
ground execution behavior
relationship graph behavior
dependency graph behavior
plugin discovery
plugin loading
plugin execution
CCSDS/PUS/CFDP framing
transport behavior
flight software framework behavior
ground segment behavior
Validation status¶
The release was prepared using the existing project validation posture:
documentation build expected to succeed with mkdocs build --strict
full test suite expected to pass with python -m pytest
Future documentation-only follow-up PRs may re-run:
mkdocs build --strict
python -m pytest
No Mission Data Contract semantic migration is required from v1.0.0 to v1.1.0.