Skip to content

Extension Roadmap

Target Architecture — Final-State Design

This page describes how the Marketplace Platform extends beyond its final-state core. The eleven services, ten aggregate roots, six APIs, and five workers documented elsewhere are the baseline; the items here are planned extensions that preserve the same bounded-context boundaries, event envelope, and naming conventions.

The Marketplace is designed to grow without re-architecting. New asset types, commerce models, and autonomy capabilities slot into existing contexts or add new ones, always communicating through the canonical event envelope and following Naming Conventions.

Extension principles

  • Context-aligned growth — new capabilities extend an existing bounded context or introduce a cohesive new one; they never blur context boundaries.
  • Event-first — extensions integrate by publishing/consuming canonical events, not by reaching into another context's store.
  • Additive contracts — new event/API fields are additive; breaking changes get a version suffix. Consumers tolerate unknown fields.
  • Asset-type as a plugin — the nine asset types are an open set; adding a type is metadata + a quality/compatibility profile, not a re-platforming.
  • Governance by default — every extension is subject to publisher trust, signing, quality scanning, and audit.
  • Autonomy-ready — new surfaces expose machine-consumable APIs/events so the Agent Mesh can use them without a human UI.

Future services

Candidate service Context Purpose
AssetRecommendationService Catalog & Search ML-driven, context-aware asset recommendations for agents and users.
AssetBundleService Publishing & Versioning Compose multiple assets into curated bundles/solutions (e.g. Industry Packs as first-class bundles).
PublisherPayoutService Commerce Revenue share and payouts to external/partner publishers.
AssetCertificationService Publisher Formal certification tiers (security, performance, accessibility) beyond trust tiers.
AssetTelemetryService Reviews / Catalog In-product usage telemetry of installed assets feeding ranking and deprecation.
MarketplaceFederationService Catalog & Search Federate external/partner marketplaces into a unified catalog.

Future workers

Candidate worker Trigger Purpose
AssetVulnerabilityScanWorker scheduled / new CVE feed Continuously rescan released packages against new vulnerability data and flag/yank affected versions.
AssetDeprecationWorker usage/quality signals Auto-propose deprecation of low-adoption or superseded versions.
RecommendationIndexWorker install/usage events Maintain the recommendation model/index.
LicenseRenewalWorker schedule Proactively renew/notify on expiring licenses via billing.
BundleResolutionWorker bundle publish/install Resolve and validate multi-asset bundles.

Future APIs

  • GET /marketplace/recommendations — context-aware recommendations for a project/target.
  • POST /marketplace/bundles and POST /marketplace/bundles/{bundleId}/install — curated multi-asset bundles.
  • GET /marketplace/assets/{assetId}/usage — adoption and usage telemetry for publishers.
  • POST /marketplace/assets/{assetId}/certify — submit an asset for certification.
  • GET /marketplace/publishers/{publisherId}/payouts — publisher revenue/payout reporting.
  • Webhooks / subscription APIs so external systems can react to AssetPublished/AssetInstalled.

Marketplace expansion

  • External publisher ecosystem — open verified publishing to partners and community, with trust tiers, certification, signing, and payouts.
  • Cross-marketplace federation — a unified catalog spanning ConnectSoft and federated partner marketplaces.
  • New commerce models — usage-based and outcome-based pricing, trials, promotions, and bundled licensing via ConnectSoft.Extensions.Saas.Billing/Metering.
  • Additional asset types — extend beyond the initial nine (e.g. Data Packs, Compliance/Certification Packs, Model Packs) as the open asset-type set grows.
  • Multi-region catalog — globally distributed read replicas and package mirrors for low-latency discovery and install.

Agent opportunities

The Marketplace is built to be operated autonomously by the Agent Mesh:

  • Autonomous asset selection — agents query the catalog and recommendations to choose the best asset/version for a plan, then evaluate compatibility and install — all attributable to a task- id.
  • Self-curating catalog — agents propose deprecations, bundles, and quality improvements based on adoption and incident telemetry.
  • Publisher copilots — agents assist publishers by drafting metadata, remediating quality findings, and recommending pricing.
  • Compatibility autopilot — agents pre-compute compatibility matrices and dependency upgrade paths so installs are conflict-free before they run.
  • Governance agents — agents monitor trust, vulnerability, and review signals to recommend suspensions or trust-tier changes to Governance.

These extensions deepen the factory's promises — traceability, reusability, autonomy, governance, observability, and multi-tenant scale — while keeping the Marketplace a clean, event-driven, bounded-context architecture.

Continue to Overview, Bounded Contexts, and the sibling platforms: Template & Library Platform, Agent Mesh, Factory Studio, and Governance, Security & Compliance.