Sync.com

Build me a personal encrypted backup console using restic and storage I control as a narrow substitute for Sync.com. Requirements:

- Use Python, Typer, and the installed restic CLI. Configure one local source folder and one user-owned S3-compatible bucket or local repository; keep repository credentials and password outside source control.
- Provide setup preflight, backup, snapshot list, check, and restore-to-new-folder commands. Show the exact restic command and destination before each write.
- Save a dated run log with snapshot ID, source path, destination, status, and error text, but no passwords or object-storage credentials.
- A restore command refuses to target the source folder and verifies restored file count and selected hashes against the snapshot listing.
- Let me schedule backups through the operating system's scheduler and show the last successful run and any missed schedule. Keep repository retention as an explicit command with a preview.
- No accounts, telemetry, continuous two-way sync, live sharing links, team access, cross-device conflict resolution, or custom cryptographic code. Restic owns encryption and snapshot format.
- README: restic installation, S3 credential setup, recovery password handling, repository check, restore drill, and how this differs from Sync.com's sharing and sync service.

# AGENTS.md — Build guide for Sync.com

## Project scope
Back up and share selected folders, encrypt files client-side, track versions, and restore them from user-owned object storage.

Catalogue verdict: no. A consolation build is possible, but the paid product's decisive value sits outside a solo rebuild. For Sync.com, back up and share selected folders with client-side encryption and versioning. The hard boundary is zero-knowledge architecture, mature sync clients, sharing controls, and support, plus reliability, durability, and cross-device sync.
Use the implementation prompt below to define the deliverable. Complete each phase's acceptance checks before extending the scope.

## Working agreement
- Inspect the repository and its existing instructions before choosing paths, dependencies or commands. Keep one coherent stack and explain changes to the proposed architecture.
- Plan a vertical slice that accepts a real input and produces the useful output described below. Persist only the state the prompt calls for; respect memory-only and upstream-managed workflows. Use fixtures only when they are clearly labelled.
- After scaffolding, document the actual install, development, check and build commands in README and keep them synchronized with the package or project manifest. Do not report commands as successful unless they ran.
- Work in small steps. At handoff, list implemented flows, checks actually performed, remaining blockers, and any credentials or provider setup the owner must supply.
- Do not publish, spend money, contact customers, delete source data or run irreversible migrations without the project owner's authorization.

## Prerequisites
- user-owned server or S3-compatible bucket
- PostgreSQL
- MinIO or object storage
- desktop filesystem permissions
- backup key stored offline

## Stack and architecture
- Python and Typer
- Installed restic CLI
- User-owned S3-compatible or local restic repository
- Operating system scheduler

## Security and data integrity
- Use restic for encryption rather than inventing a cipher or sync protocol
- Keep repository password and object-storage credentials out of logs
- Restore to a new folder and verify before replacement

## Agent implementation rules
- Follow restic's current repository, backup, check, and restore documentation
- Make retention and restore operations inspectable

## Optional agent skills and references
No installable skill is listed for this guide; use the project rules and the stack documentation.

Read the linked SKILL.md and its dependencies before adding a skill. Select only the skills matching this project's runtime and task; their documentation does not supply API access, credentials or approval to perform external actions. Pin the reviewed revision where the tool supports it. Follow the chosen agent's documented project-level installation mechanism.

## Distribution ideas
These are optional planning notes. Obtain the owner's approval before publishing or contacting anyone.
- Present encrypted personal backups, without continuous sync or sharing claims

## Engineering roadmap
1. Wrap restic setup, backup, snapshot list, check, and restore in a CLI.
2. Record safe run logs and schedule status.
3. Document key custody, restore drill, and missing Sync.com features.

## Paid-product capabilities outside this build
- zero-knowledge architecture, mature sync clients, sharing controls, and support
- global sync network
- battle-tested conflict resolution
- ransomware recovery guarantees
- mobile clients and support

## Implementation prompt
Build me a personal encrypted backup console using restic and storage I control as a narrow substitute for Sync.com. Requirements:

- Use Python, Typer, and the installed restic CLI. Configure one local source folder and one user-owned S3-compatible bucket or local repository; keep repository credentials and password outside source control.
- Provide setup preflight, backup, snapshot list, check, and restore-to-new-folder commands. Show the exact restic command and destination before each write.
- Save a dated run log with snapshot ID, source path, destination, status, and error text, but no passwords or object-storage credentials.
- A restore command refuses to target the source folder and verifies restored file count and selected hashes against the snapshot listing.
- Let me schedule backups through the operating system's scheduler and show the last successful run and any missed schedule. Keep repository retention as an explicit command with a preview.
- No accounts, telemetry, continuous two-way sync, live sharing links, team access, cross-device conflict resolution, or custom cryptographic code. Restic owns encryption and snapshot format.
- README: restic installation, S3 credential setup, recovery password handling, repository check, restore drill, and how this differs from Sync.com's sharing and sync service.

## Completion evidence
Demonstrate the prompt's acceptance scenarios against the scoped workflow. Include setup from a clean checkout and failure recovery. Check persistence across restart and export/restore only for the state the prompt says to store; for memory-only tools, confirm that temporary content is discarded as specified. Record actual results and remaining limitations. A detailed plan alone does not establish a working replacement.