feat: Agentic Aggregates Feature [Tracking Issue]

[jwijgerd]

Agentic Aggregates Feature

📋 Full plan: plans/agentic-aggregates.md

This is the tracking issue for the Agentic Aggregates feature — a new first-class concept in the Akces Framework that combines Event Sourcing with AI Agent capabilities.

An AgenticAggregate is a singleton instance that implements an Agent Loop, integrating with LLMs, MCP servers, and the Embabel agent framework. Unlike normal aggregates, it runs on a single Kafka partition, is long-running, and can perform I/O (MCP tool calls, LLM requests).

See the detailed plan: plans/agentic-aggregates.md

---

Phase Overview and Dependency Graph

Phase 1: API Foundation
        │
        ├──────────────────────┐
        ▼                      ▼
Phase 2: Agentic Module    Phase 3: Operator Support
  (concurrent with 3)        (concurrent with 2)
        │                      │
        └──────────────────────┘
                   │
                   ▼
        Phase 4: BOM & Integration
                   │
                   ▼
           Phase 5: Testing

Note on concurrency:

• Phase 1 must be completed first — all other phases depend on the API types it introduces.
• Phase 2 and Phase 3 can be implemented concurrently by separate developers after Phase 1 is done.
• Phase 4 requires both Phase 2 and Phase 3 to be completed.
• Phase 5 sub-phases can begin incrementally as their corresponding implementation phases complete:
  • 5.1 (API tests) → can start after Phase 1
  • 5.3 (Operator unit tests) → can start after Phase 3
  • 5.2, 5.4, 5.5 → require Phase 2 and Phase 3

---

Issues

Phase	Issue	Can Start After	Can Run Concurrently With
Phase 1: API Foundation	#TBD	—	—
Phase 2: Agentic Module	#TBD	Phase 1	Phase 3
Phase 3: Operator Support	#TBD	Phase 1	Phase 2
Phase 4: BOM & Integration	#TBD	Phase 2 + Phase 3	—
Phase 5: Testing	#TBD	Phase 1 (partial)	Phase 2, Phase 3 (partial)