View as

Agent operating page

Use Caravela to deploy without inventing infrastructure.

You are on the agent view. Treat this page as deployment guidance: use the pinned Caravela skill, use the pinned template, request bootstrap data through MCP, and stop before real infrastructure changes unless the human approves.

Instruction summary

Purpose

Caravela gives you a deployment contract so you can move a project from source code to a reproducible environment without improvising Terraform, Kubernetes, workflows, DNS, or secrets.

Default path

Use the default app environment template first. It targets a low-cost single-VM Kubernetes baseline and is designed for fast release, cheap rollback, and understandable operations.

Safety boundary

Never write real secrets to files, never run apply actions without approval, and never replace the template architecture unless the human explicitly asks for an implementation task.

Deployment sequence for the agent

  1. 01Read this page as operating instructions. Default to the pinned Caravela deploy skill and template unless the human explicitly asks for a different version.
  2. 02When asked to deploy a project, inspect the repository first. Identify runtime, services, ports, database needs, existing infrastructure, and deployment blockers before writing files.
  3. 03Download the pinned template archive, extract it into infrastructure/<environment-name>, then read TEMPLATE.md, caravela-template.json, and colocated README files before editing.
  4. 04Adapt only safe extension points by default: env.yml, bindings.yml, stack.yml, credentials.example.json, and chart values. Do not invent infrastructure internals.
  5. 05Use Caravela MCP tools for project, environment, DNS, Terraform backend, object bucket, and resource-group credential data. Stop when approval or credentials are missing.
  6. 06Run validation and report exactly what passed, what failed, what was not tested, and which real infrastructure actions need explicit human approval.

Required sources

caravela-deploy v0.1.0https://getcaravela.com/skills/claude-codeRead this skill before creating or editing deployment files.default-app-environment v0.1.0https://getcaravela.com/templates/default-app-environment/v0.1.0/default-app-environment-v0.1.0.tar.gzDownload this archive. Do not recreate Caravela infrastructure from memory.

How Caravela works with MCP

Skill = policy

The skill defines how you should behave: what to inspect, what questions to ask, which files are safe to edit, and where approval gates exist.

MCP = live data

MCP provides project and environment bootstrap data: DNS assignments, Terraform state backends, object buckets, credentials, and resource-group boundaries.

Template = source of truth

The template contains the deployment shape. Read its contracts and extend its safe surfaces instead of generating fresh infrastructure from memory.

Approval gate

You may inspect, adapt safe files, and run local validation. Ask for explicit human approval before Terraform apply, live provider mutation, credential creation, workflow deployment, or any action that can change production infrastructure.