This documentation hub provides comprehensive guidance on agent coordination, multi-agent workflows, and orchestration patterns used throughout the METAINFORMANT project.
METAINFORMANT employs a multi-agent architecture where specialized AI agents and software components collaborate to execute complex bioinformatics workflows across 28 domains. This hub documents the coordination patterns, communication protocols, and orchestration mechanisms that enable seamless multi-agent operations.
In METAINFORMANT, an agent can refer to:
- AI Development Agents: Hermes Agent, Cursor AI assistants that write and review code
- Pipeline Agents: Software components that perform specific bioinformatics tasks (download, process, analyze)
- Workflow Managers: Orchestration agents that coordinate multi-stage pipelines
flowchart TB
subgraph A[Layer 1: AI Development Agents]
AI[Hermes Agent / Cursor AI]
AI -.->|writes code| DEV[Developer Workflow]
end
subgraph B[Layer 2: Coordination & Orchestration]
ORCH[Orchestration Layer]
subgraph OrchestrationComponents
WM[Workflow Manager<br/>BasePipelineManager]
PF[Pipeline Phases<br/>Stage lifecycle]
TM[Task Distributor<br/>ThreadPoolExecutor]
CM[Config Manager<br/>YAML/JSON configs]
end
ORCH --> OrchestrationComponents
end
subgraph C[Layer 3: Domain Pipeline Agents]
subgraph DomainAgents[28 Domain Modules]
DNA[DNA Analysis<br/>dna/]
RNA[RNA-seq & amalgkit<br/>rna/]
GWAS[GWAS Pipeline<br/>gwas/]
ML[Machine Learning<br/>ml/]
VIZ[Visualization<br/>visualization/]
end
DomainAgents -.->|use| CORE[Core Infrastructure<br/>metainformant.core]
end
subgraph D[Layer 4: Core Utilities]
IO[I/O Operations<br/>io.py]
LOG[Logging<br/>logging.py]
CFG[Configuration<br/>config.py]
PATH[Path Management<br/>paths.py]
PAR[Parallel Execution<br/>parallel.py]
end
AI -->|delegates to| ORCH
ORCH -->|orchestrates| DomainAgents
DomainAgents -->|leverage| D
D -.->|shared by all| DomainAgents
style AI fill:#e1f5ff
style ORCH fill:#fff4e1
style DomainAgents fill:#e8f5e9
style D fill:#f3e5f5
METAINFORMANT supports multiple coordination patterns:
- Sequential Pipeline - Stages executed in strict order (e.g., download → process → analyze)
- Parallel Fan-Out - Independent tasks processed concurrently (e.g., batch download of 8,300 samples)
- Conditional Branching - Workflow paths chosen based on data or config
- Fan-In Aggregation - Results collected from parallel workers for consolidation
- Event-Driven - Reactive execution triggered by data availability
This hub organizes documentation into the following sections:
| Section | Content |
|---|---|
| Architecture | System-level coordination architecture |
| Agent Directives | Rules and constraints for all agents |
| Orchestration | Workflow manager internals and usage |
| Multi-Agent Workflows | Complex workflow examples |
| Communication | Inter-agent messaging and data sharing |
| Safety | Error handling, validation, rollback |
| Best Practices | Configuration and operational guidelines |
Read Architecture to understand the layered design and coordination patterns.
Study Orchestration to learn how BasePipelineManager coordinates multi-stage workflows.
See Multi-Agent Workflows for practical examples of complex pipeline compositions.
Review Safety for error handling, validation, and rollback strategies.
- Core Module - Shared utilities (I/O, logging, parallel execution)
- RNA Module - Example of sophisticated orchestration (8,300+ samples across 28 species)
- Workflow Manager API - Source code reference
- Parallel Execution - ThreadPoolExecutor patterns
- Zero-Mocking Policy - Testing philosophy requiring real implementations