# DeepWork — tools that shaped CodeVetter

> Canonical page: https://codevetter.com/inspiration/deepwork

Long agent tasks need explicit steps, artifacts, and quality gates.

## What we admire

DeepWork turns a loosely worded task into a procedure with required steps and checks. That is a useful model for work that cannot be trusted merely because an agent produced a polished final answer.

## The principle that stayed

A procedure should say what each step consumes, what it produces, and what makes it pass. When a gate fails, the handoff should preserve the failure and the remaining questions.

## Where CodeVetter stands

CodeVetter’s Evidence Pattern Search design names DeepWork-style procedures for review, fix, QA, and handoff. That reference is about workflow structure; DeepWork is not a required runtime or dependency.

## Sources

- [DeepWork source repository](https://github.com/Unsupervisedcom/deepwork) — the creator's own source
- [CodeVetter evidence-pattern design](https://github.com/Codevetter/codevetter/blob/main/docs/archive/PRD-EVIDENCE-PATTERN-SEARCH.md) — the CodeVetter project record

This is independent appreciation, not endorsement, partnership, code reuse, or feature parity.

## Public product links

- [CodeVetter](https://codevetter.com/)
- [Download](https://codevetter.com/download)
- [Documentation](https://codevetter.com/docs/)
- [Source](https://github.com/Codevetter/codevetter)
