Quick Start
Which Template Should I Use?
Templates at a Glance
| Industry | Key Agents | Highlights |
|---|---|---|
| Manufacturing | ParseOrder, CheckInventory, OptimizeSchedule, DefectDetect | Multi-format order processing, real-time inventory, production optimisation, quality inspection |
| Energy | SCADAReader, VibrationAnalyzer, PowerForecaster, MaintenanceScheduler | Wind-farm monitoring, vibration-based fault detection, power forecasting, predictive maintenance |
| Healthcare | VitalSignsCapture, EMRRetrieval, TriageRecommendation, ResourceAllocator | Emergency triage workflow, HIPAA-compliant data handling, ESI-based triage, resource allocation |
| Agriculture | MultispectralAnalyzer, DiseaseIdentifier, SprayRecommender, YieldPredictor | Drone/satellite multispectral analysis, pest/disease detection, targeted spraying, yield forecasting |
| Transportation | LiDARFusion, DisplacementCalculator, HeatmapGenerator, MaintenancePlanner | Tunnel/bridge LiDAR analysis, displacement tracking, safety heatmaps, predictive maintenance |
How It Works
All five templates share the same SRAO architecture — only the domain logic differs. Every step includes a fallback strategy — if an agent fails, the workflow degrades gracefully rather than crashing.Cross-Industry Reuse with IndustryAgentPattern
IndustryAgentPattern provides four factory methods that power ~70 % of every template:
| Method | Purpose | SLA param |
|---|---|---|
create_data_parser(name, domain, sla_seconds) | Extract/structure raw inputs | sla_seconds=30 |
create_resource_checker(name, resource_type, sla_seconds) | Verify availability | sla_seconds=5 |
create_optimizer(name, optimization_target, sla_minutes) | Find optimal solution | sla_minutes=2 |
create_inspector(name, inspection_type, sla_minutes) | Analyse quality/safety | sla_minutes=1 |
Pydantic I/O Schemas
Every template uses Pydantic models to enforce typed data between agents:| Industry | Input Schema | Output Schema |
|---|---|---|
| Manufacturing | OrderDetails | QualityReport |
| Energy | TurbineData | MaintenancePlan |
| Healthcare | VitalSigns | ResourceAllocation |
| Agriculture | MultispectralData | YieldForecast |
| Transportation | LiDARScan | MaintenanceSchedule |
Common Patterns
Add a custom tool to any agentBest Practices
Start with the prebuilt workflow function
Start with the prebuilt workflow function
Call
manufacturing_workflow(), energy_monitoring_workflow(), etc. before customising. These functions already wire up all agents and fallbacks in the correct order.Use Pydantic schemas for typed hand-offs
Use Pydantic schemas for typed hand-offs
Pass structured Pydantic objects (e.g.
OrderDetails, VitalSigns) between agents instead of raw strings. This catches type errors early and makes pipelines easier to test.Respect SLA targets per agent
Respect SLA targets per agent
Each agent declares its SLA in its instructions. Keep custom tools within those bounds — e.g. inventory checks must complete in ≤ 5 seconds to not block downstream agents.
Attribution: SRAO Framework
Attribution: SRAO Framework
These templates are based on the SRAO Framework (MIT). The
IndustryAgentPattern class provides the shared 70 % reuse layer.Related
Manufacturing Template
Order processing, inventory, scheduling, and quality control agents.
Energy Template
Wind-farm monitoring, vibration analysis, and predictive maintenance agents.
Healthcare Template
Emergency triage, EMR retrieval, and resource allocation agents.
Agriculture Template
Multispectral analysis, disease detection, and yield prediction agents.

