RobotAtom recovery evidence tool

Keep a successful restore separate from permission to restart

Record what was restored, which dependencies were checked and who decided the release boundary. This tool does not run a restore, set a safe operating state or approve production.

Define the restore before recording the result

Entries remain in this tab until downloaded. Use document references, never passwords, licence keys, backup files or sensitive network details. Closing the tab discards the entries.

Trace the backup copy used in this exercise

Put the approved backup reference beside the copy actually retrieved and tested. Record the comparison evidence even if it reports a mismatch or cannot establish integrity. Do not enter backup files, secret keys or sensitive storage paths.

6 backup-copy trace fields remain open. Filling every field does not establish that the copies match or approve recovery.

  • Approved backup reference, creation time and scope
  • Copy used in the exercise and retrieval reference
  • Comparison or integrity-check evidence and exceptions
  • Actual target and applicable compatibility review
  • Dated exercise result, exclusions and witness
  • Reviewer disposition, restrictions and next action

This record reads no backup, computes no checksum and performs no restoration. Preserve mismatch, failure, rejection and restricted-use decisions in the download.

Change-impact review

Use this section when reviewing a changed configuration. Preserve the earlier result and record what needs review; blank fields mean no review recorded, not evidence that a change is harmless.

This free-text review does not determine compatibility, invalidate files automatically or authorise a restart.

Restore request authorised
Target compatibility reviewed
Controller restore observed
Dependent systems checked
Production release decision

5 milestone records incomplete

3 recovery-boundary fields remain blank. Record completeness is not recovery success. The release decision is currently: Not observed.

  • Restore request authorised
  • Target compatibility reviewed
  • Controller restore observed
  • Dependent systems checked
  • Production release decision

Generated locally; aggregate tool-use events contain no entered answers.

Check the update packet for required evidence references

Added 14 October 2026. Copy the references required by your review plan, then those listed in the proposed update packet. Use one exact record identifier or reference per line. This check reads text only; it does not retrieve documents or decide whether old evidence applies to the update.

Review withheld: no required reference set recorded.

Surrounding spaces and duplicate lines are ignored; case and all other characters remain significant. A renamed or superseded record needs a documented mapping from the review owner, not a silent substitution. Do not include secrets or private document URLs. Entries remain in page memory and clear on refresh.

Source context checked 14 October 2026: NIST AI RMF 1.0 Core (2023 framework, undated excerpt) and NIST SSDF v1.1 (final 3 February 2022). Their evaluation and release-artifact guidance informs the questions; this typed-list check is RobotAtom’s method, not a compliance assessment.

Read the AI robot update evidence guide. Keep update evidence separate from rollback and restart decisions. A complete reference list does not establish that its documents are accessible, unchanged or applicable.

What remains powered when the cell loses supply?

Record one interruption case and its evidence boundary. Keep missing observations and withheld restart decisions visible. This worksheet does not instruct you to interrupt power or test live equipment; qualified owners must define any authorised procedure.

Entries stay in this tab and local download. Aggregate analytics receives no typed values. Do not enter credentials, confidential drawings or sensitive installation details.

7 power-boundary fields remain open

  • Exact cell, controller, I/O supply configuration and dated drawing references
  • Interruption boundary: which supplies are lost, and under which event?
  • Retained supplies and loads, duration assumptions and evidence references
  • Expected and observed equipment states, including tools and held material
  • Qualified review of isolation boundaries, external feeds and stored energy
  • Authorised observation reference, conditions, deviations and untested cases
  • Restart disposition, restrictions, responsible owner and dated next action

Completing fields does not validate a supply, retained-load duration, isolation method, safe state or permission to restart.

Power interruption is a separate recovery boundary

Added 12 October 2026. Record lost and retained supplies separately from backup restoration. Universal Robots documents internal and external I/O supply configurations, and its Control Box 5.5/5.6 mains instructions warn against external equipment powering I/O during lockout. Those product-specific instructions do not establish what happens in your cell.

The worksheet checks missing references only. It performs no measurement, electrical calculation, isolation, power interruption or restart.

Read the electrical supply evidence guide

Which copy did this exercise use?

The backup-copy trace added 9 October 2026 keeps the approved record, retrieved copy, comparison evidence, actual target, observed exercise and reviewer disposition separate. It checks only whether references were recorded. It does not inspect a file, verify integrity or decide whether the copy is acceptable.

Source scope checked 9 October 2026: NIST's SP 1339 public abstract supports backup testing and recovery-exercise review; Universal Robots' versioned instructions document backup-file selection and a product-specific serial-number constraint. Neither prescribes this worksheet.

One controller is not the whole service

NIST SP 1339, final 17 June 2026, places OT backup testing and review within recovery exercises. Universal Robots' PolyScope 5.22 documentation warns that a new SD-card image with a mismatched serial number can leave a restore incomplete. The compatibility detail applies to that documented product; obtain the exact instructions for your actual target.

The milestone structure is RobotAtom's coordination method, not a vendor procedure or safety assessment. A failed check or withheld release stays visible even when every evidence field is filled.

Read the complete recovery guide · Discuss your recovery evidence