semantic-conflict-prediction

What problem does it solve?

Detects semantic conflicts that textual merges miss by analyzing code structure and intent so concurrent agent edits do not produce build or runtime breakages after merging. It finds mismatches like signature changes, transitive dependency breaks, and renames that standard git merges cannot surface.

Core Features & Use Cases

• AST-based symbol extraction: Use tree-sitter to identify functions, methods, classes, and exported symbols across polyglot repositories.
• Symbol-level claims: Model agent intent as read/modify/add/delete/rename claims at the function/method level to enable fine-grained coordination.
• Incremental dependency graphs and call/type edges: Build and update dependency graphs lazily to estimate blast radius and transitive impact of changes.
• Conflict prediction & scoring: Classify direct, dependency, and transitive conflicts with severity and confidence scores and produce suggested resolutions.
• Integration scenarios: Ideal for coordination daemons, Arbiters enforcing SymbolClaimConsistency, and multi-agent task assignment before work begins.

Quick Start

Ask the system to analyze two agents' pending symbol claims and report blocking or warning conflicts with explanations and confidence scores.