Integration Platform — Later capabilities¶
Target
This page describes intended behaviour or structure. No implementation is claimed unless a section is explicitly marked Current implementation or Evidence.
Principles retained from the former roadmap: provider, not code; adapters over forks; events stay canonical; governed by default (credential custody, rate limiting, signature verification, audit are platform properties); asset-type as a plugin; autonomy-ready APIs.
| Capability | Purpose | Trigger | Owner |
|---|---|---|---|
| Integration packs (descriptor, versioned clients, capabilities, profiles, webhook schemes, configuration forms) as marketplace assets seeded from the first-party clients | turnkey vendors | Marketplace platform live | BC-27 with BC-17 |
| Object-storage, data-warehouse, identity-provider (SCIM, SSO), messaging-channel (push, WhatsApp, chat), analytics and observability-vendor connectors | broader reach behind capability interfaces | generated-product demand | BC-17 |
| Provider certification suite expansion; rate-limit tuning from observed limits | connector operations | pilot evidence | BC-17 |
| Webhook replay negotiation after vendor incidents | recovery | first vendor incident | BC-17 |
| Vendor cost attribution; secret-expiry forecasting | FinOps and hygiene | usage accounting feed | BC-16, BC-17 with BC-05 |
| Every registered capability exposed as a governed MCP tool automatically | agent-operable integration | registry volume | BC-08 with BC-17 |
| Agent-drafted integration packs from OpenAPI or SDK specs for human review | faster onboarding | Software Factory pack agents | BC-17 |
| CloudEvents envelope profile for deliveries | interoperability | consumer demand | BC-17 with BC-42 |