What is a required view?
It is the angle or detail needed to answer the specific review question for this row.
Use one row to produce a view-by-view coverage ledger that another reviewer can reproduce.
A view-coverage ledger that distinguishes visible angles, obscured details, missing views, and evidence requests without issuing a quality verdict.
Quick FAQ
It is the angle or detail needed to answer the specific review question for this row.
They may be compared only when their stages and exact selection context remain visible.
Name the exact area, angle, and reason it matters to the row decision.
Record fields
For this photo coverage check, each field preserves a different part of the audit trail so a later reviewer can distinguish evidence from an unresolved question.
Review path
This path protects row identity first, then assembles a view-by-view coverage ledger; the order makes a later source change visible instead of silently overwriting it.
Decision states
Decision state 1: fully visible must remain explicit in the saved record.
Decision state 2: partially visible must remain explicit in the saved record.
Decision state 3: wrong angle must remain explicit in the saved record.
Decision state 4: view absent must remain explicit in the saved record.
Reusable output
A second reviewer should be able to retrace the source, compare the saved fields, and understand why the decision remains settled or open.
Required evidence 1: selection and image stage must remain explicit in the saved record.
Required evidence 2: required view must remain explicit in the saved record.
Required evidence 3: visible detail must remain explicit in the saved record.
Required evidence 4: missing or obscured area must remain explicit in the saved record.
Stop rules
A narrow unresolved state is more useful than a confident field assembled from mismatched evidence.
Keep the a view-by-view coverage ledger dated and tied to one exact row.