spaces-architecture

What problem does it solve?

Coordinate massCode spaces state and IPC coordination to ensure consistent behavior across code, notes, math, and tools.

Core Features & Use Cases

• Space Model: code, notes, math, tools each with independent state, updates, and synchronization rules.
• Space State Storage: per-space state stored under spaces/{spaceId}/.state.yaml within vault, with runtime helpers to load and persist space state.
• IPC Rules: centralized space-specific IPC handlers and standardized events for reading and writing space data.
• Space-Aware Sync: system:storage-synced updates the active space and triggers appropriate refreshes across code, notes, math, and tools.
• Debounce & Persist: maintains reliable save behavior to avoid sync loops and data loss.

Quick Start

Follow the Space Architecture guidelines to initialize a new space by wiring its state, updates, and IPC routes to the vault structure.