Skip to main content

Releases and reproducibility

Blueprint Drafts mutate; Blueprint Releases never mutate. This is the central lifecycle rule in ProductAtlas.

Current lifecycle​

In Publisher Studio, an authorized Publisher works on a private Blueprint Draft, edits sections, uploads supported assets, and previews deterministic structural readiness for an exact saved revision. Submitting that revision stores an immutable snapshot with the intended semantic version, release notes, license, and attribution.

After successful structural checks, every v1 candidate requires human review. Changes requested return the Publisher to the mutable Draft and a new submission. Approval authorizes publication but does not perform it. An authorized Publisher must explicitly use Publish release to create an immutable Blueprint Release that is public or unlisted from the exact approved submission.

Publishing creates, never overwrites. It rechecks the approved submission, authorization, evidence, and idempotency boundary server-side. A successful publish creates a new Release document and never updates an existing version in place.

If guidance needs correction, publish a new semantic version. An authorized Publisher can add or update reversible deprecation guidance and optionally point to a replacement Release. Withdrawal removes the Release from public eligibility and is permanent when initiated by the Publisher. Administrators can restore only an administrator-withdrawn Release; restoration never mutates the immutable Release.

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.

Public catalog search excludes unlisted and withdrawn Releases. REST, the public web, and anonymous read-only MCP retrieve eligible immutable Releases; they never expose private Drafts or review material.

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.

Planned extensions​

  • Deeper customer-facing asset upload and processing are Planned. A Release can reference only eligible public derivatives, but availability does not imply that every possible scanner or asset workflow exists.
  • Semantic or AI quality evaluation is Planned. Current readiness scoring is deterministic and structural.
  • Production Proven remains a future evidence process, not a result of publication, human review, or Publisher self-attestation.