Fleet (AGET)

A Fleet (AGET) is an Agent Fleet instantiated under the AGET Framework that coordinates multiple AGET Agents under a shared Governance Policy with Cross-Fleet Coordination capability.

• AKA: AGET Fleet, AGET Agent Fleet, AGET Portfolio, Agent Seat Collection.
• Context:
  • input: AGET Agent Registrations, governance policy, Fleet Configuration
  • output: Fleet Coordination Decisions, Cross-Seat Evidence Chains, Fleet Health Reports
  • measure: Fleet Seat Count, Fleet Governance Conformance, Cross-Seat Drift
  • ...
  • It can (typically) contain one Supervisor AGET and multiple Worker AGETs, each holding a distinct Agent Domain Scope.
  • It can (typically) enforce a Uniform Governance Policy across member seats, covering Session Protocols, Skill Naming Conventions, and Evolution Document practice.
  • It can (typically) share a Fleet Substrate, such as a Wiki Substrate, a Compute Substrate, or a Knowledge Base Substrate.
  • It can (typically) propagate Framework Version upgrades through a Fleet Upgrade Lifecycle, so member seats converge on one Framework Release.
  • It can (typically) exchange Fleet Messages carrying Substrate-OK Protocol signals and Evidence Chains between seats.
  • ...
  • It can (often) designate Stewardship Ownership for shared vocabularies, so a Framework Vocabulary has exactly one Steward Seat.
  • It can (often) coordinate a Joint Maintenance Window across seats sharing one substrate, sequenced via R-Row Bindings.
  • It can (often) route work between seats via Inter-Agent Communication, such as an Inbox Handoff or a Steward Advisory.
  • It can (often) constrain a member seat to Read-Only Cross-Seat Access, so one seat may audit another without write authority.
  • It can (often) accumulate Cross-Seat Learning as Learning Documents that outlive any single Software Session.
  • ...
  • It can range from being a Personal Agent Fleet to being an Organizational Agent Fleet, depending on its Fleet Scale.
  • It can range from being a Homogeneous Agent Fleet to being a Heterogeneous Agent Fleet, depending on its Domain Specialization Spread.
  • It can range from being a Single-Portfolio Fleet to being a Multi-Portfolio Fleet, depending on its Portfolio Topology.
  • It can range from being a Loosely-Governed Fleet to being a Strictly-Governed Fleet, depending on its Governance Intensity.
  • ...
  • It can be distinguished from an Ad-Hoc Agent Collection by its shared Governance Policy and Fleet Upgrade Lifecycle.
  • It can suffer Canon Version Skew when member seats run divergent copies of a Canonical Specification.
  • It can exhibit Correlated Seat Error when multiple seats reason from one Contaminated Source Artifact, which resembles Independent Corroboration but is not.
  • It can require a Seat Abbreviation Registry if Skill Namespaces are qualified per seat.
  • ...
• Example(s):
  • the GM-RKB Fleet, composed of a content-enhancement seat, an analytics seat, and an infrastructure seat, sharing the GM-RKB Wiki as substrate.
  • the AGET Framework Fleet, in which a Framework Steward Seat owns Skill Naming Convention and Framework Vocabulary decisions for other seats.
  • a Supervised Agent Fleet in which a Supervisor AGET performs Fleet Health Checks and Fleet Version Sweeps across member seats.
  • a Cross-Portfolio Fleet spanning Agent Portfolios with differing Canonical Path Resolution layouts.
  • ...
• Counter-Example(s):
  • an Ad-Hoc Agent Collection, which lacks shared Governance Policy and a common Fleet Upgrade Lifecycle.
  • a Multi-Agent System of independently-owned agents, which coordinates behavior but shares no Framework Version or Learning Document practice.
  • a Stateless Service Replica Pool, whose members are interchangeable instances rather than seats with distinct Agent Domain Scopes.
  • a single standalone Worker AGET, which has no Cross-Fleet Coordination surface.
• See: Agent Fleet, AGET Framework, Supervisor AGET, Worker AGET, Multi-Agent System, Cross-Fleet Coordination, Governance Policy, Software Session.

---

References

2026

• Published from the AGET framework; machine-readable concept: w3id.org/aget/vocab#Fleet