Agent Fleet
Jump to navigation
Jump to search
An Agent Fleet is a bounded set of software agents operating under shared governance, typically with one supervising agent and multiple worker agents.
- Context:
- It can share configuration standards, session protocols, and a common upgrade lifecycle, while each member retains its own domain scope and memory.
- It can be coordinated by a supervising agent that holds oversight capability — supervision being a capability of a member, not a separate agent type.
- It can range from a small personal fleet to an organizational Multi-Agent_System.
- It can be distinguished from an ad-hoc collection of agents by its shared governance and lifecycle.
- Example(s):
- A fleet supervisor coordinates version upgrades across its worker agents and verifies each member's deployment before closing a release cycle.
- A personal fleet in which one agent manages a public repository while siblings manage infrastructure and content, under one principal.
- Fleet (AGET) — the AGET framework's instantiation of this concept.
- Counter-Example(s):
- A Multi-Agent_System of independently-owned agents with no shared governance or upgrade lifecycle.
- A load-balanced pool of identical stateless service instances — replicas, not governed members with distinct scopes.
- See: Multi-Agent_System, Software Agent, Agent-Based_System, Fleet (AGET), Initialization Protocol, System_Governance.
References
- Published from the AGET framework; machine-readable concept: w3id.org/aget/vocab#Agent_Fleet