Generic Bridge and Native Adapter

A generic bridge is the fastest way to prove interoperability because it can exchange a shared file or API format and surface common finding fields quickly. It is a strong pilot path when the goal is to validate connectivity, normalize minimum viable data, and learn partner-specific edge cases without committing to a full integration.

A native adapter is the right choice when the integration must preserve partner-native object models, workflow and lifecycle state, and a partner-native user experience. It replaces flattened abstractions with versioned contracts and explicit failure handling, but it should be treated as planned work until it is built and tested. The maturity boundary matters: a generic bridge demonstrates compatibility, but it should not be described as native.