> ## 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 and proofs API

> Read workplan source resolution and proof-package metadata from EyeParity.

EyeParity exposes repository-scoped workplan routes and Unit of Work proof packages. These APIs are part of the authenticated production data plane; tenant authorization applies where required.

## Resolve a workplan

```http theme={null}
GET /api/workplans/{repo}/resolve/{slug}
```

Use the resolver when the production route is known by repository and slug. A successful response identifies the resolved source and its API path. Treat a fallback page or unresolved source as a fail-closed result even when the outer HTML route responds.

## Read a dated source

```http theme={null}
GET /api/workplans/{repo}/{date}/{filename}
```

This form addresses a specific repository workplan file. Use the exact filename returned by the resolver or repository-scoped listing rather than inventing a path.

## Read a Unit of Work proof

```http theme={null}
GET /api/uow/{id}/proof
```

The response summarizes the Unit of Work and links its proof package. Proof packages may include acceptance evidence, verifier state, runtime identities, artifact hashes, and visual evidence URLs.

## Artifact URLs

Immutable Unit of Work artifacts use the production artifact surface:

```text theme={null}
/artifacts/unit-of-work/{id}/proof-package.json
```

Clients should preserve the returned artifact URL and identity instead of reconstructing storage paths. A local filesystem path is not a reviewer-facing artifact reference.

<Warning>
  Do not place credentials, cookies, OAuth codes, access tokens, or private tenant content in API examples, logs, screenshots, or proof metadata.
</Warning>