[P0] Unified Agent Memory (UAM) - Real-Time Agent Coordination

Problem Statement

Agentix agents operating in distributed cloud environments face critical coordination challenges:

• Identity Amnesia: Agents lose context after session compaction
• Blind Parallelism: No real-time visibility into what other agents are working on
• Merge Conflict Hell: Multiple agents editing same files create costly conflicts
• Dependency Blindness: No awareness of upstream/downstream code relationships
• Async-Only Communication: Git-based messaging has 30-60s latency

Architecture

Three-layer architecture:

| Layer | Purpose | Technology | Latency |
|-------|---------|------------|---------|
| L1: Git State | Persistent identity, session recovery | Git + .agentix/ | 30-60s |
| L2: Presence | Real-time status, file reservations | Redis/Azure Cache | <100ms |
| L3: OOB Bus | Instant messaging, coordination | Azure Service Bus | <50ms |

Key Components

1. Identity Manager: Persistent agent identity with cross-session continuity
2. Presence Service: Real-time agent status and availability
3. File Reservation System: Prevent merge conflicts BEFORE they happen
4. Dependency Graph: Track code dependencies for impact analysis
5. OOB Message Bus: Instant, secure messaging between agents

Success Criteria

| Metric | Current | Target |
|--------|---------|--------|
| Merge conflicts per day | 5-10 | < 1 |
| Session recovery time | 30-60s | < 5s |
| Agent awareness latency | 30-60s | < 500ms |
| Wasted parallel work | 20% | < 2% |

Implementation Phases

• Phase 1: Foundation - Identity, Session, Presence
• Phase 2: File Reservations
• Phase 3: OOB Messaging
• Phase 4: Dependency Graph
• Phase 5: Integration & Polish

Specification

Full specification: docs/specs/UAM_SPECIFICATION.md

Dependencies

• Azure Cache for Redis (to provision)
• Azure Service Bus (to provision)
• Azure Key Vault (exists)

---
Linear Issue: ONW-565
BEADS Issue: Agentix-myf