fleet
Fleet configuration models.
A fleet is a concert-of-concerts: multiple agent scores launched and managed as a unit. Fleet configs define score membership, group dependencies, and fleet-level operations.
Fleets are one level of nesting only: fleet → score → sheet. No fleet-of-fleets — sane limits to prevent recursive explosion.
Classes¶
Bases: BaseModel
One score in a fleet roster.
Each entry references a score YAML path and optionally assigns it to a group for dependency ordering.
Bases: BaseModel
Dependency declaration for a fleet group.
Groups without depends_on start immediately. Groups with depends_on wait for all named groups to complete their first cycle before starting.
Bases: BaseModel
Top-level fleet configuration.
A fleet launches and manages multiple agent scores as a unit.
Run like any score: mzt run fleet.yaml. Fleet-level operations
act on all members.
Example YAML::
name: marianne-dev-fleet
type: fleet
scores:
- path: scores/agents/canyon.yaml
group: architects
- path: scores/agents/forge.yaml
group: builders
groups:
architects:
depends_on: []
builders:
depends_on: [architects]