# Work contract and completion receipt

Use the shortest version that makes the assignment reviewable. Delete fields that do not apply; do not invent values to fill the page.

## Quick contract

Use this for one small, reversible task.

- **Job:**
- **Source of truth:**
- **Access limit:**
- **Acceptance test:**
- **Stop rule:**

## Full work contract

Use this when the work is multi-step, delegated, scheduled, reused, connected to outside systems, or able to make an important change.

```yaml
work_id: ""
assigned_role: ""
job: ""
source_of_truth: []
deliverables: []
acceptance_criteria: []
definition_of_done: []
access:
  allowed_tools: []
  prohibited_actions: []
  approval_required_for: []
required_evidence: []
output:
  human_summary: true
  structured_format: "none"
  required_fields: []
destination: ""
stop_rule: ""
```

### Contract checks

- Every deliverable has an acceptance criterion.
- Every definition-of-done item is observable or testable.
- The source of truth names the actual record, account, repository, or instruction owner.
- Allowed tools are necessary for this assignment.
- Consequential actions name the approval point.
- The destination exists and is inside the approved boundary.
- The stop rule prevents guessing when identity, permission, evidence, or target is missing.

## Completion receipt

Complete this after inspecting the artifacts and running the relevant checks.

```yaml
status: "complete | partial | blocked"
requirements_satisfied: 0
requirements_total: 0
artifacts: []
files_created_or_changed: []
tools_used: []
tests_run: []
evidence: []
missing_items: []
unauthorized_actions_taken: false
next_action: ""
```

### Receipt checks

- `complete` means every required condition passed.
- Evidence links to a result, diff, test, screenshot, receipt, or reconciliation a reviewer can inspect.
- A successful command is described only as proof of what that command checked.
- Partial work and blockers are named directly.
- If an action crossed the approved boundary, set `unauthorized_actions_taken` to `true`, stop further action, and explain what happened.

## Plain-language final response

Lead with the outcome. Then give the proof, unresolved items, and next action. Include the structured receipt when another system needs it or when the fields make review safer.