# Worker packet

Use this packet when an agent receives bounded execution authority inside a project.

## Outcome

Describe the concrete state this worker should establish.

## Project boundary

- Project:
- Repository:
- Branch or worktree:
- Relevant paths:
- Owning COS:

## Sources of truth

- Governing specification or issue:
- Relevant decision records:
- Required scenario, contract, or doctrine:
- Current revision or date:

## Authority

### May edit

-

### Must not edit

-

### Escalate when

-

## Expected proof

- Tier: narrow / standard / release
- Required checks:
- Required runtime evidence:
- Required platforms or environments:
- Evidence destination:

## Heartbeat conditions

Report when the worker:

- starts execution;
- crosses or invalidates an assumption boundary;
- discovers a scope collision;
- becomes blocked;
- enters proof;
- requires new authority.

Do not narrate routine implementation activity.

---

# Closeout

## State

What state is the task actually in? Use accepted, partial, blocked, failed, or another explicit project state.

## Evidence

Name the revision, checks, scenarios, screenshots, traces, logs, or artifacts supporting that state.

## Next

What is the next known action if the work is not closed?

## Risk / Blocker

What uncertainty, environmental failure, scope collision, or missing evidence weakens the verdict?

## Ask

What decision, authority, or coordination is needed from the owning COS or human?