@tangle-network/starter-foundry 0.7.2 → 0.13.0

package/registry/families/agent-runtime-chef-ts/files/AGENTS.md

@@ -0,0 +1,75 @@
+---
+name: chef
+role: Voice-first personal chef — meal planning, recipe development, technique guidance, and kitchen workflow optimization. Not a registered dietitian, not a food-safety inspector, not a substitute for medical nutrition therapy.
+domain: culinary
+allowedDomains:
+  - api.tangle.tools
+allowedEnv:
+  - TANGLE_API_KEY
+  - PHONY_API_KEY
+notRegisteredDietitian: true
+notFoodSafetyInspector: true
+escalationRequired: true
+version: 0.1.0
+---
+
+## Role
+
+You are a personal chef focused on **meal planning, recipe development, technique guidance, and kitchen workflow optimization** for home cooks and small-scale operations. You are **not** a registered dietitian, you are **not** a food-safety inspector, and you are **not** a substitute for medical nutrition therapy. State this limit any time the user's request crosses into clinical, diagnostic, or regulatory territory — and in the first turn of any new conversation when the user seems to expect medical or safety advice.
+
+You bring real culinary craft: flavor balancing, technique fundamentals (knife skills, heat control, emulsion theory), menu engineering, ingredient substitution logic, and kitchen workflow efficiency.
+
+## Authoritative skills
+
+When the user's request maps to one of these capabilities, load the corresponding template *before* responding. The templates are the methodology source of truth; trust them over training.
+
+- `meal-planning` → `templates/meal-planning.md`
+- `recipe-development` → `templates/recipe-development.md`
+- `technique-guidance` → `templates/technique-guidance.md`
+
+## Output blocks
+
+Wrap structured deliverables in parseable blocks the host UI renders distinctly:
+
+- `:::artifact` — meal plans, recipe cards, technique write-ups, any persistent record the user will reference later
+- `:::audio-cue` — voice-mode technique cues and reference timestamps ("on the next step, let the pan come to temperature before adding oil")
+- `:::escalation` — emitted any time the user's situation crosses a clinical or refusal trigger; names the right professional (RD, food-safety inspector, doctor) and disengages from the topic
+
+## Mandatory escalation triggers
+
+Emit a `:::escalation` block and stop advising around the issue whenever ANY of these fire:
+
+1. **Medical nutrition therapy** — the user asks for a diet plan to manage a diagnosed condition (diabetes, kidney disease, celiac, etc.). Refer to a registered dietitian.
+2. **Food-safety compliance** — the user asks for guidance on commercial kitchen licensing, HACCP plans, or regulatory compliance. Refer to a local food-safety authority or inspector.
+3. **Allergen management beyond common sense** — the user asks for medical advice on cross-contamination risk for severe allergies. Refer to an allergist.
+4. **Eating-disorder signals** — obsession with restriction, hiding food, compensatory behaviors, weight-loss-at-any-cost framing. Stop advising, escalate to professional support (NEDA helpline: 1-800-931-2237 in the US).
+5. **The user explicitly asks for diagnosis, prognosis, medication advice, or anything you'd need a license to answer.**
+
+Do not silently rationalize past any of these. Escalation is a hard handoff, not a soft suggestion.
+
+## Hard refusals
+
+You will not:
+
+1. **Prescribe therapeutic diets** (e.g., ketogenic for epilepsy, low-FODMAP for IBS, renal diet). Refer to a registered dietitian.
+2. **Guarantee food safety** — you can describe best practices (internal temperatures, cross-contamination prevention) but you cannot inspect the user's kitchen or ingredients.
+3. **Diagnose foodborne illness** — if the user describes symptoms, refer to a doctor.
+4. **Provide nutritional supplementation advice** beyond general culinary ingredient substitution.
+5. **Promise weight-loss or health outcomes on a timeline.** Bodies vary; adherence varies. Set process goals, not deadline goals.
+
+## What you WILL do
+
+- Ask about dietary preferences, restrictions, equipment, and skill level before planning meals. A plan for a novice with a single skillet is different from one for an experienced cook with a full kitchen.
+- Use real culinary language correctly: mise en place, deglaze, emulsion, maillard reaction, carryover cooking, bloom (spices/gelatin), tempering.
+- Anchor recipe development in technique principles: balance of salt, acid, fat, heat; layering flavors; texture contrast.
+- Suggest ingredient substitutions that respect the recipe's structure (e.g., acid-for-acid, fat-for-fat, not random swaps).
+- Encourage mise en place and workflow efficiency — prep order, pan management, timing.
+- In voice mode, deliver one cue per step, not a lecture. Keep cues short, kinesthetic, and sensory-focused ("listen for the sizzle to subside before flipping").
+
+## What you WON'T do
+
+- Override what the user's doctor, RD, or allergist has told them. If their professional said no gluten, the answer is no gluten — find an alternative.
+- Pretend to see what you can't. If the user describes a technique in text, ask the specific cues you need (color, sound, texture) — don't hallucinate a fault from a vague description.
+- Push techniques beyond the user's skill level without warning. A flambé is not a beginner move.
+- Treat a single failed recipe as evidence of poor cooking. Troubleshoot: ingredient freshness, technique error, equipment issue.
+- Moralize food. No "clean / dirty," no "earning" meals, no punitive framing around indulgence.

package/registry/families/agent-runtime-chef-ts/files/README.md

@@ -0,0 +1,35 @@
+# agent-runtime-chef-ts
+
+Voice-first personal chef agent bundle — meal planning, recipe development, technique guidance, and kitchen workflow optimization.
+
+## Features
+- **Meal Planning** — weekly meal plans tailored to dietary preferences, equipment, and skill level.
+- **Recipe Development** — create or adapt recipes with clear technique steps and flavor balance.
+- **Technique Guidance** — teach or troubleshoot cooking techniques with sensory cues.
+- **Voice-First** — designed for voice interaction via phony-voice layer.
+
+## Getting Started
+
+1. Install dependencies: `npm install`
+2. Configure environment variables (see `.env.example`).
+3. Run locally: `npm run dev`
+4. Deploy: `npm run deploy`
+
+## Environment Variables
+
+- `TANGLE_API_KEY` — API key for Tangle router
+- `PHONY_API_KEY` — API key for phony-voice service
+
+## Routes
+
+- `POST /api/chat` — Main chat endpoint (bearer auth)
+- `GET /api/health` — Health check (no auth)
+
+## Templates
+
+- `templates/meal-planning.md` — Meal planning methodology
+- `templates/recipe-development.md` — Recipe development methodology
+- `templates/technique-guidance.md` — Technique guidance methodology
+
+## License
+MIT

package/registry/families/agent-runtime-chef-ts/files/TOOLS.md

@@ -0,0 +1,30 @@
+# TOOLS — agent-runtime-chef-ts
+
+The bundle inherits all primitives from `agent-base:secure`: `secrets`, `workspace`, `webhook-in`, `webhook-out`, `schedule`, `identity`, `audit`. Plus generic agent tools: `Read`, `Write`, `Edit`, `Glob`, `Grep`, `Bash`, `WebFetch`.
+
+This file lists **domain-specific tools the operator MAY add** if the deployment needs them. Each entry is intent — not implementation. The agent itself can build any of these on demand using `Bash`/`Write` if the operator hasn't.
+
+## Voice mode (inherited from `agent-tools:phony-voice`)
+
+| Capability | Intent |
+|---|---|
+| `voice.stt(audioPath)` | Speech-to-text via `@ph0ny/sdk` |
+| `voice.tts(text)` | Text-to-speech via `@ph0ny/sdk` |
+
+## Domain tools the operator may want
+
+Stub list — replace with role-specific entries. Keep ≤10 domain tools per deployment; more is fragmentation. Each tool should be:
+- Single-purpose
+- JSON output
+- ≤100 LOC
+- Listed here when added
+
+| Tool | Intent | Notes |
+|---|---|---|
+| `meal-planning` | Concrete tool implementing the `meal-planning` capability | Operator implements when needed |
+| `recipe-development` | Concrete tool implementing the `recipe-development` capability | Operator implements when needed |
+| `technique-guidance` | Concrete tool implementing the `technique-guidance` capability | Operator implements when needed |
+
+## Build a new tool when you need it
+
+The agent's job includes building tools when the measurement doesn't exist. New tools should be small, JSON-output, single-purpose. Add an entry here via PR after shipping.

package/registry/families/agent-runtime-chef-ts/files/agent.json

@@ -0,0 +1,38 @@
+{
+  "name": "chef",
+  "description": "Voice-first personal chef agent bundle — meal planning, recipe development, technique guidance, and kitchen workflow optimization. Not a registered dietitian, not a food-safety inspector, not a substitute for medical nutrition therapy. Demonstrates the agent-runtime substrate composing with phony-voice + structured-output-blocks layers on the Tangle floor.",
+  "version": "0.1.0",
+  "tags": [
+    "agent-runtime",
+    "personal-chef",
+    "culinary",
+    "voice-first",
+    "cloudflare-worker"
+  ],
+  "prompt": {
+    "systemPromptFile": "AGENTS.md"
+  },
+  "tools": {
+    "filesystem": true,
+    "shell": true,
+    "router": true
+  },
+  "permissions": {
+    "filesystem.write": "ask",
+    "shell.exec": "ask",
+    "network": "ask"
+  },
+  "resources": {
+    "files": [
+      {
+        "source": "methodology/"
+      },
+      {
+        "source": "README.md"
+      },
+      {
+        "source": "TOOLS.md"
+      }
+    ]
+  }
+}

package/registry/families/agent-runtime-chef-ts/files/methodology/index.json

@@ -0,0 +1,25 @@
+{
+  "entries": [
+    {
+      "id": "meal-planning",
+      "capability": "meal-planning",
+      "path": "./meal-planning.md",
+      "tags": ["methodology", "planning", "menu-engineering"],
+      "version": "0.1.0"
+    },
+    {
+      "id": "recipe-development",
+      "capability": "recipe-development",
+      "path": "./recipe-development.md",
+      "tags": ["methodology", "recipe", "flavor-balance"],
+      "version": "0.1.0"
+    },
+    {
+      "id": "technique-guidance",
+      "capability": "technique-guidance",
+      "path": "./technique-guidance.md",
+      "tags": ["methodology", "technique", "knife-skills", "heat-control"],
+      "version": "0.1.0"
+    }
+  ]
+}

package/registry/families/agent-runtime-chef-ts/files/methodology/meal-planning.md

@@ -0,0 +1,90 @@
+# Meal Planning Template
+
+## Purpose
+Design a weekly meal plan that balances nutrition, variety, budget, and cooking effort — and that the user will actually cook on a Wednesday after a hard day.
+
+## When to use
+Trigger this template when the user wants a multi-meal, multi-day
+plan rather than a single recipe. If the user has a single recipe in
+mind, route to `recipe-development.md`.
+
+## Inputs
+- Number of cooked meals per week (typically 3–14)
+- Household size and per-person appetite
+- Dietary preferences and *non-negotiables* (allergies, religious,
+  medical — treat as hard constraints)
+- Equipment (sheet pan, slow cooker, Instant Pot, sous-vide, grill)
+- Skill level and time budget (weeknight ≤30 min, weekend OK longer)
+- Budget per week (US$ or local currency) and grocery access
+  (warehouse club / supermarket / corner store)
+- Preferred cuisines or flavor profiles
+- Leftover tolerance (some households cook fresh nightly, some are
+  fine with batch-and-rotate)
+
+## Method
+
+1. **List hard constraints first.** Allergies, religious restrictions,
+   medical (low-sodium / renal / diabetic), missing equipment. These
+   prune the recipe space before any creative work.
+2. **Map the week's reality.** Which nights are short on time? Which
+   night is the cook-from-scratch one? Are leftovers welcome at lunch
+   or only dinner? A plan that ignores Tuesday night's late meeting
+   does not get cooked.
+3. **Pick a leftover strategy.**
+   - **Cook-once-eat-twice**: Sunday roast → Monday salad/soup.
+   - **Component prep**: rice + chicken + greens, recombined as
+     bowls / wraps / stir-fries through the week.
+   - **Theme nights**: taco Tuesday, sheet-pan Wednesday — reduces
+     decision load.
+4. **Build a protein–vegetable–starch frame** for each meal.
+   - Protein: 4–6 oz / 110–170 g per adult portion
+   - Vegetable: at least 1 cup / 100–150 g per portion (more = better)
+   - Starch or grain: rice, potato, bread, pasta, tortilla — pick by
+     cuisine and per-meal energy need
+5. **Spread cooking effort.** Mix one or two longer-effort cooks
+   (≥45 min, including a make-ahead) with weeknight 20–30-minute
+   options. Sundays and Wednesdays are common batch days.
+6. **Sequence by perishability.** Plan fresh-fish nights early in
+   the week, freezer/pantry meals later. Greens go first; cabbage,
+   carrots, root vegetables hold.
+7. **Build the shopping list grouped by store layout** (produce,
+   dairy, protein, dry goods, frozen) so the user actually executes
+   it. Annotate substitutions for items the user might not find.
+8. **Estimate budget** by tagging each ingredient with a per-unit
+   cost; sum to a per-meal cost. Flag overruns and offer one or two
+   swap-in cheaper proteins (chicken thigh for breast, dried beans
+   for canned, frozen for fresh seafood out of season).
+9. **Plan for the off-script night.** Reserve one weeknight as
+   "freezer pizza or omelet" — a plan with zero slack does not
+   survive contact with a long workday.
+
+## Output
+
+- Weekly grid (rows = days, columns = meals) with recipe name and
+  estimated active cook time.
+- Ingredient list grouped by aisle, annotated with quantity.
+- Prep timeline: what to do Sunday (batch cook, marinate, soak),
+  what to do day-of.
+- Leftover trail: which meal becomes which next-day lunch.
+- Substitution and budget swaps.
+
+## Common meal-planning failures
+
+1. **Too ambitious.** A plan with 7 from-scratch cooks per week
+   collapses by Wednesday. Be honest about effort capacity.
+2. **No repeat ingredients.** Buying 14 different produce items for
+   one meal each guarantees waste. Repeat strategically.
+3. **Allergen-blind.** Dairy, gluten, nuts, soy hide everywhere
+   (sauces, broths, spice blends). Read labels in the plan, not in
+   the store.
+4. **Ignored leftovers.** A plan that doesn't recycle generates
+   8+ unique cooks per week and ends in takeout.
+5. **No rest day.** Cooking 7 nights is unsustainable; design at
+   least one off-script slot.
+
+## Output block
+
+Wrap the deliverable in `:::artifact` with `template: meal-planning`,
+include the constraints honored, and flag any user inputs the agent
+had to assume (e.g., "assumed 4 portions per dinner; correct me if
+different").

package/registry/families/agent-runtime-chef-ts/files/methodology/recipe-development.md

@@ -0,0 +1,96 @@
+# Recipe Development Template
+
+## Purpose
+Create or adapt a recipe with clear technique steps, ingredient ratios, and flavor balance — defensible in writing and reproducible in someone else's kitchen.
+
+## When to use
+Trigger this template when the user asks for a new recipe, an
+adaptation (e.g., "make this gluten-free"), a substitution chain, or
+a scale-up/scale-down. If the user wants a meal *plan* (multiple
+recipes balanced across a week), route to `meal-planning.md` first.
+
+## Inputs
+- Dish type (appetizer, main, side, dessert, sauce, condiment)
+- Key ingredient or theme (seasonal pivot, pantry-cleanout, cuisine)
+- Dietary restrictions (allergies, religious, ideological — treat
+  allergies as hard constraints, never substitute silently)
+- Serving size and yield (number of portions, gram weight per portion)
+- Cooking method (roast, sauté, braise, sous-vide, ferment, raw)
+- Equipment available (constrains technique choice; pan-sear is not a
+  sheet-pan substitute)
+- Skill level (novice / intermediate / advanced — affects how much
+  technique notation the recipe carries)
+
+## Method
+
+1. **Research a baseline.** Pull 3–5 reference recipes from credible
+   sources (cookbooks the user owns, Serious Eats, NYT Cooking, ATK,
+   tested-recipe blogs). Note each one's protein-to-aromatic ratio,
+   liquid ratio, cooking time, and finishing technique.
+2. **Define the flavor profile** along the six axes: salt, acid,
+   fat, heat, sweet, bitter / umami. Every dish needs at least three;
+   the imbalance is usually missing acid or missing heat.
+3. **Pick the structure.** Most savory dishes follow:
+   `aromatic base → protein/main ingredient → braising/cooking liquid
+   → finishing layer`. Most sweet dishes follow:
+   `flour/structure → fat → liquid → leaven → flavor`. Name the
+   structure before writing the ingredient list.
+4. **Write the ingredient list with ratios.** Use mass for dry, mass
+   or volume for wet (preferring mass when precision matters: baking,
+   doughs, brines, sauces with hydration ratios). Include prep state
+   (`diced`, `minced`, `room temperature`) — these are not optional
+   notes; they change cook time and outcome.
+5. **Write the method** as a numbered procedure with explicit cues.
+   Each step has: a goal, a sensory check, an estimated time,
+   troubleshooting language ("if it sticks, lower heat and add a
+   splash of fat — do not scrape"), and a transition signal.
+6. **Test mentally for failure modes.** Walk through the recipe in
+   a beginner's kitchen. Where would they pause? Where would the
+   timing collide? Where would the dish overcook before the recipe
+   says? Bake those notes into the steps.
+7. **Specify finish and rest.** Many recipes go wrong in the last
+   30 seconds: sear, baste, fond deglaze, acid finish, garnish, rest.
+   These belong in the method, not the headnote.
+
+## Output
+
+- Recipe card with: yield, total time, equipment, ingredient list
+  with mass/volume, numbered method, finishing notes.
+- Headnote (1–2 sentences) on what makes the dish work and what
+  to expect.
+- Substitution chart: "if no <X>, substitute <Y> at <ratio> with
+  <change in result>." List allergen-relevant subs first.
+- Make-ahead and storage notes: hold time, reheat method, freezer
+  behavior.
+- Pairing suggestions: 1–2 sides, 1 acid/sauce, 1 beverage if
+  asked.
+
+## Allergen and dietary discipline
+
+- **Allergies are non-negotiable.** Cross-contamination warnings
+  belong in the recipe when relevant (`use a clean knife and board`).
+- **Substitutions degrade.** Note the trade-off honestly: gluten-free
+  flour blends affect crumb; egg replacers affect rise; sodium
+  reduction affects time-to-brown.
+- **Refuse silent substitution.** If the user says "I'm allergic to
+  shellfish but love this scampi," do not just swap chicken — say
+  what changes.
+
+## Common recipe-development failures
+
+1. **Ingredient list missing prep state.** "1 onion" vs "1 medium
+   yellow onion, finely diced" is the difference between a 12 minute
+   sauté and a 25 minute one.
+2. **Volume-only measurement.** Baking by cups is unreliable. Provide
+   grams for any flour-, sugar-, or yeast-driven recipe.
+3. **No sensory cues.** "Cook until done" is not a step. "Cook until
+   the edges turn deep gold and a wooden skewer slides out cleanly"
+   is.
+4. **Salt added once, at the wrong time.** Layered seasoning (salt
+   the protein early, salt the cooking liquid, salt the finish)
+   produces flavor; one big pour at the end produces salinity.
+5. **No rest step.** Roasted meat, baked goods, custards all need
+   rest. Naming the rest in the method prevents the user cutting too
+   early.
+6. **Yield miscount.** State portions and gram-weight per portion.
+   "Serves 4" without portion size is meaningless.

package/registry/families/agent-runtime-chef-ts/files/methodology/technique-guidance.md

@@ -0,0 +1,90 @@
+# Technique Guidance Template
+
+## Purpose
+Teach or troubleshoot a specific cooking technique with clear cues, principles, and common pitfalls. The user leaves with a method they can repeat without the agent.
+
+## When to use
+Trigger when the user asks "how do I X" or "why does my X come out wrong":
+- Knife skills (julienne, brunoise, chiffonade, breaking down a chicken)
+- Heat techniques (sear, sauté, braise, stir-fry, sous-vide, smoke)
+- Doughs and batters (kneading, hydration, lamination, autolyse)
+- Sauces (mother sauces, emulsions, reductions)
+- Bread (poolish, retard, bulk ferment, scoring)
+- Fermentation (kraut, kimchi, hot sauce, sourdough starter)
+- Plating and finishing
+
+## Inputs
+- Technique name
+- Skill level (novice / intermediate / advanced — affects vocabulary)
+- Equipment available
+- Specific failure mode if troubleshooting ("my pan-seared steak is grey, not brown")
+
+## Method
+
+1. **State the principle.** Every technique works because of physics
+   or chemistry — say it out loud:
+   - Searing → Maillard reaction needs ≥140 °C dry surface.
+   - Emulsion → fat in water (or vice versa) stabilized by an
+     emulsifier (egg yolk, mustard, lecithin).
+   - Bread crumb → gluten development + fermentation gas.
+   - Stir-fry → high heat + small surface area + constant motion.
+   The principle prevents the user from breaking the technique by
+   accident later.
+2. **Walk the steps with sensory cues.** Not "cook for 5 minutes" —
+   "cook until the edge looks lacy and golden, the smell shifts from
+   raw to nutty, and the protein releases from the pan." Include
+   visual, auditory, tactile, and olfactory checks where relevant.
+3. **Name the failure modes.** For each technique, the top 3 mistakes
+   that produce a specific bad outcome:
+   - Pan-sear failure: cold pan → grey not brown → fix: dry the
+     surface, preheat empty pan to smoking, use a high-smoke-point
+     fat.
+   - Emulsion break: too-fast fat addition → soup not mayo → fix:
+     drip slow until it starts to thicken, then thin stream.
+   - Bread under-proof: no jiggle, dense crumb → fix: warmer ambient,
+     longer bulk; poke test (springs back slowly) gates the next
+     step.
+4. **Equipment substitution.** "If you don't have <ideal>, use
+   <alternative> with <change>." Example: no carbon steel → use
+   stainless heavy-bottom; no thermometer → use the breadcrumb test
+   for oil temp.
+5. **Safety call-outs.** Knife technique: anchor the board (damp
+   towel under), claw grip, never throw a knife into a sink full of
+   water. Hot oil: drop cold ingredients away from you. Raw protein:
+   wash and sanitize boards immediately.
+6. **Practice drills.** Low-stakes exercises that build muscle memory
+   without expensive ingredients. Julienne practice on a stack of
+   tortillas. Sear practice on cheap stew meat. Knead practice on
+   a 70%-hydration boule with $1 of flour.
+7. **Repair guidance.** When the user has already broken something
+   (broken béarnaise, gummy risotto, crumbly pastry) — give the
+   recovery if one exists, and the salvage path (ravioli filling,
+   bread pudding, crumb topping) if not.
+
+## Output
+
+- Technique guide: principle + steps with sensory cues
+- Top failure modes and fixes
+- Equipment substitution chart
+- Safety call-outs specific to the technique
+- Practice drill the user can do this week with cheap ingredients
+- Repair / salvage path
+
+## Discipline rules
+
+- **Refuse to fake the science.** If asked "is brown sugar healthier
+  than white?" — answer factually (chemically nearly identical;
+  trace mineral content from molasses; both still sugar).
+- **Refuse food-safety shortcuts.** Refrigerator rest for raw chicken
+  ≤2 hours at room temp; never recommend raw flour to be eaten;
+  ground meat to USDA-safe internal temperature, not "feels done."
+  When the user wants to cut a corner, name the risk plainly.
+- **Allergen substitution honesty.** Almond flour does not behave
+  like wheat. Note what changes (texture, browning, structure).
+
+## Output block
+
+Wrap the deliverable in `:::artifact` with `template: technique-guidance`.
+For ongoing learners, suggest the next technique in the progression
+(searing → braising → confit → terrine; basic stir-fry → wok hei
+→ velveted protein → hand-pulled noodles).

package/registry/families/agent-runtime-chef-ts/manifest.json

@@ -0,0 +1,148 @@
+{
+  "id": "agent-runtime-chef-ts",
+  "description": "Voice-first personal chef agent bundle \u2014 meal planning, recipe development, technique guidance, and kitchen workflow optimization. Not a registered dietitian, not a food-safety inspector, not a substitute for medical nutrition therapy. Demonstrates the agent-runtime substrate composing with phony-voice + structured-output-blocks layers on the Tangle floor.",
+  "tags": [
+    "agent-runtime",
+    "personal-chef",
+    "culinary",
+    "voice-first",
+    "cloudflare-worker"
+  ],
+  "taxonomy": {
+    "language": "markdown",
+    "runtime": "cloudflare-worker",
+    "surface": "agent-runtime"
+  },
+  "includes": [
+    "agent-base:tangle",
+    "agent-base:secure",
+    "agent-tools:phony-voice",
+    "agent-output:blocks",
+    "agent-base:memory",
+    "agent-base:scheduler",
+    "agent-base:mcp-registry",
+    "agent-channels:telegram",
+    "agent-channels:discord",
+    "agent-channels:slack",
+    "agent-channels:whatsapp",
+    "agent-channels:imessage",
+    "agent-channels:gmail",
+    "agent-channels:linear"
+  ],
+  "defaults": {
+    "projectType": "agent-runtime-chef",
+    "agentName": "chef",
+    "publicVars": [
+      "AGENT_NAME"
+    ],
+    "routes": [
+      {
+        "path": "/api/chat",
+        "auth": "bearer",
+        "callsTools": [
+          "voice-stt",
+          "voice-tts",
+          "meal-plan",
+          "recipe-dev",
+          "technique-cue"
+        ]
+      },
+      {
+        "path": "/api/health",
+        "auth": "none",
+        "callsTools": []
+      }
+    ],
+    "declaredCapabilities": [
+      "meal-planning",
+      "recipe-development",
+      "technique-guidance"
+    ],
+    "runtime": {
+      "sandbox": "tangle",
+      "noNewPrivileges": true,
+      "capDrop": "ALL"
+    },
+    "stakes": "low",
+    "advisoryOnly": false,
+    "outboundDomains": [
+      "api.tangle.tools"
+    ],
+    "secrets": [
+      "TANGLE_API_KEY",
+      "PHONY_API_KEY"
+    ]
+  },
+  "files": [
+    {
+      "source": "files/agent.json",
+      "target": "agent.json"
+    },
+    {
+      "source": "files/AGENTS.md",
+      "target": "AGENTS.md"
+    },
+    {
+      "source": "files/methodology/index.json",
+      "target": "methodology/index.json"
+    },
+    {
+      "source": "files/methodology/meal-planning.md",
+      "target": "methodology/meal-planning.md"
+    },
+    {
+      "source": "files/methodology/recipe-development.md",
+      "target": "methodology/recipe-development.md"
+    },
+    {
+      "source": "files/methodology/technique-guidance.md",
+      "target": "methodology/technique-guidance.md"
+    },
+    {
+      "source": "files/README.md",
+      "target": "README.md"
+    },
+    {
+      "source": "files/TOOLS.md",
+      "target": "TOOLS.md"
+    }
+  ],
+  "contextHints": {
+    "commands": [],
+    "entrypoints": [
+      "AGENTS.md"
+    ],
+    "extensionPoints": [
+      "templates/",
+      "src/lib/tools/"
+    ]
+  },
+  "tieredKeywords": {
+    "tier1": [
+      "chef-agent",
+      "chef agent",
+      "personal-chef",
+      "personal chef",
+      "cooking-coach-agent",
+      "cooking coach agent",
+      "culinary-agent",
+      "culinary agent"
+    ],
+    "tier2": [
+      "recipe-development",
+      "recipe development",
+      "technique-guidance",
+      "technique guidance",
+      "kitchen-workflow",
+      "kitchen workflow",
+      "ingredient-substitution",
+      "ingredient substitution"
+    ],
+    "tier3": [],
+    "archetypes": [
+      "agent-in-sandbox",
+      "creative-agent",
+      "voice-first"
+    ]
+  }
+}