# Adapter plan

**Draft boundary; no plugin API is released.**

An engine adapter maps start, send, inspect and stop to one real harness. It streams typed results and declares cancellation, resume and termination capabilities. An environment adapter owns workspace/process resources; a tool integration owns authorized resource operations. Avoid a general plugin framework until one real adapter validates these boundaries.

DreamLake service identity, model credentials and native harness login are separate. A new worker must demonstrate supported programmatic authentication; copying a personal login is not the proposed general mechanism. Credentials stay outside model messages.

Dependency order: minimal authorized tool loop → one adapter authentication/cancellation POC → reliable Babble transport and two-machine validation → manager agent. Bash isolation, full memory and elastic sandbox pools remain separate gated work.

[Transport gates](https://babble.dreamlake.ai/gates)
