CLI Local File Synchronization Workflow

Explains how CLI DevServer synchronizes local .airpds and .airpm files with Aircada Studio and Engine in real time.
Published: 7/10/2026

Dual-File Synchronization Architecture

Aircada provides real-time local file synchronization via CLI DevServer (aircada dev). This architecture bridges local project workspace files (datasets/*.airpds and option-models/*.airpm) with Aircada Studio and Engine.

text
LOCAL WORKSPACE                         AIRCADA ENGINE

┌──────────────────────┐   DevServer WS  ┌─────────────────────┐

│ datasets/*.airpds    │◄───────────────►│ Engine Hydration    │

│ option-models/*.airpm│  (aircada dev)  │ & Studio Adapters   │

└──────────────────────┘                 └─────────────────────┘

Key Synchronization Characteristics

1. Atomic File Write Protections: Writes to local .airpds and .airpm files use atomic .tmp $\rightarrow$ fs.rename operations, ensuring local files are never corrupted or truncated on disk.

2. updatedAt Timestamp Reconciliation: Startup handshakes compare updatedAt timestamps between local files and Engine state to establish single-source-of-truth reconciliation.

3. Live Studio UI Refreshes: Edits to .airpds or .airpm files trigger real-time onPricingModelAdapterReady view adapter updates in Web Studio UI without requiring full page reloads.

4. Echo Suppression: Content hashing prevents infinite sync feedback loops between disk watchers and WebSocket events.

About the Author

W
Wylie Chenoweth
Co-founder & CTO

Wylie Chenoweth is the CTO of Aircada. He leads the engineering team building the high-performance 3D rendering engine and tools, bringing over a decade of systems architecture and 3D web rendering experience.