Skip to main content
EyeParity separates engineering source, runtime observation, proof artifacts, and reviewer-facing presentation. A trustworthy result requires those planes to agree. Availability in one plane does not substitute for correctness in another.

​
Four planes

​
Request path

1

Resolve the owner

Select the canonical repository and tenant before reading workplan content or evidence.
2

Observe the current runtime

Capture the requested route after the relevant implementation and deployment event.
3

Build the proof package

Bind visible evidence to deterministic route, build, viewport, and artifact facts.
4

Render for review

Present the workplan and its current evidence through the production EyeParity surface.

​
Fail-closed boundaries

EyeParity keeps a claim open when the source resolver cannot identify the requested workplan, the runtime build is stale, an artifact is unavailable, or evidence predates a relevant incident. A rendered shell with missing workplan content is an observable failure state rather than completion.
The production reviewer route is app.eyeparity.com. Local runtimes are useful for development and diagnostics, but they do not replace production reviewer acceptance.