parallel-dispatch-ownership

To prevent merge conflicts with parallel AI agents, enforce MECE file boundaries ensuring parallel write agents never modify the same files. Exclusive write scope validation guarantees disjoint ownership, eliminating integration breakage during parallel feature decomposition.

MECE decomposition in parallel dispatch assigns mutually exclusive, collectively exhaustive file boundaries to write agents. This deterministic ownership model ensures every required change belongs to exactly one owner, preventing overlapping path claims across parallel sub-tasks.

Contract immutability is enforced by validating that BUILD-phase writers do not modify frozen contracts produced during DESIGN. Coverage and immutability checks ensure frozen specifications remain untouched while parallel write tasks execute independently.

Integration sub-tasks must run strictly after parallel write tasks complete in DAG-level dispatch planning. This timing constraint ensures aggregation files like routers, mains, registries, and global config are assembled safely without concurrent modification risks.

Validate disjoint write scopes by running pre-flight ownership validation before dispatching each DAG level. This checks for intersection, coverage, and contract immutability, aborting dispatch immediately upon detecting any overlapping file ownership violations.

Parallel agent dispatch fails after merging when ownership violations surface at merge points. Running post-merge verification detects overlapping write scopes and coverage gaps, requiring re-decomposition to restore MECE boundaries before retrying failed sub-tasks.