From 1d95ee17bb17e13701a02ad5d6bfec2e33e746dc Mon Sep 17 00:00:00 2001 From: dave Date: Sat, 4 Apr 2026 20:14:31 +0000 Subject: [PATCH] huskies: create 477_spike_distributed_build_agents_via_bft_crdts_over_websocket --- ...e_distributed_build_agents_via_bft_crdts_over_websocket.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/.huskies/work/1_backlog/477_spike_distributed_build_agents_via_bft_crdts_over_websocket.md b/.huskies/work/1_backlog/477_spike_distributed_build_agents_via_bft_crdts_over_websocket.md index c240a0d4..2109e8ed 100644 --- a/.huskies/work/1_backlog/477_spike_distributed_build_agents_via_bft_crdts_over_websocket.md +++ b/.huskies/work/1_backlog/477_spike_distributed_build_agents_via_bft_crdts_over_websocket.md @@ -10,7 +10,9 @@ Investigate integrating the existing BFT JSON CRDT Rust crate (to be placed in c ## Goal -Replace or augment the filesystem-based pipeline state with a CRDT document synced over WebSocket between nodes. Each node (Docker container on a different laptop) sees the full pipeline state and self-assigns work autonomously. No central scheduler. +Replace the filesystem-based pipeline state (`.huskies/work/` stage directories) with a CRDT document synced over WebSocket between nodes. The CRDT becomes the single source of truth for pipeline metadata (stage, agent assignments, retry counts, blocked flags). Each node (Docker container on a different laptop) sees the full pipeline state and self-assigns work autonomously. No central scheduler. + +Story markdown files (content/AC), worktrees, and config files remain on the filesystem. Only the pipeline orchestration state moves into the CRDT. ## Key Questions