---
source_hash: 264f5282fcc0cbdae1c992ac24047ed54fc69c450621349c6d6af394bb943169
---

# Context Pack: Define Done as Thinking

## Gist

Decide how to accept or reject a result before asking a model to make it.

## Verbatim excerpts

> What exists, what proves it, and what you won't accept. Those three questions are enough to get started.

> A screenshot cannot prove a sign-in works.

## Working rules

- Name an observable artefact or behaviour.
- Choose evidence that tests the actual claim, including failure paths.
- State rejection criteria such as audience, voice, broken behaviour or scope growth.
- A template is useful only if it shapes the job.
- Correct missing decisions before adding prompt adjectives.

## Use and boundaries

Use this pack to understand the essay and apply its reasoning to a project. Read the full essay for its examples. Examples introduced as hypothetical are not claims about Ari's personal history. This pack contains no private teaching transcript.

## Links

- Essay: /documents/outcomes-and-systems/define-done-as-thinking
- Ordered practice: /courses/define-outcomes-build-products
- Related: /documents/outcomes-and-systems/context-is-king
- Related: /documents/outcomes-and-systems/hold-the-system

## Source

content/posts/outcomes-and-systems/define-done-as-thinking.mdx