> ## Documentation Index
> Fetch the complete documentation index at: https://docs.eyeparity.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Quickstart

> Create a workplan-first EyeParity review loop.

This quickstart establishes the minimum workflow for a reviewable change. It intentionally keeps capture and deployment details separate from the evidence contract.

## 1. Choose the owning repository

Identify the product repository that owns the change. The workplan, task identifiers, and proof metadata must use the same repository identity. Do not place one product's evidence in another product's lane.

## 2. Create one owning workplan

Create the workplan in the repository's current dated WIP folder:

```text theme={null}
docs/wip/YYYYMMDD/WORKPLAN_<STABLE_SUBJECT>.md
```

Use a stable subject in the filename. The directory carries the date; the filename should not. Include the production EyeParity workplan URL, the corresponding data-plane URL, explicit tasks, acceptance criteria, and an evidence plan.

## 3. Define evidence before implementation

For each task, identify:

* the deterministic command, API field, or runtime fact that proves the behavior;
* the exact route and viewport that must be captured when the task is visual;
* the annotated proof artifact a reviewer will inspect;
* the condition that keeps the task open.

## 4. Implement and verify

Make the product or documentation change, then run the repository's governed diagnostics. A passing build or validator supports the result, but it does not replace current visual proof for a visible claim.

## 5. Review in production

Open the workplan through its `https://app.eyeparity.com/<repo>/workplans/<slug>` route. Confirm that:

1. the workplan data plane resolves;
2. the expected content is rendered;
3. cited artifacts are served and current;
4. open tasks remain visibly open;
5. completion language matches the evidence.

<Warning>
  Do not use a successful route shell or a stale screenshot as completion evidence. If the runtime was restarted or the route became stale, recapture the affected proof.
</Warning>