crdt-vterm

Collaborative terminal sharing with CRDTs uses s-expressions and GF(3) trifurcated conflict resolution to merge concurrent edits without data loss. Start by recording a vterm session with the Babashka recorder, then share live via P2P multicast. The system applies tri-queue input handling (MINUS, ERGODIC, PLUS) to deterministically resolve conflicts across participants.

Yes. Recorded sessions are stored as CRDT s-expression logs and can be replayed deterministically using the replay tooling. DuckDB indexing supports auditing merged sessions, and you can regenerate exact terminal states from the log for reproducible playback and collaboration verification.

CRDT-based sharing handles concurrent multi-user input without overwrites by applying GF(3) conflict resolution to track insertions, deletions, and concurrent edits as versioned s-expressions. Traditional recording captures sequential playback only; this approach ensures deterministic conflict resolution and live P2P synchronization across Emacs/vterm environments.

The Emacs bridge and vterm environment are the primary integration points for recording, replaying, and live sharing. Shadow buffers and CRDT sexp logs are managed within this ecosystem. The Babashka recorder handles session capture, and multicast P2P sharing works within the integrated toolchain.

GF(3) trifurcation splits concurrent edits into three queues (MINUS for deletions, ERGODIC for ergodic operations, PLUS for insertions) and applies field arithmetic to deterministically order conflicts. This ensures that concurrent terminal inputs from multiple users produce identical merged results regardless of arrival order.

The system integrates Babashka (bb scripts) for recording, Emacs replay for deterministic playback, and DuckDB indexing for session analysis. These tools work together to capture CRDT s-expression logs, enable reproducible terminal state recovery, and support multi-user session auditing.