Marketplace — later capabilities¶
Target
This page describes intended behaviour or structure. No implementation is claimed unless a section is explicitly marked Current implementation or Evidence.
No later-stage services.
The platform itself starts after Asset Publication (BC-04), the Factory's commercial context (BC-34) and fleet operations (D33) are in use. Beyond that start:
| Capability | Owner when built | Taken up when |
|---|---|---|
| Federated partner catalogs through A2A agent cards | BC-27 with Control (ADR-0023) | partners run their own Factories |
| Curated collections per vertical (the examples section) | BC-27 | enough listings per vertical |
| Semantic search over listing documents through the knowledge platform | BC-27 with Knowledge | listing documents are ingested |
| Adversarial evaluation suites required for public tool and MCP listings | BC-27 with Evaluation | the governance threat corpora exist |
| Partner payouts through a payment connector | BC-28 with Integration | partner listings generate revenue |
| Enterprise agreements covering many tenants | BC-28 | an organization-level customer asks |
| Usage-based pricing of operated products per customer tenant | BC-28 with Fleet | fleet cost attribution exists |
| Offline installation bundles for on-prem | BC-27 | an on-prem customer asks |
| Regional marketplaces per residency | BC-27 with Data & Event | residency rules forbid cross-region listing data |