[Evolution] Parallel Agent Coordination — Gitea Task Claiming Protocol ✅ #115

New Issue

NW · 2026-05-18T15:14:22Z

NW commented

2026-05-18 15:14:22 +00:00

Evolution Summary

Type: Parallel Coordination Hardening
Date: 2026-05-18T16:00:00+01:00

Problem

Parallel agent execution (implementation phase) had no conflict detection. Multiple agents could write to same files, create colliding migrations, overwrite each other on merge to dev.

Solution

Gitea comments as lock store: ## 🔒 Task Claim comments with machine-readable GNS_EVENT footer
Pre-emptive overlap check: Extract files_to_modify from each agent prompt → normalize → check intersection → serialize if overlap
Lease expiration: Claims auto-expire (checkpoint.budget.remaining * 0.05 min) to prevent deadlocks from crashed agents
Sequential migration timestamps: Orchestrator assigns timestamps, agents never self-generate

New Files

.kilo/rules/parallel-coordination.md — claim protocol, overlap check, agent entry verification, claim release, deadlock prevention, migration timestamps

Updated Files

.kilo/agents/orchestrator.md — Overlap Verification MANDATORY before parallel spawn + Implementation Phase parallel group
.kilo/capability-index.yaml — implementation_phase parallel group with claim_protocol, claim_timeout_min, migration_timestamp_assignment
.kilo/rules/gns-agent-protocol.md — task_claim and task_claim_release event types
.kilo/EVOLUTION_LOG.md — evolution entry #6

Commit

ded8e30 — feat(parallel-coordination): evolution — Gitea comment-based task claiming for parallel agent execution

Usage Example

Planner decomposes product catalog into 3 modules. Orchestrator checks file sets → no overlap → posts claims → spawns 3 agents simultaneously → each works in own worktree → posts releases → merge back to dev (no conflicts).

/close

## Evolution Summary Type: **Parallel Coordination Hardening** Date: 2026-05-18T16:00:00+01:00 ### Problem Parallel agent execution (implementation phase) had no conflict detection. Multiple agents could write to same files, create colliding migrations, overwrite each other on merge to `dev`. ### Solution - **Gitea comments as lock store**: `## 🔒 Task Claim` comments with machine-readable GNS_EVENT footer - **Pre-emptive overlap check**: Extract `files_to_modify` from each agent prompt → normalize → check intersection → serialize if overlap - **Lease expiration**: Claims auto-expire (`checkpoint.budget.remaining * 0.05` min) to prevent deadlocks from crashed agents - **Sequential migration timestamps**: Orchestrator assigns timestamps, agents never self-generate ### New Files - `.kilo/rules/parallel-coordination.md` — claim protocol, overlap check, agent entry verification, claim release, deadlock prevention, migration timestamps ### Updated Files - `.kilo/agents/orchestrator.md` — Overlap Verification MANDATORY before parallel spawn + Implementation Phase parallel group - `.kilo/capability-index.yaml` — `implementation_phase` parallel group with `claim_protocol`, `claim_timeout_min`, `migration_timestamp_assignment` - `.kilo/rules/gns-agent-protocol.md` — `task_claim` and `task_claim_release` event types - `.kilo/EVOLUTION_LOG.md` — evolution entry #6 ### Commit `ded8e30` — `feat(parallel-coordination): evolution — Gitea comment-based task claiming for parallel agent execution` ### Usage Example Planner decomposes product catalog into 3 modules. Orchestrator checks file sets → no overlap → posts claims → spawns 3 agents simultaneously → each works in own worktree → posts releases → merge back to dev (no conflicts). /close

NW changed title from ~~[Evolution] Parallel Agent Coordination — Gitea Task Claiming Protocol~~ to [Evolution] Parallel Agent Coordination — Gitea Task Claiming Protocol ✅

2026-05-18 15:14:29 +00:00

NW closed this issue

2026-05-18 15:14:29 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: UniqueSoft/APAW#115