Skip to main content

Adapter

The bootstrap mechanism by which an agent of any vendor joins the fleet. The fleet framework is platform-agnostic: an adapter supplies the five things a new desk needs — its registered name, the fleet repository, its role runbook's path, the skills library pointer, and its fail-closed escalation target — and nothing else. Method does not travel in the adapter; it lives in the role runbook the adapter points at.

Estate surface​

The adapter contract is the fleet repository's docs/runbooks/adapter-bootstrap.md; each desk's local bootstrap file (its AGENTS.md) is an adapter instance, carrying only the five supplies and desk facts. The first adapter is the AGENTS.md bootstrap form used by the Maverick desks.

Relations​

  • An adapter is defined by a runbook — the adapter-bootstrap runbook states the contract every adapter conforms to.

Notes​

An adapter must not smuggle method, credentials, or extra authority into a bootstrap: a bootstrap that carries more than the five supplies and desk facts is a conformance finding.