pCloud

Build me a focused file sync, sharing and backup workflow for the personal core of pCloud. Requirements:

- Use Next.js 15, TypeScript, PostgreSQL, MinIO, and a Tauri 2 sync client. Store version metadata, tombstones, device identifiers, and integrity checks in PostgreSQL.
- Paid product context: Sync and version selected folders against a user-owned object store. Build only this DIY scope: Sync selected folders against a user-owned object store, encrypt files client-side, track versions, and restore any version on demand.
- Add file history, point-in-time restore, key export, storage usage, and scheduled restore tests.
- Sync selected folders against a user-owned object store, encrypt files client-side, track versions, and restore any version on demand.
- Sync and version selected folders against a user-owned object store.
- Use a desktop window with source import, a work list, and result export. Required input or access: user-owned server or S3-compatible bucket; MinIO or object storage.
- Recovery: Provide upload and restore queues with pause, retry, bandwidth limits, and resumable transfers.
- Acceptance: with one labelled sample, show the input, saved intermediate state, and exported result; verify this invariant: An invalid input or interrupted operation must retain the source and show a recoverable state; exported records must reload with the same IDs.
- Out of scope: cross-platform clients, media playback, sharing, optional encryption, and lifetime operations; global sync network. Keep this a personal, inspectable workflow.
- Include a README with setup, a sample input, required keys or permissions, data location, and the supported scope.

# AGENTS.md — Build guide for pCloud

## Project scope
Sync selected folders against a user-owned object store, encrypt files client-side, track versions, and restore any version on demand.

Catalogue verdict: no. A consolation build is possible, but the paid product's decisive value sits outside a solo rebuild. For pCloud, sync and version selected folders against a user-owned object store. The hard boundary is cross-platform clients, media playback, sharing, optional encryption, and lifetime operations, 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
- Use Next.js 15, TypeScript, PostgreSQL, MinIO, and a Tauri 2 sync client.
- Store version metadata, tombstones, device identifiers, and integrity checks in PostgreSQL.
- Interface for this file sync, sharing and backup workflow: a desktop window with source import, a work list, and result export.

## Security and data integrity
- Provide upload and restore queues with pause, retry, bandwidth limits, and resumable transfers.
- Validate imported records and file paths; keep user data within the storage location named in the prompt.
- State the practical limit: cross-platform clients, media playback, sharing, optional encryption, and lifetime operations.

## Agent implementation rules
- Project rule, data: Store version metadata, tombstones, device identifiers, and integrity checks in PostgreSQL.
- Project rule, behavior: Add file history, point-in-time restore, key export, storage usage, and scheduled restore tests.
- Project rule, recovery: Provide upload and restore queues with pause, retry, bandwidth limits, and resumable transfers.

## 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.
- Demonstrate this file sync, sharing and backup operation with sample or user-owned data: Add file history, point-in-time restore, key export, storage usage, and scheduled restore tests.
- Show a concrete result or export: Add file history, point-in-time restore, key export, storage usage, and scheduled restore tests.
- State the practical limit: cross-platform clients, media playback, sharing, optional encryption, and lifetime operations.

## Engineering roadmap
1. Phase 1, architecture and data: Use Next.js 15, TypeScript, PostgreSQL, MinIO, and a Tauri 2 sync client. Store version metadata, tombstones, device identifiers, and integrity checks in PostgreSQL.
2. Phase 2, implement: Add file history, point-in-time restore, key export, storage usage, and scheduled restore tests.
3. Phase 3, implement: Sync selected folders against a user-owned object store, encrypt files client-side, track versions, and restore any version on demand.
4. Phase 4, review and output: Sync and version selected folders against a user-owned object store. Add file history, point-in-time restore, key export, storage usage, and scheduled restore tests.
5. Phase 5, recovery and acceptance: Provide upload and restore queues with pause, retry, bandwidth limits, and resumable transfers. Verify this invariant with a saved fixture: An invalid input or interrupted operation must retain the source and show a recoverable state; exported records must reload with the same IDs. State the practical limit: cross-platform clients, media playback, sharing, optional encryption, and lifetime operations.

## Paid-product capabilities outside this build
- cross-platform clients, media playback, sharing, optional encryption, and lifetime operations
- global sync network
- battle-tested conflict resolution
- ransomware recovery guarantees
- mobile clients and support

## Implementation prompt
Build me a focused file sync, sharing and backup workflow for the personal core of pCloud. Requirements:

- Use Next.js 15, TypeScript, PostgreSQL, MinIO, and a Tauri 2 sync client. Store version metadata, tombstones, device identifiers, and integrity checks in PostgreSQL.
- Paid product context: Sync and version selected folders against a user-owned object store. Build only this DIY scope: Sync selected folders against a user-owned object store, encrypt files client-side, track versions, and restore any version on demand.
- Add file history, point-in-time restore, key export, storage usage, and scheduled restore tests.
- Sync selected folders against a user-owned object store, encrypt files client-side, track versions, and restore any version on demand.
- Sync and version selected folders against a user-owned object store.
- Use a desktop window with source import, a work list, and result export. Required input or access: user-owned server or S3-compatible bucket; MinIO or object storage.
- Recovery: Provide upload and restore queues with pause, retry, bandwidth limits, and resumable transfers.
- Acceptance: with one labelled sample, show the input, saved intermediate state, and exported result; verify this invariant: An invalid input or interrupted operation must retain the source and show a recoverable state; exported records must reload with the same IDs.
- Out of scope: cross-platform clients, media playback, sharing, optional encryption, and lifetime operations; global sync network. Keep this a personal, inspectable workflow.
- Include a README with setup, a sample input, required keys or permissions, data location, and the supported scope.

## 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.