Integration guide

AgentPlat can be introduced incrementally. Keep the first deployment local and in-memory, then add persistence, peer transport and protected effects one boundary at a time.

Recommended progression

1. Use @agentplat/framework for a local agent and explicit model adapter.
2. Add @agentplat/collective-runtime when work requires multiple roles or recovery.
3. Add @agentplat/collective-host-postgres or the relevant persistence adapter for durable state.
4. Add @agentplat/collective-sync and @agentplat/mesh-protocol for authenticated peer exchange.
5. Add protected actions only after policy, identity, lease and evidence checks are configured.

Do not begin by exposing every tool to every agent. Start with a narrow capability catalog and expand it only when the evidence and policy boundary are clear.

Integration boundaries

The application owns model credentials, external side-effect idempotency and deployment secrets. AgentPlat owns coordination contracts, lifecycle state, policy decisions and evidence interfaces.