Skip to main content

How ProductAtlas works

ProductAtlas separates authoring from distribution so that agents can consume reproducible knowledge without seeing unfinished work.

The authoring, asset validation, review, and publishing sequence below is the planned lifecycle. 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.

Planned lifecycle: from idea to release​

  1. A Publisher—an individual or organization—owns a stable Blueprint.
  2. Contributors edit its mutable Blueprint Draft.
  3. Validation reports blocking errors and non-blocking warnings against an exact draft revision. Supporting assets must complete the required safety pipeline.
  4. Review evaluates the exact candidate revision without editing Publisher content.
  5. An authorized publisher selects a semantic version, license, attribution, and release notes, then publishes that exact revision.
  6. ProductAtlas creates a new immutable Blueprint Release. Publishing never changes an earlier release.

Each release snapshot carries its content, public safe assets, license, attribution, dependencies, trust results, publication metadata, and a deterministic content digest. A correction therefore becomes a new version; the historical release remains addressable.

From discovery to adaptation​

In the current public release, public search indexes the latest eligible release metadata, not drafts, withdrawn content, or private assets. Search returns compact summaries so a consumer can choose a match before retrieving full content.

The anonymous public MCP flow is:

MCP client
  -> Streamable HTTP /mcp
  -> search_blueprints or get_blueprint
  -> public catalog application service
  -> immutable Blueprint Release

search_blueprints supports text plus exact metadata filters and opaque pagination cursors. get_blueprint resolves an optional exact version and returns summary, standard, or complete detail. See the tool reference for the implemented contract.

Boundaries that stay visible​

  • Trust signals describe a specific check and subject; they do not guarantee that a Blueprint is correct or that an implementation will be secure.
  • Publisher-authored text and assets remain untrusted even after authentication, scanning, or human review.
  • Anonymous MCP is read-only and contains no draft or publication tools.
  • RavenDB stores application documents; binary assets and generated bundles are designed for Cloudflare R2. Only approved public derivatives belong in a release.