# Decisions and external prerequisites ## Frozen decisions - Name/commands/packages/services: `drosync`. - Implementation: Go control plane and Rust client. - Direction: local to BOS only. - Conflict: automatic keep-both; never alter the original after a failed conditional commit. - BOS capability: fail closed until probed; do not auto-enable bucket versioning and do not rely on `x-bce-forbid-overwrite`. - Shared-prefix update: both technical conditional-update capability and administrator exclusivity confirmation are mandatory. - Credentials: long-lived device token until administrator revocation. - Existing Mongo BOS AK/SK representation remains, with the residual risk explicitly accepted. - Network: public direct access only in v1. ## External prerequisites that source code cannot satisfy - Windows Authenticode certificate/private key. - Apple Developer ID, installer identity, notarization profile, and Apple runner. - Linux GPG/package signing key. - CI runners for all three target operating systems. - `droboticflow` POC namespace, registry secret, Mongo secret, and dedicated BOS acceptance credential. - A cost-approved window for >5 GB copy, 1 TiB, and 20 TiB real BOS certification. - A dedicated Ed25519 audit/update signing key in the production key vault. These are release gates, not implementation defaults. Private keys must never enter Git. ## D-08 decision gate Until a real BOS probe supplies evidence: 1. unprobed/unsupported spaces cannot accept sessions; 2. conditional-create success permits only create; 3. conditional update plus conditional multipart completion and explicit prefix exclusivity permit original-path update; 4. any drift disables the space and requires reconcile plus explicit reopen. ## Open decision: `data_operator` session ownership The product contract says a `data_operator` can view and operate only "their own" sessions, but the current identity model does not bind a user to a device, credential, mapping, or sync space. The management API therefore currently has only an organization boundary and cannot enforce personal ownership without a product choice. Do not enable the `data_operator` role in production until one of these models is selected and implemented: - **A — device owner (recommended):** an administrator assigns one or more users when approving a device; sessions inherit the device owner and only those users can operate them. - **B — space assignment:** administrators assign operators to sync spaces; every assigned operator can operate all sessions in those spaces. - **C — organization-wide operator:** keep the current organization-wide visibility and explicitly redefine "own" as "within the operator's organization". This decision also determines reassignment behavior, historical-session visibility, and whether multiple operators may own the same device.