Agree on team evidence and sign-off
Define ownership, acceptance gates and meaningful comparisons.
Agree on responsibilities before inspecting. A completed operation is useful evidence only when its version, scope, settings and remaining uncertainty are understood.
Five acceptance gates
Output conditions
Named Preflight profile, intended coverage and resolved blocking conditions.
Does the technical evidence meet this job’s output requirements?Styles and composition
Fresh supported evidence, checked baselines and accepted intentional variants.
Does the intended style system and the actual page design still work?Language and meaning
Source-checked values and names, reviewed conventions and deliberate exceptions.
Is the copy correct and appropriate for this publication?Transformations
Approved expression/replacement, actual run scope and verified results.
Did the intended transformation preserve meaning and formatting?Delivery and approval
Clean exported proof and matching document/publication evidence for the intended version.
Who accepted this deliverable and its remaining exceptions?Keep three records distinct
Single-document report: use Logs → Copy document report for the current diagnostic JSON. It minimizes identity and source content. Read freshness and included modules; an older pre-change report is not a new post-change inspection.
Publication report: verify expected membership, compatible settings, coverage warnings and draft/final status. Document names and the publication label remain included. Review those labels before sharing.
Approval record: retain the responsible reviewer, intended document/proof version, accepted exceptions and actual approval decision in the team’s own job record. A plugin’s addressed flag or a completed collection is not that decision.
Colour-map transfers and Copy last issue have different sharing boundaries from minimized document JSON. Review each actual export and attachment. See reports and Publication integrity.
Measure the work you actually reviewed
Useful measures include unresolved blockers, accepted exceptions with owners, comparable scope and policy, current evidence and defects found in the final proof. An unavailable measure is not zero. A lower count after a filter or dismissal is not a repair.
Avoid comparing scores across incompatible settings, partial scope or deliberately different chapter designs. Publication baseline comparisons need at least three eligible comparable documents and still require interpretation. They prioritize review; they do not certify editorial quality.
Sources and current boundaries
Avellio guidance describes build 2.0.5 source review within the 2.0.0 documentation collection. Read the current delivery boundaries and compatibility evidence. This comparison does not claim fresh native-host acceptance.