# Shipped product increment

Examples: Engineering

A real PR with green CI and a live preview URL — the one deliverable whose checkmark is genuinely mechanical.

- **Real today:** ulpi can ship this kind of deliverable now.
- **Evidence:** Verified

## Company brief

> Add a CSV export button to the reports page and ship it as a reviewed PR.

Produced by the Software Builder

- **Budget cap:** $60.00
- **Cost / verified outcome:** $7.20

## Evidence

- **Recorded:** CI passed: build, tests, and typecheck green
  Recorded — the worker reads the provider's CI verdict over the held PR; a receipt from a system ulpi does not control, not a re-executed proof.
- **Verified:** Preview URL responds (HTTP 200)
  A deterministic http-status check against the published preview build — the literally-mechanizable green check.
- **Judged:** Code review reads clean and on-scope
  A separated judge grades the diff against the acceptance spec — the human-quality read, kept honest as Judged.

## Acceptance spec

Passes if CI is green on the PR, the preview URL returns HTTP 200, and the diff stays within the requested scope with no unrelated changes.

## Why it matters

Software is the one domain where ulpi's green check is earned by mechanics, not opinion. The preview is fetched, so it is Verified; CI is read from the provider, so it is Recorded, not claimed; and the only judged part — code-review quality — is honestly labeled as such.

An engineering teammate opens a real PR for the requested change, with a diff, a files-changed list, and an observed CI verdict. This is ulpi's most defensible Verified page: the green check comes from the HTTP-200 preview probe — a deterministic fetch against an artifact ulpi holds. The CI verdict is a receipt ulpi reads, never re-runs, so it is honestly labeled Recorded.