Integration releases identify tested combinations

A suite version describes named integration profiles, not a simultaneous release of every Constellation component.

The current immutable integration release is 0.1.0-alpha.6, which fixes the reviewed-local-copy/v1 governed-action composition and its public evidence-reader path. Earlier snapshots remain immutable and separately scoped: alpha.1 covers Maude consultation, alpha.2 saved-check attention, alpha.3 objective saved-check reading, alpha.4 the connected disposable cache, and alpha.5 the installed-cadence exercise. The mutable candidate catalog is not an installation manifest: select the exact release for your use case. Component versions, existing tags and release lines remain independent.

What a released manifest fixes

Each immutable snapshot names its profiles, exact public component commits, runtime/toolchain requirements, relevant configuration and schema versions, matching examples, documentation and qualification evidence. Artifact or dependency digests are included where used. The manifest schema version is separate from the suite version. No credentials or private installation prerequisites belong in a released profile.

The evolving family inventory answers what exists. A released manifest answers which exact combination was exercised. Family membership alone does not put a component in a tested release.

Release stages

• Alpha: a tested external integration path with explicit limitations; interfaces may still change. Support is best effort, without a guaranteed response time.
• Beta: an operator can actually live in the advertised path: evidence that it is stable and exercised, including relevant failures, recovery and day-to-day operation.
• Stable: an explicit support and compatibility commitment in addition to qualification evidence.

Changing a snapshot

Changed runtime pins or integration contracts require a new prerelease. Never move an existing release tag, replace published manifest contents, or regenerate a released manifest from current repository heads. If a proposed version already exists, select the next unused prerelease. Identify documentation-only corrections separately when tested runtime pins and contracts are unchanged; retain the original snapshot and link the correction.

Evidence and limits

A release must reproduce its advertised external example from public sources in a clean environment and verify relevant refusal, uncertainty and recovery. Synthetic inputs are labeled, and cannot replace the capability the profile claims to demonstrate. Recorded results do not establish present system state; settlement does not establish success or permit continuation.

General ECAD/design-flow readiness and unsupported federation are outside the first release. Qualifying one profile does not complete other tutorials or imply family-wide maturity. Start with the composition guide; use the support guide when a documented path fails.