Base de datos y esquema

Outcome: Complete the task with Base de datos y esquema (Database & Schema). User context: Una tabla de pedidos se enlaza con los clientes y limita los valores permitidos de moneda, cantidad y estado. Technical concept or control: Base de datos y esquema (Database & Schema). Why it fits: Usa un esquema para mantener los hechos verdaderos y explicar lo que significan los datos. Do not use it when: Nunca pongas todo tipo de datos en un mismo campo JSON sin verificaciones. Engineering requirements: Define inputs, outputs, contracts, and rules that must always hold. Set authorization and input checks. Define failures, timeouts, retries, one-time effects, data moves, and compatibility limits. Operations: Add useful signals and logs that hide sensitive data. Set capacity limits and write an operator guide. Test recovery and rollback. Acceptance criteria: Contract and failure-path tests pass. Data and authorization rules still hold during retries and partial failures. Check performance limits, monitoring, recovery, and rollback. Evidence and limits (evidence boundary): Ningún estándar oficial único controla todo el término. Su significado puede cambiar según equipos, plataformas o marcos. Unknowns to confirm: Where the code runs, data stores, traffic shape, consistency needs, and the security boundary. Also confirm the compatibility period, service goals, and rollback limits.