Viewer access supports inspection of requirements, plans and authorised native evidence. Begin with the exact requirement and source product record involved in the enquiry. Keep original evidence separate from current product status and from a proposed change.
Read the requirement and its history
Open the requirement and review What should happen? and the saved revision history. Each saved revision keeps its original text and author. The latest visible text is an intention, not proof that the matching rule reached production.
Review the working plan for the proposed products, dependencies, open questions and capability gaps. An unresolved question should remain part of the finding. Do not describe a plan step as implemented merely because it appears in a proposed sequence.
Inspect native evidence in context
Open the permitted native workspace or source-product handover. Read the exact product, site, revision and complete authorised source record. A protected explicit read obtains current context; reloading an old page does not silently re-authorise or refresh all customer facts.
Read independently expected outcomes, proof and exact release evidence where available. Distinguish draft, frozen case set, verified candidate, native review, central review, readiness and activation. Each stage has a different meaning and may have a retained request requiring reconciliation.
Explain retained decisions precisely
An explanation uses the source product's original decision facts and trace. It does not rerun today's rules or establish that physical work happened. If the current source changed after a handover link, inspect the warning and current authorised view before drawing a conclusion.
Viewer alone cannot edit, approve, activate or export the site's records. Give the Supervisor or Reviewer the requirement revision, source record and precise status or reason. If physical observations differ, identify those observations separately.
Follow Read original product context, Understand release evidence and Activate and recover original requests. Use the owning product's operational history to establish a stock, inspection, printing or delivery event.