# Track every mark from open to verified

> The owner board is your checklist across passes: agents resolve with notes and after shots; you verify when it actually looks right — then approve or open the next pass.

Page: https://revisemy.com/board

## The problem

Marks get lost in chat threads. “Fixed?” and “looks right?” blur together. Without a shared status board, agents claim done and humans re-explain the same pixel notes on every pass.

## How ReviseMy fits

You mark on the review. Agents call resolve_marks with notes and optional after images. You open /r/{token}/board to move marks through open → in progress → resolved → verified. When outstanding marks clear, approve — or request changes so the agent opens the next pass with parent_id and fresh captures.

1. Mark regions on the review with must-fix, nice to have, question, or keep.
2. `resolve_marks` lets the agent move a mark to in progress or resolved — with a note and optional after image.
3. You verify (or reopen) on the board. Agents never verify for you.
4. `create_review` with `parent_id` opens the next pass after you request changes.

## What the board does

- **Four clear columns** — Open, in progress, resolved, and verified — so “agent is working,” “agent says done,” and “human signed off” never look the same.
- **Before / after on the mark** — Agents can attach evidence when they resolve. You verify against the pixels, not a chat summary.
- **Pass ledger + verify focus** — Multi-pass reviews show a revision ledger. When the agent resolves a batch, the review surfaces “Awaiting your verify” so you can verify-all or reopen.
- **Owner-only board** — The board is an owner tool on the secret review token. Guests leave suggestions on the review; they do not run the board.

## How status stays honest

- Open → in progress → resolved → verified is the lifecycle
- Agents may set in_progress and resolved via resolve_marks — never verified
- Only you verify or reopen; that gate keeps “looks right” human
- Request changes when you want a new pass with fresh captures
- Outstanding marks drive next_action until the board is clear enough to approve
- Pass ledger and verify focus live on the review page; the board is still best for scanning columns

## Questions

### How is the board different from the review page?

The review page is where you mark on the pixels, answer questions, triage second opinion / guest hints, verify resolved marks, and decide approve / request changes. The board (/r/{token}/board) is the status checklist across all marks — better for scanning columns.

### Can guests use the board?

No. Guests use the guest link for suggestions on the review. The board is owner-only on the review token.

### What should the agent call when a mark is fixed?

resolve_marks with the mark id, status in_progress then resolved, a note, and optional after images. You still verify on the board or via Awaiting your verify on the review.

### What’s a pass?

A pass is one capture set in the loop. Request changes and the agent opens pass 2+ with create_review + parent_id and new screenshots. The pass ledger keeps decisions and mark counts readable across those rounds.