From 8164917f32a94bdfd4c91f07a07131c925a9c927 Mon Sep 17 00:00:00 2001 From: dave Date: Sat, 4 Apr 2026 20:14:39 +0000 Subject: [PATCH] huskies: create 477_spike_distributed_build_agents_via_bft_crdts_over_websocket --- ...ike_distributed_build_agents_via_bft_crdts_over_websocket.md | 2 +- 1 file changed, 1 insertion(+), 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 2109e8ed..bc14377d 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 @@ -16,7 +16,7 @@ Story markdown files (content/AC), worktrees, and config files remain on the fil ## Key Questions -1. **CRDT integration**: The BFT CRDT crate goes in `crates/`. How does it map to the current pipeline state model (stories in stage directories, agent assignments, retry counts)? Does it replace `.huskies/work/` or layer on top? +1. **CRDT integration**: The BFT CRDT crate goes in `crates/`. How does the CRDT document schema map to the current pipeline state model (stages, agent assignments, retry counts, blocked flags)? The CRDT replaces `.huskies/work/` stage directories as the source of truth for pipeline state. 2. **Work claiming**: Two nodes see a story enter current simultaneously. Design a CRDT-native claim mechanism (e.g. node ID + timestamp in the CRDT doc) so exactly one node runs the coder. What happens on conflict?