v0.10.0 - Stability and Compatibility Contract¶
OrbitFabric v0.10.0 introduces the first stability and compatibility classification baseline on the path toward v1.0.0.
This is a release alignment and documentation contract milestone.
It does not introduce new Mission Model semantics, new generated surfaces, new CLI behavior, plugin execution, relationship graphs, dependency graphs, runtime behavior, ground behavior or Studio-specific APIs.
Purpose¶
The v0.10.0 goal is to classify OrbitFabric public and preview surfaces before v1.0.0.
The release defines what is currently:
public preview
candidate contract
stable contract
internal implementation detail
disposable generated artifact
compatibility-sensitive
The purpose is to make future evolution explicit, reviewable and safe for users and downstream tools.
Added¶
v0.10.0 adds the following reference documents:
Stability and Compatibility Contract
Mission Model Stability Contract
CLI Contract v1 Preview
Generated Surfaces Stability
Lint Rule Code Stability
JSON Report Compatibility
Scenario Evidence Stability
Release Compatibility Policy
These documents classify the compatibility expectations for:
Mission Model YAML
scenario YAML
CLI commands and documented options
lint diagnostic codes and severities
JSON report families and fields
Core-owned structured surfaces
generated runtime-facing manifests and bindings
generated ground-facing manifests and artifacts
release notes and release impact classification
Changed¶
v0.10.0 changes the project baseline from:
v0.9.0 - Relationship Manifest Surface and Extensibility Boundary
to:
v0.10.0 - Stability and Compatibility Contract
The package and CLI version are updated to:
0.10.0
The roadmap is updated so:
v0.10.0 Stability and Compatibility Contract completed
v0.10.1 Documentation and Published Site Consistency next
Compatibility impact¶
v0.10.0 is intentionally classification-only.
It does not change Mission Data Contract semantics.
It does not change the shape of existing generated outputs.
It does not change command behavior.
It does not change scenario execution behavior.
It does not change lint rule behavior.
It does not introduce a v1.0 compatibility guarantee.
Mission Data Contract impact¶
No Mission Model fields are added, removed or renamed.
No controlled values are added, removed or renamed.
No identifier rules are changed.
No scenario expectation semantics are changed.
No model domains are added.
The Mission Model remains the source of truth.
CLI impact¶
No CLI commands are added, removed or renamed.
No command options are added, removed or renamed.
No CLI behavior is changed.
The release classifies the current CLI surface as a public preview surface and clarifies that terminal text is human-oriented, not a machine contract.
JSON report impact¶
No JSON report fields are added, removed or renamed.
No JSON report families are added or removed.
No report schemas are introduced.
The release classifies JSON report compatibility expectations and clarifies which fields and tokens are compatibility-sensitive before v1.0.0.
Generated artifact impact¶
No generated artifact implementation changes are introduced.
No new generated surface is introduced.
No generated artifact path is changed.
The release classifies generated and exported surfaces as Core-owned structured surfaces, public preview generated artifacts or disposable generated artifacts depending on their role.
Lint diagnostic impact¶
No lint rules are added, removed or renamed.
No diagnostic codes are added, removed or renamed.
No diagnostic severities are changed.
The release classifies diagnostic code and severity evolution as compatibility-sensitive before v1.0.0.
Scenario evidence impact¶
No scenario fields are added, removed or renamed.
No scenario behavior is changed.
No expectation types are added, removed or renamed.
The release classifies scenario input and scenario evidence surfaces as development-preview surfaces and clarifies that simulation logs are human-oriented, while simulation JSON reports are the machine-readable evidence surface.
Architectural boundary¶
v0.10.0 intentionally does not introduce:
new Mission Model semantics
new YAML fields
new model domains
new CLI behavior
new JSON report fields
new generated surfaces
new lint diagnostics
new scenario behavior
schema migration tooling
JSON Schema publication
plugin execution
plugin discovery
plugin loader
relationship graph
dependency graph
runtime behavior
ground behavior
Studio-specific API
stable v1.0 compatibility guarantee
v1.0 direction¶
v0.10.0 prepares the project for the v1.0 path by making compatibility expectations explicit before further extensibility work.
The next planned milestone is:
v0.10.1 - Documentation and Published Site Consistency
That milestone should verify and preserve consistency between repository documentation and the published documentation site without introducing model, CLI, export, generator, runtime, ground or plugin behavior.