# Visual Feedback / Verification

Purpose: collect papers and technical systems that use rendered or observed artifacts as feedback for code/document/artifact generation and repair.

This folder mirrors the public board page:

- Web page: `notes-visual.html`
- Survey bucket: `3-Paper_Survey/visual-feedback/`

## Why This Bucket Exists

The project thesis is broader than any single image-to-code method:

> Agentic coding loops need multimodal verification to check whether rendered, visible, or behavior-level outcomes actually satisfy user intent.

Most works in this folder are concrete applications of that idea: web/UI, chart, SVG, PDF/LaTeX, slides, and browser-state repair. They are not all "our method"; they are evidence, neighbors, or design patterns we can borrow from.

## Current Organization

| Web Section | Local File | Role |
| --- | --- | --- |
| Cross-application card index | `render-feedback-card-index.md` | Markdown copy of the board's visual-feedback cards and takeaways |
| Document / scientific typesetting | `paperfit-2026-vision-in-the-loop-typesetting.md` | PaperFit as a concrete application of vision-in-the-loop continuation |

## Application Buckets To Grow

| Bucket | Examples currently tracked | What to extract |
| --- | --- | --- |
| Web / UI code | RRVF, UI2Code^N, WebCompass | screenshot rendering, relative visual ranking, browser-based judge |
| Chart / data visualization | RRVF, MSRL, Visual-SDPO | multi-granularity reward, chart semantic checks, visual defect attribution |
| SVG / vector graphics | RLRF | rendering-aware feedback when source-only execution is insufficient |
| Document / slides / PDF | PaperFit, Visual-SDPO on AeSlides | page-image verification, layout defects, source-level repair constraints |
| Interaction / browser state | HTMLCure, WebCompass | multi-viewport, scroll/click/hover/resize traces and state consistency |

## Entry Schema

Each paper/system note should include:

- Citation and links.
- One-line takeaway for our project.
- Problem and task form.
- Loop structure: observe/render, verify, feedback, revise.
- What evidence the verifier sees.
- What feedback is produced.
- Difference from our intended framing.
- Reusable design ideas.
- Limits and open questions.

## Citation Discipline

Before citing a paper in an article draft, re-check the official paper or repository. The board cards are working notes; dates, versions, and benchmark details should be verified from primary sources.