Concurrency conflict in state.yaml and run artifacts during parallel FIRE execution (possible AIDC also)

[ovidiuadorian-yonder]

When multiple contributors run SpecsMD FIRE flows in parallel, shared state files are causing frequent merge conflicts and occasional state corruption.

Observed problem:

Concurrent writes to state.yaml from different users/sessions conflict.
Concurrent updates under .specs-fire/runs/ also conflict or become inconsistent after rebases/merges.
Manual conflict resolution is error-prone and can overwrite valid intent/run status updates.

Reproduction:

Two users start FIRE work in parallel in the same repository (different branches or the same integration branch).
Both execute planner/builder flows that update state.yaml and run metadata.
Merge/rebase one branch onto the other.
Git reports conflicts in state/run files; resolving may produce stale or incorrect final state.
Expected behavior:

Parallel runs should not require manual conflict resolution for shared runtime/state files.
Intent/run state should remain deterministic and merge-safe.

Actual behavior:

High conflict rate in state.yaml and run metadata.
Lost or inconsistent status transitions after merges.
Impact:

Slower team velocity.
Risk of incorrect FIRE state tracking.
Increased operational overhead for multi-user collaboration.

Suggested direction:

Move to per-user or per-run state shards with deterministic aggregation(maybe based on git user).
Or implement intent bases folders with no relation to others
Or make run/state artifacts append-only and conflict-tolerant by design.

[hancengiz]

hey 👋
thank you for the feedback, I udpated fire planner to use the current worktrees name in the run name so this way we would have and easier merge conflict resolution, in my cases it is mosty automatic. does it work for you?

https://github.com/fabriqaai/specs.md/blob/main/src/flows/fire/memory-bank.yaml#L96

[ovidiuadorian-yonder]

Hi @hancengiz, thank you for the updates. It works if you are using worktries, as you mentioned. However, if you are working with branches ( also in a multiple developer flow), the runs will have conflicting names when merging to main branch

[hancengiz]

I am currently adding the worktree name to the run name, I will update to include intent name as well, or branch name
I could probably do;
check if not on main worktree, add worktree as name,
if on main worktree, check branch name, if not main branch add branch name,
if on mai worktree, and on main branch, add intent name.

or I can just add intentname without that complexity. :) how is your workflow? do you work on branch on main worktree?

[ovidiuadorian-yonder]

I prefer to work on a branch; I think adding the intent name is enough.