One question that comes up early when evaluating an agent orchestration library is how it fits into an existing backend stack. If your services run on Spring Boot, Micronaut, or Quarkus, you want agents to live inside the same dependency injection container, use the same configuration system, and expose metrics through the same actuator endpoints. The interesting design decision in AgentEnsemble is that it has no framework dependencies at all. It is a plain Java 21+ library with a builder API. Framework integration is just a matter of wrapping those builder calls in whatever DI mechanism your framework uses. Nothing in the library changes. This keeps the core small and testable, but it also means the integration patterns are worth spelling out explicitly. The Builder API as the Integration Surface Every AgentEnsemble component -- agents, tasks, ensembles, memory stores, listeners -- is created through builders.…