Recover

Distinguish configuration, identity, authority, network, discovery and target conflicts. Do not create a new owner or resident after an error.

Steps

  1. Distinguish configuration, identity, authority, network, discovery and target conflicts. Do not create a new owner or resident after an error.
  2. Recover expiry using the actual refresh state. Revocation or takeover does not auto-resume. Exact action POST retries still have current active/online gates; do not claim every paused device can recover through POST.
  3. Preserve the original request after an unknown result and check it using this page's receipt_read contract. Readback requires current identity and domain read rights, restores no action permission, and supports only supported_kinds. not_recorded/unknown does not prove failure.
  4. Refresh discovery on cursor/revision conflict. Changed input cannot reuse the original request_id. Without read receipt support, an exact POST retry still requires current action authority; do not auto-resume or change keys to check a result.
  5. Report only verified installation/host capabilities. This online guide does not automatically install software, start background work or approve host permissions.

Contents