v0.10.1 - Documentation and Published Site Consistency¶

OrbitFabric v0.10.1 closes the documentation and published-site consistency pass after v0.10.0.

This release is intentionally narrow.

It does not introduce Mission Model semantics, CLI behavior, generated surfaces, JSON report fields, lint diagnostics, scenario behavior, runtime behavior, ground behavior, plugin execution or Studio-specific APIs.

Purpose¶

The purpose of v0.10.1 is to verify and preserve consistency between:

repository documentation
published documentation site
release notes
roadmap
README
reference documentation
MkDocs navigation

The milestone confirms that the public documentation baseline reflects v0.10.0 - Stability and Compatibility Contract before OrbitFabric moves toward the next extensibility boundary milestone.

Changed¶

v0.10.1 includes:

README wording clarification for Relationship Manifest family counts
repository documentation and published-site consistency audit
v0.10.1 release notes
roadmap release alignment
package and CLI version bump to 0.10.1

The README now separates:

19 admitted relationship families at the candidate surface level
46 emitted relationship records for examples/demo-3u/mission
17 emitted relationship families for examples/demo-3u/mission

This aligns README wording with the existing Roadmap, Architecture and Relationship Manifest reference documentation.

Boundary¶

v0.10.1 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

v0.10.1 is a documentation consistency and release-alignment milestone only.

Result¶

After v0.10.1, the public documentation baseline is considered consistent enough to proceed toward:

v0.11.0 - Extensibility Boundary Contract, no execution

That next milestone must still preserve the existing boundary:

plugins and downstream tools consume Core-owned structured surfaces;
they do not reconstruct Mission Data Contract semantics from raw YAML, generated files, CLI text or UI state.