Home
Design

Ownership Map

extended-data owns the base data layer. Surfaces outside that boundary were moved into repositories where their dependencies, docs, tests, and release cadence are first-class.

extended-data owns the base data layer. Surfaces outside that boundary were moved into repositories where their dependencies, docs, tests, and release cadence are first-class.

In This Package

SurfaceCurrent owner
Pure data functionsextended_data.primitives
Generic and shape-specific extended containersextended_data.containers
File import/export and codecsextended_data.io
Workflow composition and local file sync primitivesextended_data.workflows
Input loading and decoratorsextended_data.inputs
Structured lifecycle loggingextended_data.logging

Moved Out

Prior surfaceCurrent repositoryInstall target
External vendor API clientsjbcom/vendor-fabricvendor-fabric
Vendor capability dispatch and provider SDK adaptersjbcom/vendor-fabricvendor-fabric[...]
Meshy, Slack, Google, GitHub, AWS, Vault, Zoom, Anthropic, Cursor integrationsjbcom/vendor-fabricvendor-fabric[...]
Vendor-backed Python sync capabilitiesjbcom/vendor-fabricvendor-fabric[secrets-sync]
SecretSync agent tool wrappersjbcom/agentic-fabricagentic-fabric[...]
Agent framework integrationsjbcom/agentic-fabricagentic-fabric[...]

The old in-package connector and secrets namespaces are intentionally absent. That is a clean major-version boundary: code should depend on the package that owns the capability it uses.

Dependency Direction

The intended layering is dependency-inward:

extended-data
  <- vendor-fabric
       <- agentic-fabric

extended-data has no dependency on the higher layers. Higher layers may use extended-data primitives, containers, input handling, workflows, and logging without reimplementing those base concerns. agentic-fabric depends on vendor-fabric for provider coordination; vendor-fabric depends on extended-data for generic data behavior.