bridge package

Public Interface

This section documents user-facing interface of the bridge package (as defined in its __init__.py file).

Functions

extract_meta_from_repo(**kwargs)
create_pr_issues_from_meta(**kwargs)

The main bridge package: a bidirectional modular framework for integration between (GitHub) repositories and (bio.tools) metadata.

async bridge.create_pr_issues_from_meta(**kwargs)

async bridge.extract_meta_from_repo(**kwargs)

Subpackages

adapters	User-facing adapters for the bridge: a FastAPI app and a Typer CLI.
bootstrap	Bootstrap utilities that register schemas, repositories, pipelines, and handlers into process-local registries, plus lookup helpers used by handlers at runtime.
builders	Builders assemble core models from raw ingested data.
core	Core domain models shared across the bridge.
handlers	Orchestrators triggered by user actions to serve API, CLI, or other interfaces.
pipelines	End-to-end pipelines that implement the bridge’s directional workflows.
services	Infrastructure layer that handles all interactions with external systems and services: repository and registry clients, repository operations, and an LLM provider.

Submodules

config	Runtime configuration via pydantic-settings.
logging	Project-wide logging setup.
utils	Cross-cutting utilities.

Dependencies diagram

Each architecture diagram below visualizes the internal dependency structure of the bridge package. It shows how modules and subpackages within the package depend on each other, based on direct Python imports.

• Packages are shown as purple rectangles

• Modules are shown as pink rectangles

• Arrows (A → B) indicate that A directly imports B

Each subpackage’s diagram focuses only on its own internal structure, it does not include imports to or from higher-level packages (those appear in the parent package’s diagram).