# Ticket Execution Template

Use this template at the start of each ticket (mentally or as a short note in PR/task comments).

## 1) Problem Statement

- What is broken or missing?
- Why does it matter now?

## 2) Scope

- In scope:
- Out of scope:

## 3) Acceptance Criteria

1. 
2. 
3. 

## 4) Impacted Areas

- Packages/files expected to change:
- External contracts affected (CLI/schema/policy): yes/no

## 5) Test Plan

- Unit tests:
- Integration checks:
- Manual verification:

## 6) Risks and Rollback

- Primary risks:
- Rollback approach:

## 7) Done Definition

- Code and tests complete.
- Required docs updated (`STATUS.md` always; ADR/`CONCEPT.md` only if needed).
- Remaining follow-up is captured explicitly.
