## Architectural Synergy Report: Beads & Overstory for CHORUS

**Goal:** Distill the most useful ideas from **Beads** and **Overstory** and show how they can be woven into a brand‑new **Rust‑based implementation of CHORUS**.

### 1. Beads – What CHORUS Can Borrow
- **Dolt-powered SQL DB:** Deterministic, mergeable data store for the state-machine graph.
- **Hash-based IDs:** Global uniqueness for P2P nodes.
- **Dependency-aware graph:** Encodes pre-conditions between state transitions.
- **Zero-conflict, cell-level merge:** Deterministic merging for concurrent P2P updates.

### 2. Overstory – What CHORUS Can Borrow
- **Agent Runtime Interface:** Pluggable execution engines (WASM, Rust, LLM).
- **Git worktree isolation:** Sandboxed file changes for agents.
- **SQLite mail system:** Lightweight, low-latency P2P messaging via WAL.
- **Tiered Watchdog:** Automated health-state machine for recovery.
- **FIFO Merge Queue:** Deterministic 4-tier conflict resolution.

### 3. UCXL – The Temporal Bridge
- **File-to-Metadata Mapping:** Watches worktrees and logs events to a temporal index.
- **Time-Travel Debugging:** Replay exact file modifications via `ucxl_events`.

### 4. Proposed Rust Architecture (CHRS)
- **chrs-graph:** Dolt-backed state transition engine.
- **chrs-worktree:** Git2-rs manager for agent sandboxes.
- **chrs-mail:** SQLite-based P2P gossip channel.
- **chrs-ucxl:** `notify`-based file event watcher.

---
*Generated by GPT-OSS-120B via opencode*
