Marketplace Assets
Install an operation, not just a workflow.
Subbasis Marketplace is the ecosystem layer for reusable governed execution assets. It is designed to help teams install complete operational patterns, not only snippets.
What this means
Marketplace unifies reusable asset families:
- Execution Templates: ready operational workflow structures.
- Connectors / ACC Adapters: governed integration paths.
- Skill Packs: reusable operational skill guidance for agents.
- Agent Blueprints: role-oriented agent configuration patterns.
- Industry Packs: domain packaging for sector-specific operations.
- Governance Packs: reusable policy, approval, and evidence defaults.
Why it matters
Most teams do not fail because they cannot write one workflow. They fail because they cannot keep implementations consistent across operations, teams, and environments.
Marketplace assets improve repeatability:
- faster rollout with standardized building blocks
- better policy and evidence consistency
- easier review and update lifecycle
- controlled portability across organizations
How Subbasis handles it
Marketplace assets are described as governed execution components. They should be installable, inspectable, and version-aware.
Each asset type plays a different role:
- Execution Templates define process shape and expected checkpoints.
- Connectors / ACC Adapters define governed connector boundaries.
- Skill Packs define role-specific guidance and action style.
- Agent Blueprints define role, limits, and permission posture.
- Industry Packs group templates/connectors/skills for a domain.
- Governance Packs package policy and approval defaults.
Marketplace asset metadata
Useful metadata fields include:
- version
- author / publisher
- provenance
- required connectors
- required model resources
- required plan
- compatibility tags
- policy metadata
- permissions
- context schema
- evidence schema
- install preview
- sandbox install
- update / rollback
Example scenario
An agency wants to deploy a sales follow-up operation for multiple clients:
- Installs an Execution Template and Agent Blueprint.
- Adds CRM connector adapter with ACC-compatible policy settings.
- Enables Governance Pack requiring approval before external send.
- Reviews install preview and required model resources.
- Validates evidence schema before moving to production rollout.
The result is a repeatable operation package, not a one-off workflow.
What to configure
- asset selection by use case and domain
- connector/model prerequisites
- role permissions and approval requirements
- policy/evidence schema alignment
- update cadence and rollback process
- compatibility checks for environment and plan
Limits and deployment notes
- Asset availability and install options depend on deployment and plan.
- Marketplace monetization is a planned ecosystem path and should not be assumed fully live unless explicitly implemented.
- Teams should validate connector/model prerequisites before install.