feat(embabel): Phase 3 — Akces Platform Development Goals, Actions, and Conditions

[Copilot]

Higher-level Embabel Goals, Actions, and Conditions enabling agentic aggregates to reason about command processing, external event handling, and cross-aggregate coordination.

Conditions (@Configuration → ComputedBooleanCondition beans)

• IsCommandProcessingCondition — reads "isCommandProcessing" binding from blackboard; true during command handling
• IsExternalEventCondition — reads "isExternalEvent" binding; true during external event handling

Actions (@EmbabelComponent + @Action)

• SendCommandAction — routes a Command through the CommandBus for cross-aggregate coordination
• AnalyzeAggregateStateAction (readOnly) — serializes AggregateState to pretty-printed JSON via ObjectMapper; falls back to toString() on failure
• DiscoverAggregateServicesAction (readOnly) — formats Collection<AggregateServiceRecord> into a structured text summary (name, topics, type, commands, events)

Goals (@Configuration → Goal beans)

• ProcessCommandGoal — precondition: isCommandProcessing. Top-level goal replacing deterministic @CommandHandler for agent-handled commands
• ReactToExternalEventGoal — precondition: isExternalEvent. Top-level goal replacing deterministic @EventHandler for agent-handled events

Not implemented (per spec)

• EmitDomainEventsAction — events collected from Blackboard by AgentProcessResultTranslator
• ManageKnowledgeGoal — subsumed by LearnFromProcessGoal (Phase 2)

Notable API detail

Goal.Companion.createInstance() parameter order is (description, outputType, name) — not (name, outputType, description) as javap suggests. GOAP preconditions are added via .withPreconditions(...):

Goal.Companion.createInstance(
    GOAL_DESCRIPTION,
    Void.class,
    GOAL_NAME
).withPreconditions(IsCommandProcessingCondition.CONDITION_NAME);

Package: org.elasticsoftware.akces.agentic.agent
38 new unit tests (83 total in agentic module).

[jwijgerd]

will change the implementation plan