Ownership Map¶

vendor-fabric owns external API connector integrations and vendor-backed sync capabilities for the Extended Data stack. Runtime agent orchestration belongs in agentic-fabric; this repository owns provider-backed capability functions and metadata that agentic-fabric can call through VendorData.

In This Package¶

Surface	Current owner
Connector registry and adapter metadata	`vendor_fabric.registry`
Optional-dependency machinery (extra lookups, install guidance, availability probes)	`vendor_fabric._optional`
Shared connector base classes	`vendor_fabric.base`
Capability declaration mechanism (`@capability` decorator, `CapabilityProviderMixin`)	`vendor_fabric.capabilities`
Connector fabric	`vendor_fabric.connectors`
VendorData facade with capability dispatch	`vendor_fabric.vendor_data`
Vendor CLI	`vendor_fabric.cli`
Cloud parameter adapters	`vendor_fabric.cloud_params`
Payload surface introspection for connector data methods	`vendor_fabric.surface`
AWS, Google, GitHub, Slack, Vault, Zoom, Anthropic, Cursor, and Meshy clients	`vendor_fabric.*`
Provider capability functions	`vendor_fabric.*.tools`
SecretSync Python binding facade	`vendor_fabric.secrets_sync`
Provider-backed capability metadata for downstream runtimes	`vendor_fabric.*.tools`

Outside This Package¶

Surface	Current repository	Install target
Base data primitives, generic containers, local file sync, inputs, logging, and workflows	`jbcom/extended-data`	`extended-data`
Agent crew discovery, runner selection, runtime adapters, and agent test fixtures	`jbcom/agentic-fabric`	`agentic-fabric`
Standalone Go SecretSync binary, if retained	`jbcom/secrets-sync`	`go install github.com/jbcom/secrets-sync/cmd/secrets-sync@latest`

SecretSync pipeline semantics, the Go runtime, CLI, GitHub Action, and gopy binding source belong in jbcom/secrets-sync. The Python facade belongs here because its useful Python shape is a vendor-backed sync capability over Vault, AWS, S3, and future providers. Agent framework packages, runtime adapters, and framework tool factories belong in agentic-fabric; they compose vendor capabilities rather than being provider implementations. MCP bridges are agent-facing transports and belong in agentic-fabric.