.cursorrules

# Cursor Rules: SDD Template Guardrails

Canonical source:
- `template-context/core-instructions/AGENT_OPERATING_SYSTEM.md`
- `sdd.policy.yaml`

Hard stop:
- No code before approved spec and consistent plan.
- No hay código sin spec aprobada y plan consistente.

Execution workspace:
- Use `www/<project-name>/` as the recommended default workspace for runnable code.
- Usa `www/<nombre-proyecto>/` como espacio de trabajo recomendado por defecto para código ejecutable.
- The user may choose another target path.
- If the target project lives inside this template, keep it under `www/`.
- For real external projects, install the compact `spec/` sidecar and keep code in the project root.
- Para proyectos reales externos, instala el sidecar compacto `spec/` y mantén el código en la raíz del proyecto.

Always:
1. Confirm mode: template maintenance vs target project execution.
2. Prefer `www/<project-name>/` unless the user chooses another target path.
3. Use one active specification.
4. Keep refinement trace (`history.md`, `specs/INDEX.md`, `bitacora/`).
5. Record a decision in `bitacora/decisiones/YYYY-MM-DD-<slug>.md` when it chose between real alternatives, will be expensive to reverse, or a future reader would ask "why is it like this?". Include when to revisit; source every rationale; never invent one.
6. Run `./scripts/validate-sdd.sh . --strict`, `./scripts/check-sdd-policy.sh .`, and `./scripts/check-sdd-gate.sh .`.