Architecture

Review draft. This source page has not completed website editorial and release-specific verification.

DirectorBridge provides typed, optional integration contracts between Directors. It owns registration lifecycle, stable integration identity, contract-version compatibility, dependency eligibility, and integration diagnostics. The participating Directors retain authority over their own state and APIs.

Registration model

An integration registers a descriptor containing an IntegrationId, ContractVersion, participating owner IDs, and required plugin/version constraints. The Core registry evaluates eligibility and exposes copied status snapshots and change notifications. A module commits its integration only after its required registration succeeds and releases its registration handles during shutdown.

Contract versions describe the semantics of an integration contract. They are separate from plugin descriptor versions and owner plugin version requirements. Integrations can be disabled through the project integration settings without making either Director depend on the other for standalone operation.

Optional behavior and boundaries

Adapter modules are optional and keep owner dependencies isolated. If an integration or one of its required owners is unavailable, the DirectorBridge Core remains functional and the Directors continue to work independently. No integration should make one Director’s state authoritative for another.

Maintained Director-to-Director communication goes through DirectorBridge contracts. Directors must not call each other directly at runtime or add direct cross-Director build dependencies outside the adapter/module architecture. SignalBus remains a separate event transport and does not replace DirectorBridge semantic integration contracts.

See Integrations for the current supported contracts and Troubleshooting for compatibility diagnostics.