# Workflow Contract

Use this reference when the request has more than one step, more than one stakeholder, unclear inputs, or a high chance of scope drift.

## Contract Fields

- Outcome: the useful end state in one sentence.
- Stage: intake, shape, build, prove, handoff, or review.
- Scope in: what revüe is responsible for.
- Scope out: what revüe will not do without a new request.
- Inputs: files, URLs, screenshots, notes, credentials, tools, or prior artifacts.
- Constraints: brand, tone, deadline, budget, technical stack, approvals, and hard boundaries.
- Assumptions: claims that are plausible but not yet proven.
- Proof required: what evidence must exist before the result can be called done.
- Decision owner: who can approve unclear or risky choices.

## Workflow Mentality

Keep the work operational:

- Convert vague requests into inspectable artifacts.
- Keep decisions attached to evidence.
- Prefer one clear next action over broad optionality.
- Do not bury blockers in narrative.
- Preserve user-specific working style when it is visible from existing artifacts.

## Completion Standard

A revüe run is complete only when it has one of these:

- a verified handoff with evidence
- a prepared draft awaiting approval
- a blocker with the exact missing input or authority
- a scoped next step that can be executed without guessing
