# AI task completion contract

Complete this before a consequential action. The authoritative check should follow the result into the system that owns it.

## Authority

**Task / authorized requester:** ____________________

**Target object and stable identifier:** ____________________

**Intended final state:** ____________________

**Permitted action / approval boundary:** ____________________

**Identity and permission scope the action runs under (should be the minimum for this action, not the requester's full access):** ____________________

**Authority expires (time or condition):** ____________________

**State that must remain unchanged:** ____________________

**Authoritative verification method:** ____________________

**Expected processing delay / pending behavior:** ____________________

**Duplicate protection (idempotency key, pre-check, or destination guarantee):** ____________________

## Attempts

| Attempt / time | Action | Destination response | Observed final state | Evidence reference | Status |
| --- | --- | --- | --- | --- | --- |
|  |  |  |  |  |  |

Use a status that matches the evidence: drafted, submitted, pending, verified, partially complete, or failed.

## Uncertain result

**Duplicate consequence:** ____________________

**Pre-check / supported retry protection:** ____________________

**Stop and human-escalation condition:** ____________________

**Correction or recovery owner:** ____________________

**Rollback path if the action was wrong but succeeded:** ____________________

## Before the result is used

- [ ] The result was checked in the owning system, not inferred from the assistant's own report.
- [ ] Output passed to another system or person was validated for format, scope, and plausibility first.
- [ ] Any human approval given is recorded with who, when, and what exactly was approved.
- [ ] People affected by the change are informed where the business expects it.
- [ ] The log entry records requester, identity used, action, target, result, and evidence reference without copying sensitive contents.

## User-facing completion

**Confirmed result:** ____________________

**Unresolved items and next step:** ____________________

## Common failure modes

- "Done" means the request was sent, not that the destination accepted it.
- A retry after a timeout completes the action twice.
- The assistant's summary of the final state is taken as the final state.
- The action ran under a person's full permissions because a narrower identity did not exist.

Store evidence with access appropriate to the task; avoid copying sensitive contents into a broad activity log.

This contract covers one consequential action. It does not review whether the assistant should have this authority at all; use the agent authority review for that.