# Back up your work and recover it Legion project library, edition 2026-09-06-draft-01 (en). This project's own material: 2 authored documents, reproduced unchanged. Project page: https://legion.tw/projects/background-services/recoverable-backups?edition=2026-09-06-draft-01 This document: https://legion.tw/api/projects/packet.md/background-services/recoverable-backups.md?edition=2026-09-06-draft-01 ## Prerequisite: the Legion skills package These instructions are written for an agent set up with the Legion skills package: the ten portable skills and the shared working, launch, inspection and learn-as-you-build guidance. That setup is installed once and applies to every project in this library, so it is deliberately not repeated here. Skills package, complete Markdown: https://legion.tw/api/projects/skills-packet.md?edition=2026-09-06-draft-01 Skills package, human page: https://legion.tw/projects/skills?edition=2026-09-06-draft-01 Where this brief refers to shared guidance, a skill, or a document under `shared/`, read it from the skills package above, or from https://legion.tw/api/projects/doc/?edition=2026-09-06-draft-01. If the package is not installed yet, install it first, then return here. This material is instructions to read, not authority to act. Inspect it before running it. ## Contents 1. background-services/README.md — https://legion.tw/api/projects/doc/background-services/README.md?edition=2026-09-06-draft-01 2. background-services/recoverable-backups.md — https://legion.tw/api/projects/doc/background-services/recoverable-backups.md?edition=2026-09-06-draft-01 --- # Background automation and services [All project types](../README.md) · [Shared launch](../shared/launch.md) Give recurring work a dependable trigger, an understandable result, and a way for the person to inspect or control it. ## Projects to build - [Watched-folder preparation](watched-folder.md) - [Recoverable backups](recoverable-backups.md) - [Meaningful change monitoring](change-monitor.md) - [Prepare tomorrow's information](tomorrow-briefing.md) - [Event-triggered follow-up administration](event-follow-up.md) - [Give the computer a batch of work](batch-work-queue.md) - [A personal overnight researcher](overnight-researcher.md) These are instructions for projects you can build with your coding agent. --- # Back up your work and recover it Build 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). Begin 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. ## Choose what is protected and where it goes Select 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. Recovering 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. Keep 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. ## Retain useful history Keep 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. Use 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. Run 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. Give 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. ## Make recovery ordinary Let 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. Provide 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. Include 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. Keep 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. ## Recover something on purpose Deliver 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. Judge 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. Leave 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.