🍳 Kitchen Vocabulary
AgentOven uses a kitchen metaphor to make agent lifecycle management intuitive. Here are the key terms you'll encounter throughout the docs and CLI.
🏺 Oven
The control plane instance. It hosts the registry, router, workflow engine, and all supporting services. One Oven can manage hundreds of agents across multiple kitchens.
🍳 Kitchen
A workspace or project scope. Kitchens isolate agents, configs, and secrets per team or tenant. Think of it as a Kubernetes namespace for agents.
📜 Recipe
A workflow definition expressed as a DAG. Recipes chain agents, set conditions, and support fan-out/fan-in. Define complex multi-agent pipelines declaratively.
🧂 Ingredient
Any resource an agent needs — models, tools, prompts, data sources, or API keys. Ingredients are versioned and can be shared across agents in a kitchen.
🔥 Bake
Deploy an agent or recipe — build, validate, health-check, and launch into the runtime. A baked agent is live and serving requests via its A2A endpoint.
❄️ Cool
Gracefully pause or scale down an agent. It stays registered but stops processing tasks. Cool agents can be re-baked instantly.
👨🍳 Baker
A user or service account identity that registers, deploys, and manages agents. Bakers have RBAC roles scoped to kitchens.
📋 Menu
The agent catalog — a browsable directory of all registered agents and their A2A agent cards. The Menu enables agent discovery and composition.
How They Fit Together
A Baker creates a Kitchen, registers agents with their Ingredients, writes Recipes to orchestrate them, then Bakes everything into the Oven. The Menu lets other agents and teams discover what's available. When load drops, agents can be Cooled to save resources.
Baker → Kitchen → Agent + Ingredients → Recipe → Bake → Menu → Cool