Logo
ScienceStack
Table of Contents
Fetching ...
Sign In

Why iCloud Fails: The Category Mistake of Cloud Synchronization

Paul Borrill

TL;DR

This document presents a unified analysis of why iCloud fails when composed with Time Machine, git, automated toolchains, and general-purpose developer workflows, supported by direct evidence including documented corruption events and a case study involving 366 GB of divergent state accumulated through normal use.

Abstract

iCloud Drive presents a filesystem interface but implements cloud synchronization semantics that diverge from POSIX in fundamental ways. This divergence is not an implementation bug; it is a Category Mistake -- the same one that pervades distributed computing wherever Forward-In-Time-Only (FITO) assumptions are embedded into protocol design. Parker et al. showed in 1983 that network partitioning destroys mutual consistency; iCloud adds a user interface that conceals this impossibility behind a facade of seamlessness. This document presents a unified analysis of why iCloud fails when composed with Time Machine, git, automated toolchains, and general-purpose developer workflows, supported by direct evidence including documented corruption events and a case study involving 366 GB of divergent state accumulated through normal use. We show that the failures arise from five interlocking incompatibilities rooted in a single structural error: the projection of a distributed causal graph onto a linear temporal chain. We then show how the same Category Mistake, when it occurs in network fabrics as link flapping, destroys topology knowledge through epistemic collapse. Finally, we argue that Open Atomic Ethernet (OAE) transactional semantics -- bilateral, reversible, and conservation-preserving -- provide the structural foundation for resolving these failures, not by defeating physics, but by aligning protocol behavior with physical reality.

Why iCloud Fails: The Category Mistake of Cloud Synchronization

TL;DR

This document presents a unified analysis of why iCloud fails when composed with Time Machine, git, automated toolchains, and general-purpose developer workflows, supported by direct evidence including documented corruption events and a case study involving 366 GB of divergent state accumulated through normal use.

Abstract

iCloud Drive presents a filesystem interface but implements cloud synchronization semantics that diverge from POSIX in fundamental ways. This divergence is not an implementation bug; it is a Category Mistake -- the same one that pervades distributed computing wherever Forward-In-Time-Only (FITO) assumptions are embedded into protocol design. Parker et al. showed in 1983 that network partitioning destroys mutual consistency; iCloud adds a user interface that conceals this impossibility behind a facade of seamlessness. This document presents a unified analysis of why iCloud fails when composed with Time Machine, git, automated toolchains, and general-purpose developer workflows, supported by direct evidence including documented corruption events and a case study involving 366 GB of divergent state accumulated through normal use. We show that the failures arise from five interlocking incompatibilities rooted in a single structural error: the projection of a distributed causal graph onto a linear temporal chain. We then show how the same Category Mistake, when it occurs in network fabrics as link flapping, destroys topology knowledge through epistemic collapse. Finally, we argue that Open Atomic Ethernet (OAE) transactional semantics -- bilateral, reversible, and conservation-preserving -- provide the structural foundation for resolving these failures, not by defeating physics, but by aligning protocol behavior with physical reality.
Paper Structure (53 sections, 3 equations, 3 figures)

This paper contains 53 sections, 3 equations, 3 figures.

Table of Contents

  1. Introduction: iCloud Is Not a Filesystem
  2. The Structural Thesis
  3. The Architecture of iCloud Drive
  4. The Coordination Layer
  5. Temporal Semantics: Last-Writer-Wins
  6. CloudKit and FoundationDB
  7. The fileproviderd Daemon
  8. Dataless Files and the Eviction Problem
  9. Incompatibility 1: Time Machine
  10. The Projection
  11. What Is Lost
  12. The Sonoma Cascade
  13. Restore Semantics
  14. Incompatibility 2: Git
  15. Git's Locking Model
  16. ...and 38 more sections

Figures (3)

  • Figure 1: A chain of nodes connected by AELinks. Charlie (below) forms a triangle with Alice and Bob, providing a recovery path when the Alice--Bob link fails. From borrill2026chiplet-summit.
  • Figure 2: Triangle failover as a three-party transaction. Charlie acts as the transaction manager (TM) for the Alice--Bob link, coordinating a 2PC recovery via the surviving links. Every triangle is a recovery resource; the role of TM rotates symmetrically among all three nodes. From borrill2026chiplet-summit.
  • Figure 3: A $3 \times 3$ octavalent substrate. Each XPU connects to its neighbours in all eight directions (N, S, E, W and all four diagonals) via direct AELinks. Every adjacent triple forms a triangle with a designated TM for each edge. The array extends indefinitely without switches, providing scale independence. From borrill2026chiplet-summit.