# drosync production v1 `drosync` is the supported one-way synchronization path from customer-owned local directories to Baidu Object Storage (BOS). It is not a mounted filesystem: v1 does not download, propagate remote deletion, merge file contents, preserve POSIX ownership/mode, follow symlinks, or create empty remote directories. ## Frozen scope - Control plane: existing Go API plus the `drosync-coordinator` asynchronous worker. - Client: Rust CLI, daemon, tray GUI, updater, and SQLite crash journal. - UI: `/object-sync` with role-specific administration, operations, release, and audit surfaces. - Targets: Windows 10/11 x86_64, Ubuntu 22.04/24.04 x86_64, and macOS 13+ arm64. - Limits per session: 1,000,000 files, 1 TiB per object, 20 TiB total; 500 devices per organization and at most 16 client data requests per device. - Retention: session/item 90 days, versions/audit 1 year, heads indefinitely, staging/multipart 24 hours, conflicts indefinitely. ## Document map - [Product requirements](product-requirements.md) - [Architecture and state machines](architecture.md) - [OpenAPI 3.1 contract](openapi.yaml) - [Installation](installation.md) - [CLI reference](cli-reference.md) - [Permissions and security](permissions-security.md) - [Conflict runbook](conflicts-runbook.md) - [Audit dictionary](audit-dictionary.md) - [Operations and SLO](operations-runbook.md) - [Disaster recovery](disaster-recovery.md) - [Updates and rollback](update-rollout.md) - [Test and acceptance matrix](testing-acceptance.md) - [Decisions and external prerequisites](decisions.md) ## Safety invariant A space starts `blocked/unverified`. A successful `If-None-Match: *` probe permits create-only operation. Original-key update is available only after conditional update and conditional multipart completion probes pass and an administrator explicitly confirms that the shared prefix has no platform-external writer. Any observed drift disables the space. The UI cannot bypass these gates.