← Field Notes
SEP 11 · Clipped · via Chromatic docs Comparison ViewRelease Decision

Chromatic solved the accept-or-deny review loop years ago

Swap snapshots for answers and the loop transfers to any agent that produces output a human reviews. The baseline moves only when a reviewer accepts a change, so no answer is approved twice and the build blocks until the review happens.

Read the source ↗ attached to Comparison View →
watching

watching → emerging → established

A candidate behavior, not yet a published pattern. Early signal — worth tracking, not yet worth standardizing on.

10 documented sightings since Jul 2024 — every one traces to a dated source.

See the evidence →

Machine summary of the source

Chromatic compares each story to a baseline, the last known good state, and shows the reviewer only what changed. The reviewer accepts or denies each change. Accepting makes the new snapshot the baseline. Denying keeps the old one and fails the build, and an unreviewed change leaves the original baseline in force. Once merged, accepted baselines apply to the target branch, so no one accepts the same change twice. Teams can require the review before the change merges.

The summary above is generated; the note at the top is the editorial judgment. Primary source ↗