# Task brief

- Stable task key and project:
- Owner, session and version observed before claim:

## Outcome

Observable deliverable, problem and source evidence. State accepted decisions, non-goals and the authority for the work.

## Acceptance

Numbered checks that a reviewer can verify without this conversation. Leave no product decision hidden in a check.

## Spec

Accepted specification and implementation plan, pinned to a commit. List dependencies and integration order.

## Files

Permitted files and exact `path:start-end` context ranges. Include the current behavior and any shared table or interface contract.

## Verification

Exact commands, required environment and evidence to retain. Tests should exercise the layer being changed.

## Branch

Worker branch and worktree, base commit and PR target. State separately what integration or release requires.

## Invariants and test matrix, when risk requires

For auth, billing, routing, deletion, tenancy or multiple surfaces, state the behavior that must remain true and the paths to verify.

## Budget and readiness

- Authorized budget and cost basis, including preparation, work, reviews, retries and shared costs:
- Limit enforcement and overshoot reserve:
- Ready / blocked, with the specific missing input:

The six main fields form the execution contract. Complete the metadata and any applicable risk fields before dispatch; unresolved load-bearing inputs mean stop and ask.