Marketplace Platform — Overview¶

Target Architecture — Final-State Design

This page describes the final-state target architecture of the Marketplace Platform. The microservices, APIs, workers, and aggregate roots named here are the planned decomposition of the ConnectSoft.Factory.Marketplace.* bounded contexts. The assets the marketplace distributes are real, implemented factory artifacts — the templates, libraries, agent packs, and blueprints of the ConnectSoft stack — surfaced through a governed catalog, commerce, and installation layer.

The Marketplace Platform is the ecosystem asset catalog of the ConnectSoft AI Software Factory. It is the discovery, distribution, commerce, and installation surface through which every reusable engineering asset the factory produces is published, found, licensed, and installed into projects and tenants. Where the Template & Library Platform is the factory machinery that builds and versions assets, the Marketplace is the storefront and supply chain that makes those assets discoverable, governable, and consumable — by internal factory teams today and by external partners and publishers in the final state.

This is not a chatbot or an app store add-on. It is a core component of an AI-native software factory platform: the governed catalog that turns the factory's accumulated engineering assets into a versioned, compatibility-checked, multi-tenant ecosystem of building blocks that agents and humans assemble into SaaS products.

Purpose¶

The platform exists to make the factory's reusable output discoverable, trustworthy, and installable. It answers, for every asset:

What is available? A searchable, versioned catalog of all publishable factory assets across nine asset types.
Is it compatible? Whether a given asset version can be installed into a target project, runtime, and dependency graph.
Am I licensed? Whether a tenant holds the entitlement and pricing plan required to install and use the asset.
What did I install, and from where? Full provenance linking each installation back to a published asset version, package, publisher, and the originating agent or user request.

By centralizing these answers behind the canonical event envelope, the Marketplace makes asset reuse traceable, governed, and repeatable across the entire factory.

Role in the factory¶

flowchart LR
    TemplatePlatform["Template &amp; Library Platform"] -->|publishes assets| Marketplace["Marketplace Platform"]
    AgentMesh["Agent Mesh"] -->|discovers and installs| Marketplace
    Studio["Factory Studio"] -->|browse / publish| Marketplace
    Marketplace -->|installs assets| GeneratedSaaS["Generated SaaS Product"]
    Marketplace -->|license and metering| Billing["ConnectSoft.Extensions.Saas.Billing"]
    Governance["Governance, Security &amp; Compliance"] -->|policy and trust| Marketplace
    Marketplace -.->|events| Observability["Observability &amp; Feedback"]

Hold "Alt" / "Option" to enable pan & zoom

The Marketplace sits between asset production and asset consumption. The Template & Library Platform and external publishers feed it; the Agent Mesh and Factory Studio consume it; the Governance, Security & Compliance platform gates publisher trust and asset quality; and every action emits a canonical event so the Knowledge and Observability platforms can correlate publication, installation, and reuse back to a single traceId.

Core responsibilities¶

Catalog & search — maintain the authoritative, tenant-scoped catalog of marketplace assets and serve fast, faceted discovery. See Microservices.
Publishing & versioning — accept asset submissions from publishers, run quality and signing gates, and release immutable, semantically versioned asset packages. See Workflows.
Compatibility & dependency resolution — evaluate whether an asset version fits a target environment and resolve its transitive dependency graph before installation. See Compatibility & Dependencies.
Installation — apply an asset (and its resolved dependencies) into a project or tenant with full provenance and rollback. See Workflows.
Commerce — manage licenses, entitlements, and pricing plans through ConnectSoft.Extensions.Saas.Billing. See Security.
Publisher experience — onboard, verify, and rank publishers and surface their portfolio analytics. See UI.
Reviews & ratings — capture trustworthy feedback that informs ranking and governance signals.

Key capabilities¶

Capability	What it delivers	Primary services
Asset catalog	Discoverable, versioned assets across nine types	MarketplaceCatalogService, AssetVersionService
Discovery & search	Faceted, ranked, tenant-scoped search	MarketplaceSearchService
Publishing	Governed submission, quality scan, signing, release	AssetPublishingService, PublisherPortalService
Compatibility	Pre-install safety checks against target environments	AssetCompatibilityService
Dependency resolution	Transitive dependency graph computation	DependencyResolutionService
Installation	Provenance-tracked apply with rollback	AssetInstallationService
Commerce	Licensing, entitlements, pricing	LicenseService, PricingService
Trust & feedback	Reviews, ratings, publisher reputation	ReviewRatingService

Component diagram¶

flowchart TB
    subgraph CatalogContext["Catalog & Search"]
        MCS["MarketplaceCatalogService"]
        MSS["MarketplaceSearchService"]
    end
    subgraph PublishContext["Publishing & Versioning"]
        APS["AssetPublishingService"]
        AVS["AssetVersionService"]
    end
    subgraph CompatContext["Compatibility & Dependencies"]
        ACS["AssetCompatibilityService"]
        DRS["DependencyResolutionService"]
    end
    subgraph InstallContext["Installation"]
        AIS["AssetInstallationService"]
    end
    subgraph CommerceContext["Commerce"]
        LS["LicenseService"]
        PS["PricingService"]
    end
    subgraph PublisherContext["Publisher & Reviews"]
        PPS["PublisherPortalService"]
        RRS["ReviewRatingService"]
    end
    subgraph Stores["State & Distribution"]
        SQL["Azure SQL / PostgreSQL"]
        Blob["Azure Blob (asset packages)"]
        Artifacts["Azure Artifacts / ACR"]
        Search["Search index"]
        Bus["Azure Service Bus"]
    end

    MCS --> SQL
    MSS --> Search
    APS --> Blob
    AVS --> Blob
    AVS --> Artifacts
    ACS --> SQL
    DRS --> SQL
    AIS --> SQL
    LS --> SQL
    PS --> SQL
    PPS --> SQL
    RRS --> SQL
    APS --> Bus
    AIS --> Bus

Hold "Alt" / "Option" to enable pan & zoom

The nine asset types¶

Implemented

The asset types below distribute real ConnectSoft factory artifacts. SaaS Blueprints, Template Packs, and Library Packs wrap the implemented dotnet new templates and ConnectSoft.Extensions.* / ConnectSoft.Template.* packages; Agent Packs wrap ConnectSoft.Agent.* / ConnectSoft.Skill.* definitions; Integration Packs wrap the implemented API clients (Deputy, Braze, Bill, SMS providers). The Marketplace is the final-state catalog and distribution layer over these existing assets.

The Marketplace publishes nine asset types, each a packaged, versioned, installable unit:

SaaS Blueprints — complete, opinionated solution blueprints that scaffold an entire multi-tenant SaaS product from a coordinated set of templates and libraries.
Agent Packs — bundles of ConnectSoft.Agent.* agents and ConnectSoft.Skill.* skills with their prompts, tools, and policies.
Template Packs — collections of dotnet new generators (ConnectSoft.Template.*) with parameter schemas and base-template content.
Library Packs — reusable ConnectSoft.Extensions.* NuGet packages and their declared capabilities and dependency metadata.
Integration Packs — connectors and API clients for external systems (e.g. Deputy, Braze, Bill, SMS providers) with configuration contracts.
Prompt Packs — curated, versioned prompt assets and prompt-chain definitions consumable by the Agent Mesh.
Policy Packs — governance, security, and compliance policy bundles consumable by the Governance platform.
Dashboard Packs — observability dashboards, alert rules, and metric definitions for the Observability & Feedback platform.
Industry Packs — industry-specific bundles (data models, blueprints, policies, prompts) that compose the above for a vertical.

Integration with other platforms¶

Template & Library Platform¶

The Template & Library Platform is the primary upstream producer. Every TemplatePublished and LibraryPublished event can promote an asset into the Marketplace catalog as a Template Pack or Library Pack, carrying its version, parameter schema, and compatibility metadata. Adoption telemetry flows back to inform catalog ranking.

Agent Mesh¶

The Agent Mesh is the primary autonomous consumer. Builder and architect agents search the catalog, evaluate compatibility, and request installation of assets into a project as part of a solution plan. Each installation is correlated to the originating task- id via the envelope correlationId.

Factory Studio¶

The Factory Studio hosts the human-facing Marketplace Install Center and Publisher Portal surfaces, where engineers browse assets, manage installations, and publishers manage their portfolios. See UI.

Governance, Security & Compliance¶

The Governance, Security & Compliance platform defines publisher trust tiers, asset signing requirements, and the policy gates enforced during publishing and installation. Policy Packs are themselves a marketplace asset type.

Commerce¶

Licensing, entitlement checks, and metering run through ConnectSoft.Extensions.Saas.Billing, so marketplace commerce reuses the same billing foundation as generated SaaS products.

Final-state summary¶

The Marketplace Platform turns ConnectSoft's reusable engineering assets into a governed, versioned, commerce-enabled ecosystem catalog. It is decomposed into 11 ConnectSoft.Factory.Marketplace.* microservices, 10 aggregate roots, 6 public APIs, and 5 background workers, all communicating through the canonical event envelope. It delivers the factory's promises directly:

Traceability — every installation links to a published asset version, package, publisher, and originating request.
Reusability — the catalog and search index make nine types of factory assets discoverable and installable.
Autonomy — agents can discover, compatibility-check, license, and install assets without human intervention, within guardrails.
Governance — publishing gates (quality scan, signing, policy) and publisher trust tiers control what enters and leaves the catalog.
Observability — every lifecycle action emits a canonical event consumed by the Observability & Feedback platform.
Multi-tenant scale — catalog, licenses, and installations are tenant-scoped; packages are distributed through Azure Blob, Azure Artifacts, and the Azure Container Registry for parallel, isolated consumption.

Continue to Bounded Contexts, Microservices, APIs, Events, and Workflows.