multi-agent-mux/FUTURE_WORKS.md

FUTURE_WORKS.md

Purpose: Track future work candidates for the tmux_agent_orchestration project. For completed items, see DONE.md. Last Updated: 2026-06-21

---

Future Improvements Roadmap

Below is the list of pending future work items. These items were proposed based on the security and concurrency analysis in the Understand_Anything_Analysis.md report.

ID	Task	Priority	Effort	Domain / Description	Dependencies
FW-L4	Migrate Job Registry to SQLite to overcome NFS flock limitations	P3 (Low)	Large	Concurrency/Infrastructure Scalability: Similar to the Session Registry, migrate the individual JSON file lock (fcntl.flock) registry structure into an integrated SQLite database transaction structure, guaranteeing full reliability in distributed/network file systems like NFS.	Conditional (commence only when multi-host/NFS deployment is required)

---

Detailed Discussion Results & Directions (Reviewer Consensus)

1. Conditional Deferral of SQLite Integration (FW-L4):
   • Unlike the session registry, maintaining individual job data in JSON files is highly intuitive for management and debugging. Since the current deployment is constrained to a single-host local file system, fcntl.flock locks are sufficient. Thus, this is assigned a low priority (P3) and will be tackled conditionally.