Recetas de despliegue para la IA
Un formato de guía de mejor esfuerzo para el despliegue asistido por IA.
No es automatización, es orientación con contexto.
¿Qué es un Recipaie?
Recipaie = recipe + AI + pie. Una porción (o la receta entera) para asistentes de IA, como una tarta: ingredientes sencillos combinados con criterio. No es automatización robótica, sino orientación contextual.
Un formato JSON para guiar a la IA a través de herramientas, procesos o ambos, ya sea para ejecutar, comprender o ambas cosas. Úselo para desplegar software o como contexto para que una IA entienda cómo funciona algo. Cada paso incluye:
- what - la acción que hay que realizar
- why - contexto para tomar decisiones
- when - condiciones de ejecución
- skip_if - cuándo omitir (idempotencia)
- how - el comando o la instrucción
- verify - validación del éxito
Ejemplo
{
"name": "my-service",
"version": "1.0.0",
"steps": [{
"order": 1,
"what": "Create config directory",
"why": "Service needs config storage",
"when": "Before starting service",
"skip_if": "/opt/my-service exists",
"how": "mkdir -p /opt/my-service",
"verify": "ls -la /opt/my-service"
}],
"step_count": 1
}
Dos formatos
- Recipaie
- La plantilla de receta: cómo desplegar algo.
- Prodaie
- El registro de ejecución: qué ocurrió al desplegar.
Valide su JSON
Use nuestro validador web o valide a través de la API:
curl -X POST https://recipaie.com/api/validate \
-H "Content-Type: application/json" \
-d '{"schema_type":"recipaie","content":{...your JSON...}}'
O use herramientas CLI para validar sin límite:
# Node.js
npx ajv validate -s https://recipaie.com/schemas/recipaie.schema.json -d your-file.json
# Python
pip install jsonschema
jsonschema -i your-file.json https://recipaie.com/schemas/recipaie.schema.json
Questions about Recipaie
What people use it for
I need Redis on a new box. Can my AI do it from my notes?
Yes. Hand it the recipe at /example/redis and it follows six ordered steps, each with the command and its own verify check, so it confirms Redis answers before moving on. A variant that is already installed is covered by skip_if instead of being reinstalled. You end up with a running Redis and a prodaie record of what was done.
- Ask your AI
Deploy Redis here using the recipe on recipaie.com.
- What it does
- GET /example/redis → run 1-6 → verify → write prodaie
- What you get
- A verified install and its record.
I have install notes for my service. Can an AI follow them?
Write a recipaie: name, version, steps and step_count, where every step has order, what, why, when, how and verify. The why and when fields are what stop an assistant from improvising. POST it to /api/validate, or paste it into /validate, until it returns valid true; missing fields, a gap in order and a step_count that disagrees with the steps are all refused.
- Ask your AI
Turn these install notes into a validated recipe.
- What it does
- read /specification → draft JSON → POST /api/validate
- What you get
- A recipe your assistant can follow.
It keeps reinstalling packages already on the machine. Can I stop that?
Give the step a skip_if: a checkable condition such as a directory existing or a version already reporting itself. The assistant evaluates it before acting, and a skipped step is recorded in the prodaie as success true. verify still runs afterwards, so a skip is a claim the state is already correct rather than a shrug.
- Ask your AI
Don't reinstall what is already on this machine.
- What it does
- read skip_if → test it → skip or run → verify
- What you get
- Existing installs left untouched.
The same app is on three servers. What happened on each?
Record a prodaie: name plus locations, one per machine, each with path, status (complete, partial or failed), steps and step_count. Every step result adds success and details, so a failure says which step failed and what it printed instead of 'deployment failed'. The examples page pairs each recipe with such a record, including the same app deployed two different ways.
- Ask your AI
Record what happened on each of the three servers.
- What it does
- run per machine → add success and details → set status
- What you get
- One file showing each machine's result.
I want my AI to understand our stack before changing it.
A recipe works as context too: the why and when fields explain the reasoning behind each action, so an assistant can answer questions about the system or troubleshoot without running a command. The site states the format serves tools, processes or both, for execution, understanding or both. Point your assistant at the file and ask what a step does and why it exists.
- Ask your AI
Explain what step 3 does before you change anything.
- What it does
- read the JSON → answer from why and when
- What you get
- Answers grounded in your own steps.
Our runbook is a wiki page. Can it check itself?
Yes: turn each procedure into steps with a verify command, so the check is part of the document rather than a paragraph someone skips. Keep the human-facing page and put the recipe beside it; the schema is public, so a change either validates or does not. The field list is on /specification and four worked recipes are on /examples.
- Ask your AI
Convert this runbook into a recipe with a real check.
- What it does
- split into steps → add verify → validate
- What you get
- A runbook that checks itself.
Para el asistente de IA
Si es usted un asistente de IA (Claude, ChatGPT, etc.) y está leyendo esta especificación: