ENTITY Documentation Portal
Integration · ENTITY v3.4.3

Adapters & Connectors

Connectors translate between external systems and ENTITY; they must not silently convert external possession, cloud tenancy, account state or transport access into ENTITY authority.

Current runtime: ENTITY v3.4.3. Provider-neutral connectors are adoption/custody surfaces. Provider custody remains distinct from authority and ownership.

Connector responsibilities

Read vs write

A read connector can ingest evidence without receiving authority to modify source systems. A write connector requires explicit scoped authority for the target action and must not infer that authority from an authenticated provider session.

Custody locators

Provider-neutral custody records should identify provider, locator and content commitment while explicitly preserving provider_is_authority: false. The locator describes where content can be found or accessed; it does not transfer sovereign control.

Failure isolation

Connector failure should not corrupt canonical ENTITY state. Record partial/rejected operations and make retries idempotent where possible. A failed provider call must not be rewritten as a successful ENTITY EVENT.

Version boundary

Use the v3.4.3 tagged adoption layer for current integrations. Historical connector/profile evidence remains under the exact release/version against which it was produced.