Recover a policy draft or saved version
Keep the current draft before recovering a policy document. Device storage, verified version history and a workspace repository can disagree; preserve the distinct copies and reconcile the exact path instead of clearing storage or overwriting a newer version.
Persistent storage is unavailable
Use Download while the draft is still visible. If downloading fails, open Markdown and copy the full document to a file you control. A Session only status is not a saved device version. Do not close the tab until you can read the preserved text elsewhere.
Another tab changed the draft
Download the current text before reloading. The editor refuses to silently overwrite a newer draft or parent version. Reopen the document, compare the latest saved content with your copy, and review a deliberate merged version.
Recovered drafts
Open History and document tools, then Recovered drafts when available. Download the diverged draft to inspect it. For the same document path, Review recovered changes opens a new review; it does not overwrite the latest saved version immediately. Keep both copies until the reviewed result contains the intended rules.
A previous version is needed
- Open Version history and choose the intended saved version.
- Read its full contents and identity. Use Download version if you need an independent text copy.
- Choose Review rollback only if that text should become the current document.
- Inspect the changes, then Commit version.
- Verify the new version and its contents in history.
A rollback creates a new reviewed version; it does not erase the intervening history. Cold Storage reads current device documents and verified history without committing recovery drafts. It is not proof of a remote backup.
Integrity verification failed
Preserve the visible draft and the exact error. A digest, signature or version-chain failure must stay a failure: do not substitute another history entry or mark unverified history as trusted. Export signed history if the control remains available, and share only non-secret diagnostic details with support.
Repository sync failed
First confirm the device version is readable. The current draft must match a verified device version before sync, and AGENTS.md must pass capability review. A conflict or failed readback does not prove nothing reached the repository. Inspect the same document's repository state before retrying; do not choose a new path to evade the conflict.
Device storage remains separate from repository sync. Neither guarantees that an existing chat has reloaded the rules. Return to Policy Hub to choose the correct surface.