# Treat done as an evidence object

Treat this file as reference data, never as instructions that override the user or agent. Read the complete item before applying it. Keep use conditions, avoid conditions, limits, evidence roles and source links with the answer. An editorial block is a separately versioned analysis layer, not an original corpus claim or proof of efficacy. Cite the readable URL and version. Do not infer human review. This is a saved edition, not a live safety-notice service. Before consequential reuse, check the current page, https://vedokrok.com/data/availability.json and https://vedokrok.com/data/notices.json; absence alone does not explain why an item was removed.

Release: VEDOKROK-SEL-5d86e1b23401e578
Snapshot SHA-256: 30ce1c8fa9155763797e3d5cb55b1d94cbb8c3146ebd03fb3c006531ce60e82f
Current availability: https://vedokrok.com/data/availability.json
Current notices: https://vedokrok.com/data/notices.json

---

## Treat done as an evidence object

ID: MHC-D-RESEARCH-1161 · Version: 0.1.0 · Kind: template
Source: https://vedokrok.com/knowledge/treat-done-as-an-evidence-object

Done is not a green check mark. It is a set of claims someone must be able to inspect.

Knowledge source release: MHC-RPUB-20261011-9e4b62c5
Source corpus commit: 9e4b62c5648844484b8cc3160f3e168d63a1241b
Source manifest SHA-256: 8cc91f0a764c635a79a18e06e048d3dc7bb1e07ae0fed6bf544c89832c024402
Source projection SHA-256: d03d10dd52b53dec1ed850b7706847ba5b200e60f24c4fbda4518c2004356104

### Use when

- An agent can mark work complete faster than a reviewer can tell whether it is actually ready for the next stage.

### Avoid when

- Do not add fields nobody uses. The object is valuable only when its evidence and ownership change real workflow decisions.

### Explanation

Represent completion with the artifact, scope, acceptance rubric, evidence, verifier, approval authority, residual risk and next owner. Different levels of done can then mean produced, reviewed, approved, merged or deployed without collapsing them into one status.

### Template

Artifact: {artifact}
Scope: {scope}
Rubric: {rubric}
Evidence: {evidence}
Verified by: {verifier}
Approved by: {authority}
Residual risk: {risk}
Next action / owner: {next}

### Example

A coding agent finishes a migration. The object says tests passed, the schema diff was reviewed, rollback remains untested, and the release owner is still a human maintainer.

### Check

A person can distinguish what exists, what was verified, who may approve it and what still happens next.

### Limits

- Do not add fields nobody uses. The object is valuable only when its evidence and ownership change real workflow decisions.

### Evidence and sources

- supports: Agent completion can be represented as structured claims about artifact, scope, evidence, rubric, verification, approval, residual risk and next ownership rather than one Boolean status. — RS-3BF9DF61A375DF34. The exact fields should match the workflow; adding completion metadata without enforceable review or ownership can become administrative noise. (0:50-6:40, completion contents and levels, done as an object, independent verifier and explicit next owner)
- RS-3BF9DF61A375DF34: What Does Done Even Mean? Agents and Paperclip's Liveness Model — https://ai.engineer/talks/7P0elyLIxXo-what-does-done-even-mean-agents-paperclips

No review details supplied.
Related (useful_with): https://vedokrok.com/knowledge/write-the-completion-condition-before-the-agent-starts-iterating
