You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
easylogic edited this page Oct 15, 2026
·
2 revisions
Vision
Git: edit → stage → commit → push → branch → PR → merge. barocss-hub: edit → operation → synchronize → converge. History, checkpoints, review, and restore still exist, but synchronization does not depend on PRs or merges. The repository is a replicated data structure. It is not a Git wrapper and not an editor disguised as a VCS.
The repository is still a replicated data structure, and synchronization still never depends on PRs or merges. What changed is where the replicas live: an always-on server is the authoritative replica, and humans and AI agents work through thin clients (partial replicas) or the server API, sending ops in real time.
Convergence is unchanged: the CRDT op model decides every result, so there is no merge and no merge queue, also for agents writing through the API. Short disconnects are buffered and resent.
Full replicas remain the server's form and an opt-in for users (escalated, Online-First E-B4).
Superseded: any reading of this page as "every user holds a full, offline-first replica" (direction A, rejected by D-048). Spec: Online-First (Repository-Semantics §6).