ProductAtlas documentation
ProductAtlas is a public knowledge platform for reusable, production-informed Blueprints. Builders can discover strong product specifications and publish what they learned building so people and AI agents can start with better product context.
A Blueprint captures the problem, desired outcomes, requirements, user stories, acceptance criteria, flows, security, telemetry, rollout guidance, recommended skills, and lessons learned.
ProductAtlas distributes product knowledge, not a finished application. Teams adapt a Blueprint to their own users, constraints, and architecture.
Start here
- Browse the Blueprint catalog to find public Releases.
- Get started to browse, connect an MCP client, or publish from Studio.
- Learn the Blueprint concepts before consuming a release.
- Connect to public MCP for anonymous, read-only agent access.
- Understand trust and safety before using third-party content.
- Publish a Blueprint to understand Publisher Studio.
The core promise
A Blueprint Draft is mutable working state. An authorized Publisher submits an exact Draft revision for checks and human review, then explicitly publishes an approved submission as a new, immutable Blueprint Release. Public users and agents consume Releases, never unpublished Draft state. That split keeps a retrieved version reproducible even as its Publisher continues authoring.
ProductAtlas currently exposes three public MCP tools: search_blueprints finds
compact release summaries, get_blueprint retrieves bounded detail, and
get_blueprint_markdown resolves a portable exact-version document. The public
MCP endpoint is anonymous and read-only.
Deeper customer-facing asset processing and semantic or AI quality evaluation are Planned. Current Studio quality guidance is deterministic structural readiness, and a displayed trust signal describes only its named check and scope.