Automation retains requirements, revisions, proposals, reviews and delivery evidence with their exact source identities. Use that evidence to explain a decision's history. It does not replace the owning product's original operational records or prove a physical action occurred.
Read retained revisions and requests
Requirement Revision history keeps original text and author. The page shows the latest 100 revisions; the site export includes complete retained history. Native requests and lifecycle results remain attributable to their original command and source revision.
Read an uncertain request before preparing another mutation. A successful old receipt retains its historical meaning, while new work still needs current authority, source and recovery checks. Do not interpret the presence of a retained request as proof that its operation succeeded.
Download the site's records
At the real site, Owners and Supervisors can use Download site records. Complete the recent security check and store the private archive according to the organisation's records arrangements. It includes requirements, revisions, review and delivery evidence within the export's scope.
Inspect the archive's stated inventory and retain its relationship to source-product evidence. An export is not an automatic rollback or a restoration of external product effects. A native activation or physical action must still be established from its own retained result.
Practise with current grants
Use Open sample workspace where offered. It connects separate sample product sites through the same native workbench. Current real-site Author and Reviewer grants still apply; entering practice does not give every role. Check the visible workspace and product realm before each source selection or change.
Return to live workspace explicitly when finished. Do not transfer a sample approval or record as evidence of an authenticated production decision. Practice inputs can help people learn the workflow, but they do not qualify a customer's engineering, devices, carrier or physical process.
For a problem, retain the exact requirement, source, command and visible reason. Use the owning product's support and recovery process for its operational records, preserving the difference between source validation, interface operation and actual customer task acceptance.
Read service health and retain a diagnostic
Owner or Supervisor can open Health on the real site and read Checks. A service check does not establish that a native release was activated or an operational event completed. Follow the actual held native record or original request for those questions.
The Owner uses Support diagnostic and Download diagnostic with recent Accounts verification. The file contains build details and service status while excluding customer records and credentials. Confirm the downloaded file, keep it private and review it before choosing to share it. Downloading does not send a support message or reopen a native recovery hold.