{
  "edition": {
    "edition": "2026-09-06-draft-01",
    "language": "en",
    "publicationState": "published",
    "sourceRevision": "a7e788eb4b151fd92c1f58153e015773e3a829af",
    "projectCount": 67,
    "documentCount": 94,
    "skillCount": 10,
    "archivePath": "library.zip",
    "archiveBytes": 181812,
    "releasedAt": "2026-09-08T05:03:11.129+00:00"
  },
  "access": {
    "released": true,
    "rehearsal": false
  },
  "project": "background-services/recoverable-backups.md",
  "markdown": "https://legion.tw/api/projects/packet.md/background-services/recoverable-backups.md?edition=2026-09-06-draft-01",
  "documents": [
    {
      "path": "background-services/README.md",
      "text": "# Background automation and services\n\n[All project types](../README.md) · [Shared launch](../shared/launch.md)\n\nGive recurring work a dependable trigger, an understandable result, and a way for the person to inspect or control it.\n\n## Projects to build\n\n- [Watched-folder preparation](watched-folder.md)\n- [Recoverable backups](recoverable-backups.md)\n- [Meaningful change monitoring](change-monitor.md)\n- [Prepare tomorrow's information](tomorrow-briefing.md)\n- [Event-triggered follow-up administration](event-follow-up.md)\n- [Give the computer a batch of work](batch-work-queue.md)\n- [A personal overnight researcher](overnight-researcher.md)\n\nThese are instructions for projects you can build with your coding agent.\n"
    },
    {
      "path": "background-services/recoverable-backups.md",
      "text": "# Back up your work and recover it\n\nBuild a backup and recovery system for the folders, notes, and application records the person cares about. Build it extremely well around the work they want to preserve and the equipment they have. Follow the [shared launch](../shared/launch.md).\n\nBegin by identifying what would be painful to lose and what the person already uses for storage or backup. Choose a dependable approach using suitable existing tools and the capabilities of their applications. Make recovery part of the delivered experience.\n\n## Choose what is protected and where it goes\n\nSelect the actual work to protect, including the files and attachments needed to use an application's records again. Establish a backup destination appropriate to the person's situation and explain what it protects against.\n\nRecovering an earlier edit and recovering after losing the computer involve different needs. Help the person choose an arrangement that addresses the consequences they care about. Explain any extra storage, provider account, or cost before making it part of their setup.\n\nKeep the protected locations and backup destination recognizable. The person should be able to understand what is included, what is stored elsewhere, and what would need a separate recovery step.\n\n## Retain useful history\n\nKeep earlier versions so an accidental change or deletion leaves a recoverable copy. Choose a retention policy that fits the person's rate of work, available storage, and need to look back. Make the effect of that policy understandable.\n\nUse an appropriate way to capture application records while preserving a usable whole, including related attachments and information needed to reopen the work. Respect applications that provide their own export or backup operation.\n\nRun backups at a suitable schedule or trigger. Make an unavailable destination or interrupted run visible, and continue appropriately when it becomes available again. Retain useful existing backups while a new one is being made.\n\nGive the person a convenient way to inspect recent successful backups, see work awaiting protection, and run or pause the process. Show when a backup actually completed and what it covered.\n\n## Make recovery ordinary\n\nLet the person choose a file, folder, or relevant application record and find the version they need. Dates and useful context should help them recognize the right copy.\n\nProvide a straightforward way to recover into a place they can inspect. Make replacing current work a deliberate choice, with the current version retained where needed for recovery. The person should know which version they are opening afterward.\n\nInclude the material needed to use the recovered work. A report needs its photographs; a notes collection may need its attachments. Let the person reopen the result in the application that normally uses it.\n\nKeep the recovery instructions and any essential access information available through an appropriate arrangement the person controls. Explain how they would reach the backup if the original computer were unavailable.\n\n## Recover something on purpose\n\nDeliver the installed backup routine and demonstrate recovery using representative work. Make a backup, change the working copy, recover the earlier version, and open it. Include an application record where that is part of the protected work.\n\nJudge whether the recovered material is usable and whether the person can find the version they meant to restore. Explain the difference between synchronizing the newest copy and retaining versions that survive a mistake.\n\nLeave them with a routine they can inspect and a recovery process they understand. Later projects can add another destination or protect additional applications while keeping earlier backups accessible.\n"
    }
  ]
}