# Runtime Delta Task Content

Runtime and hybrid task definitions must include a complete `## Runtime Delta` section. The section must remain visible from task handoff through implementation summary and reconciliation.

Required content:

- Runtime target files: concrete repository-relative paths expected to change runtime behavior.
- Expected behavior change: a concise statement of the user-visible or automation-visible behavior delta.
- Verification commands with expected evidence: executable commands and the evidence that proves the behavior changed.
- Rollback path: concrete recovery steps or files to revert.

Invalid Runtime Delta content includes:

- Empty or placeholder text.
- Documentation-only paths used as runtime proof.
- Validation commands without expected evidence.
- Broad globs or prose in place of concrete target files.
- Runtime claims that are not connected to changed paths and executable evidence.

Contract tasks may state that Runtime Delta is not applicable, but they must not claim runtime implementation in closeout evidence.
