ECC 2.0 Reference Architecture

Research summary from competitor/reference analysis (2026-03-22).

Competitive Landscape

Three-Layer Architecture

┌─────────────────────────────────┐
│        TUI Layer (ratatui)      │  User-facing dashboard
│  Panes, diff viewer, hotkeys    │  Communicates via Unix socket
├─────────────────────────────────┤
│     Runtime Layer (library)     │  Workspace runtime, agent registry,
│  State persistence, detection   │  status detection, SQLite
├─────────────────────────────────┤
│     Daemon Layer (process)      │  Persistent across TUI restarts
│  Terminal sessions, git ops,    │  PTY management, heartbeats
│  agent process supervision      │
└─────────────────────────────────┘

Patterns to Adopt

From Superset (Electron, 7.7K stars)

• Workspace Runtime Registry — trait-based abstraction with capability flags
• Persistent daemon terminal — sessions survive restarts via IPC
• Per-project mutex for git operations (prevents race conditions)
• Port allocation per workspace for dev servers
• Cold restore from serialized terminal scrollback

From dmux (Ink TUI, 1.2K stars)

• Worker-per-pane status detection — fingerprint terminal output + LLM classification
• Agent Registry — centralized agent definitions (install check, launch cmd, permissions)
• Retry strategies — different policies for destructive vs read-only operations
• PaneLifecycleManager — exclusive locks preventing concurrent pane races
• Lifecycle hooks — worktree_created, pre_merge, post_merge
• Background cleanup queue — async worktree deletion

ECC 2.0 Advantages

• Terminal-native (works over SSH, unlike Superset)
• Integrates with 116-skill ecosystem
• AgentShield security scanning
• Self-improving skill evolution (continuous-learning-v2)
• Rust single binary (3.4MB, no runtime deps)
• First Rust-based agentic IDE TUI in open source