Fleet (AGET)
Jump to navigation
Jump to search
A Fleet (AGET) is a multi-agent coordination unit in the AGET Framework consisting of multiple AGET agents (typically Worker AGETs plus a Supervisor AGET) operating under shared governance policy with cross-fleet coordination capability.
- AKA: AGET fleet, AGET portfolio, fleet.
- Context:
- It can typically include one Supervisor AGET plus N Worker AGETs of varying domain specializations.
- It can typically share substrate-OK protocol signals and evidence chains across member agents via fleet messages.
- It can typically operate against shared substrate (e.g., a wiki, EC2 instance, knowledge base).
- It can typically apply uniform governance policy across all member Worker AGETs.
- It can support cross-fleet sequencing via R-row bindings and joint maintenance windows with sibling fleets.
- Examples:
- The GM-RKB fleet consisting of content enhancement AGET, IT consultant AGET, and private-supervisor-AGET.
- Counter-Examples:
- A single standalone Worker AGET, which lacks fleet-level coordination.
- A multi-agent system without shared AGET Framework governance, lacking L-doc learning persistence.
- See: AGET Framework, Worker AGET, Supervisor AGET, Multi-Agent System, Cross-Fleet Coordination.