DreamerOS

Connector As Turn

Every external system call is a governed turn through the integrity pipeline, not a webhook with a key.

The industry treats connectors as plumbing - paste a token, the data flows, the model reads whatever comes back. DreamerOS treats every connector ingest as a turn. The same pipeline that governs a chat message governs an external read: intent shaping, integrity checks, fidelity contract, signed receipt. A connector is not a side door around governance. It is governance applied to a different input source.

The spine is wired. The /connect surface lists every connected provider and the public connector inventory makes the gateway-versus-paste split visible per provider. Closing the loop for every read path (signed receipt per ingest, drift surfacing per provider) is the active sprint. Until that is end-to-end for a given connector, the page does not claim it.

Why this matters

When a connector returns data that the model never questions, the model becomes the laundry. Treating every connector ingest as a turn is what keeps the integrity contract from leaking out the side of the system.

Connector As Turn - Every external system call is a governed turn through the integrity pipeline, not a webhook with a key. Try DreamerOS free
98