t3-p2-05authored3–5h

Guardrails for risky files

requires: t3-p2-04

Spec

For any file touching persistence or production configuration - database migration scripts, config - require the agent to produce a dry-run diff for human approval before any file is modified. Document the mechanism.

Why this matters

Some actions are not worth any amount of autonomy, because the downside is unbounded and irreversible. Knowing where that line sits, and enforcing it mechanically rather than by intention, is the difference between fast and reckless.

Verify

No result yet. Run `learn verify t3-p2-05` locally, or push to trigger CI.

artifactartifact: guides/guardrails.md

unrun

judgejudge: guides/guardrails.md

unrun

Rubric

# t3-p2-05 — Guardrails for risky files

**Task:** For any file touching persistence or production configuration - database migration scripts, config - require the agent to produce a dry-run diff for human approval before any file is modified. Document the mechanism.

**Strong:** Directly answers every one of the review questions below in the affirmative, with specific evidence from the actual work, not a restatement of the task.

- Is the guardrail mechanical, or does it rely on remembering to be careful?

**Passing but weak:** The deliverable exists and technically satisfies the spec, but is generic, restates the task instructions instead of engaging with them, or only partially addresses the review questions below.

**Fails:** The deliverable is missing, or engages with none of the review questions below - e.g. it describes what was built without explaining the reasoning the task actually asks for.