Skip to main content

Releases and reproducibility

Blueprint Drafts mutate; Blueprint Releases never mutate. This is the central lifecycle rule in ProductAtlas. The authoring, asset validation, review, and publishing details on this page describe the planned lifecycle.

Current public availability​

The current public release supports Blueprint discovery and retrieval through REST, the web marketplace, and MCP.

The current public release does not yet expose authoring or publishing workflows. The rules below explain the release model that current public retrieval preserves and that the planned publishing workflow will create.

Planned lifecycle: publishing creates, never overwrites​

Publishing operates on an exact draft revision and requires an explicit semantic version, release notes, selected license, attribution confirmation, eligible assets, authorization, and no blocking validation findings. A successful publish creates a new release document. It does not update an existing version in place.

If guidance needs correction, publish a new semantic version. Deprecating an older release preserves its history and can point to a replacement. Withdrawal can make content or assets unavailable while retaining auditable metadata.

What an immutable snapshot includes​

  • Blueprint and Publisher identity
  • exact semantic version and publication timestamp
  • release sections and safe asset references
  • license and attribution
  • namespaced Blueprint dependencies
  • trust results tied to the appropriate subject and digest
  • release notes, checksums, and deterministic content digest

This snapshot means later Draft changes, organization changes, or dependency Draft edits cannot silently alter previously published guidance.

Selecting a version through MCP​

get_blueprint accepts an optional exact version. Omit it to resolve the latest public release at request time; provide a semantic version to reproduce a prior result. The returned resolvedVersion, contentDigest, and canonical productatlas:// resource URI record what ProductAtlas actually served.

The literal string latest is not an immutable version identifier. Omit the version to ask for current latest, then retain the resolved exact version in downstream records.

See the MCP tool reference for retrieval detail levels.