What you will achieve now
A decision or test applied to «Minimum operations: logs, owner, backups and degraded mode».
- 1 Understand the criterion
- 2 Do a small practice
- 3 Save evidence
A brief note with what you did, what went well, what failed and what you would review afterwards.
- Assign a person responsible for each flow and its change decisions.
- Log enough to reconstruct an error without storing secrets or excess data.
- Design a verified backup and a manual mode when something fails.
Every flow needs an owner
AI is not responsible for a process. Assign a name and a role: an owner decides what the flow is for and when it is paused; an operator reviews alerts and backups; and a reviewer approves outputs that have impact. In a small company they may be the same person, but the roles must be written down.
FICHA DE OPERACIÓN flujo: clasificación de emails con borrador propietario: responsable de atención operador: persona que revisa alertas y accesos revisor: quien aprueba cada borrador horario y volumen esperado: laboral; hasta 40 al día acciones prohibidas: enviar, borrar, cambiar CRM o prometer condiciones contacto si falla: canal interno y proceso manual fecha de próxima revisión: YYYY-MM-DD
Useful logs, not a data dump
For each run store an identifier, date, flow version, status, source or minimum authorised input, rules that failed, approximate cost or usage and human decision. Protect access to those records and minimise personal text, attachments, keys and sensitive content. If you need to reproduce a case, keep a safe reference or an authorised copy—do not export every document into a flat log.
- Input: internal ID or minimised summary, not secrets.
- Process: prompt version, model, tool and validations applied.
- Output: status, key fields, evidence and reasons for abstention.
- Decision: approved, corrected, rejected or sent to a manual process.
registro_minimo: ejecucion_id: mail-2026-07-18-017 flujo_version: 1.2 estado: revisar entrada_ref: ticket-483 modelo_o_servicio: proveedor-configurado validaciones: [asunto_presente, datos_minimizados] evidencia: [base-conocimiento-v3/seccion-4] abstencion: false decision_humana: pendiente coste_estimado: 0.01 error_tecnico: null
A backup only exists if you can restore it
Back up the flow configuration, credentials stored securely, templates, rules, data needed to operate and restoration documentation. Then try restoring in a safe environment or with a non-production copy. A backup that no one has restored is a hypothesis, not a continuity measure.
- Separate configuration, business data, secrets and logs; not all need the same retention.
- Document who can restore and from where.
- Test a restore before you depend on the system.
- Update the backup when flows, access or tools change.
Design for failure before it happens
Write a response for four scenarios: the provider is down, the budget is exceeded, a validation fails or a duplicate input arrives. In all four cases, the flow must stop or degrade in a visible way. For repeated inputs, use an identifier and an idempotency rule: processing twice must not send twice, log twice or charge twice.
SI el proveedor no responde: guardar tarea en cola o crear borrador pendiente avisar al operador no reintentar sin límite SI se supera el presupuesto: pausar llamadas externas usar proceso manual o alternativa aprobada registrar el motivo SI una validación falla: estado = revisar no ejecutar acción posterior SI llega un duplicado: localizar ejecucion_id reutilizar estado o pedir revisión; nunca duplicar la acción
If you have saved the evidence for this lesson, continue with «Permissions and agents». If not, repeat the check before moving on.
Learn with a verifiable reference
Aulafy separates stable concepts from data that changes—versions, prices, models and commands. Check the course card for the review date, the verified scope and the primary sources.
«Editorial review» means structure, claims and sources have been reviewed. It does not mean every command has been executed: when a technical test exists, it will be marked as such.