> ## 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.

# Workplans

> Use a workplan as the durable link between an engineering task and its evidence.

A workplan is the owning record for an implementation lane. It carries the investigation, decisions, task list, verification results, visual findings, and the final stop decision. Keeping these elements together prevents evidence from becoming detached from the work it is supposed to prove.

## Workplan identity

Each workplan has three identities that must agree:

* **Repository:** the canonical source repository that owns the work.
* **Source file:** the `docs/wip/YYYYMMDD/WORKPLAN_*.md` record.
* **Production route:** `https://app.eyeparity.com/<repo>/workplans/<slug>`.

The rendered route is reviewer-facing. The source resolver and provenance metadata establish which file produced it.

## Semantic review

A useful workplan review checks more than the outer page status:

| Layer      | Question                                                             |
| ---------- | -------------------------------------------------------------------- |
| Transport  | Did the route respond?                                               |
| Data plane | Did the workplan resolver return the intended source?                |
| Semantics  | Does the page contain the expected tasks and current status?         |
| Evidence   | Are referenced artifacts available, current, and mapped to the task? |
| Decision   | Is it legal to close, or does an actionable item remain?             |

## One owning record

Retries, proof reruns, and handoff notes normally update the same workplan. Create a separate workplan only for a distinct feature, repository boundary, owner lane, risk boundary, or independently shippable unit of work.

## Honest status

Keep a task open when any required evidence is missing. A validator pass can close a configuration task when the task makes no visual claim, but a user-visible documentation deployment remains open until the deployed pages are reviewed and captured through the production proof surface.