Skip to content

v0.12.0 - v1.0 Release Candidate Hardening

Status: Released
Scope: release candidate hardening toward v1.0.0
Release type: documentation, compatibility and release-alignment hardening

Summary

OrbitFabric v0.12.0 hardens the path toward v1.0.0 - Stable Mission Data Contract.

This release does not broaden OrbitFabric.

It introduces documentation and review surfaces that make the future v1.0 stabilization decision explicit, controlled and auditable.

The main additions are:

v1.0 Candidate Surface Inventory
Golden Output and Regression Confidence Policy
v1.0 Compatibility and Migration Notes
documentation ambiguity cleanup for the v0.12.0 hardening path

These surfaces clarify which existing OrbitFabric Core surfaces require stabilization review, how golden outputs should be selected before being committed, how compatibility and migration notes should be written, and which future topics remain outside the v1.0 Core scope.

Added

  • Added v1.0 Candidate Surface Inventory.
  • Added Golden Output and Regression Confidence Policy.
  • Added v1.0 Compatibility and Migration Notes.
  • Added all three hardening references to the MkDocs Reference navigation.
  • Added explicit v0.12.0 hardening wording to the documentation homepage.
  • Added roadmap guidance for release candidate hardening before v1.0.0.
  • Added contributor guidance for the v0.12.0 hardening phase.
  • Added an explicit disposition for security assumptions and command criticality contracts: valid future exploration, not a v1.0.0 blocker, deferred beyond v1.0.0 unless separately scoped.

Changed

  • Updated the package and CLI version to 0.12.0.
  • Marked v0.12.0 - v1.0 Release Candidate Hardening as completed in the roadmap.
  • Marked v1.0.0 - Stable Mission Data Contract as the next milestone.
  • Aligned README with the v0.12.0 release baseline.
  • Aligned the public documentation homepage with the v0.12.0 release baseline.
  • Aligned Quickstart, Development Guide, Contributing Guide and Versioning Model with the v0.12.0 release baseline.
  • Aligned Architecture and Project Charter headers with the v0.12.0 hardening baseline.
  • Clarified that v0.12.0 hardening references are review and governance documentation, not new Mission Data Contract semantics.
  • Clarified that candidate, preview and generated surfaces do not become stable v1.0 automatically.

Compatibility impact

v0.12.0 has no Mission Data Contract semantic impact.

It does not add, remove or rename Mission Model fields.

It does not change validation behavior, lint diagnostics, scenario execution behavior, JSON report fields, generated runtime-facing artifacts, generated ground-facing artifacts or Core-owned structured surface schemas.

The compatibility impact is documentation-only:

public documentation: updated
release alignment: updated
package version: updated to 0.12.0
Mission Model semantics: unchanged
CLI behavior: unchanged except reported package version
JSON report structure: unchanged
generated artifacts: unchanged
lint diagnostics: unchanged
scenario evidence behavior: unchanged

Architectural boundary

v0.12.0 intentionally does not introduce:

new Mission Model semantics
new YAML fields
new model domains
new CLI behavior beyond version reporting
new JSON report fields
new generated Core surfaces
new lint diagnostics
new scenario behavior
new golden files
new snapshot tests
new CI jobs
schema migration tooling
migration commands
compatibility scanners
JSON Schema publication
Mission Model security domain
security YAML fields
security enforcement semantics
plugin discovery
plugin loading
plugin execution
metadata schema
metadata parser
metadata loader
metadata validator
relationship graph
dependency graph
runtime behavior
ground behavior
Studio-specific API
stable v1.0 compatibility guarantee

v0.12.0 is a release candidate hardening milestone only.

It prepares OrbitFabric for v1.0.0 by reducing ambiguity, not by expanding scope.

Migration notes

No migration is required from v0.11.0 to v0.12.0.

Existing Mission Model YAML files, demo scenarios, lint workflows, JSON reports, runtime-facing generated artifacts, ground-facing generated artifacts and Core-owned structured surface exports remain compatible with the v0.11.0 baseline.

Users should note that the new v0.12.0 hardening references clarify future compatibility review expectations before v1.0.0.

They do not introduce new required actions for current users.

Validation expectation

The expected release validation remains:

ruff check .
pytest
mkdocs build --strict
orbitfabric lint examples/demo-3u/mission/ --json generated/reports/lint_report.json
orbitfabric gen docs examples/demo-3u/mission/
orbitfabric gen data-flow examples/demo-3u/mission/ --output-file generated/docs/data_flow.md
orbitfabric sim examples/demo-3u/scenarios/battery_low_during_payload.yaml --json generated/reports/battery_low_during_payload_report.json --log generated/logs/battery_low_during_payload.log
orbitfabric sim examples/demo-3u/scenarios/payload_data_flow_evidence.yaml --json generated/reports/payload_data_flow_evidence_report.json --log generated/logs/payload_data_flow_evidence.log

Release validation may additionally include:

orbitfabric export model-summary examples/demo-3u/mission/ --json generated/reports/model_summary.json
orbitfabric export entity-index examples/demo-3u/mission/ --json generated/reports/entity_index.json
orbitfabric export relationship-manifest examples/demo-3u/mission/ --json generated/reports/relationship_manifest.json
orbitfabric gen runtime examples/demo-3u/mission/
cmake -S generated/runtime/cpp17 -B generated/runtime/cpp17/build
cmake --build generated/runtime/cpp17/build
orbitfabric gen ground examples/demo-3u/mission/

Final statement

v0.12.0 completes the release candidate hardening layer before v1.0.0.

The next milestone is v1.0.0 - Stable Mission Data Contract.

That future release must explicitly select the final stable surface.

Nothing in v0.12.0 automatically makes every candidate, preview or generated surface stable.