Skip to content

Flavour manifest (kind: Flavour)

Package: mas-runtime · Schema: flavour.schema.yaml

Shipped flavours use apiVersion: flavour/v1. The schema currently validates apiVersion as a string without constraining it to a constant.

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.exposure_protocol Native/OTel export; MCP exposure protocol
Protocol / comm agent_comm protocol: local \| grpc \| hybrid, mode, emulation

Governance plugins that alter trajectory are declared through Agent governance[] (directly or via an Overlay). Agent control-plane plugins use control; Flavour selects deployment posture and plugin defaults.

A flavour that should mimic another product (for example an OpenClaw-like profile) composes overlays — with-hardened (undeclared-tool BLOCK + typed retry/circuit) plus observability plus later checkpoint/backtrack — instead of copying every plugin into the flavour YAML. See governance.md and reliability.md.

Schema fields

The schema keeps spec forward-compatible (additionalProperties: true). Its declared sections are:

spec field Purpose
agent_comm Agent-to-agent protocol, mode, emulation, and addresses.
capabilities Feature flags and capability overrides.
telemetry Basic telemetry sink configuration.
observability Observability plugin selection.
control Control-plane plugin selection.
tools Tool exposure protocol, remote-tool policy, and allow-list.
config Free-form deployment configuration; never store secret values.
operator Operator/provisioner metadata.

What does not belong here

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

Enforced by FlavourSeparationValidator and mas-lab check-config.

Selection at run time

Flavours select how this application exposes agents or tools. MCP consumption is not a flavour concern: a ToolServerRegistry with usage: use is an infra dependency. --bind NAME=mcp://… is a shortcut for that infra row, not a flavour switch. --flavour mcp selects tool exposure protocol. Internal agency stays in-process on flavour local until an Application endpoint (--infra-ref YAML or --bind NAME=a2a://…) sets usage: use.

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, mcp.yaml, local-benchmark.yaml). The scheduler resolves flavours via mas.lab.flavour.resolve.resolve_flavour_path() — do not copy flavour YAML into individual labs or samples.

See also