Skip to content

Flavour manifest (kind: Flavour)

Package: mas-runtime · Schema: flavour.schema.yaml · apiVersion: flavour/v1 (or mas/v1)

A flavour is a deployment preset: observability export, transport, tool policy — not model API URLs (those live in infra manifests and agent models).

Terms: glossary.md · Hub: README.md.

Sits between application manifests and infrastructure: deployment profile for protocol, observability, tool policy, and RAG/skills backend.

Two aspects (your model)

Aspect Flavour sections Examples
Control / observation observability, telemetry, tools (tool-server enable, allow-list), mocking OTel backend, span export path, deny dangerous tools
Protocol / comm agent_comm protocol: local \| grpc \| hybrid, mode, emulation

Governance plugins that alter trajectory are usually declared on Agent plugins[] or via Overlay; flavour configures the runtime plane they attach to.

What does not belong here

Forbidden in Flavour Belongs in
model, api_base Agent models + infra LLMProxy
infra_refs config.yaml, MAS infra_refs, CLI --infra-ref

Enforced by FlavourSeparationValidator and mas-lab check-config.

Selection at run time

mas-ctl run-mas mas.yaml --infra-ref ./infra/prod-bundle.yaml

For benchmarks, select a flavour on the experiment or CLI:

mas-lab benchmark run experiment.yaml --flavour local

metadata.default_flavour on MAS provides the default name.

OSS mas-lab: canonical flavour YAML lives only under library-standard/src/mas/library/standard/flavours/ (local.yaml, local-benchmark.yaml, mock.yaml). The scheduler resolves flavours via mas.lab.flavour.resolve.resolve_flavour_path() — do not copy flavours/local.yaml into individual labs or samples.

See also