Skip to content

Embodied AI Codesign Agent: Subtask Enumeration

In progress · updated 2026-10-30 · embodied-ai-architect/docs/plan/embodied-ai-codesign-subtasks.md

PlatformKey ConstraintsPrimary Perception Needs
Drones (UAVs)Weight, power, real-timeObstacle avoidance, landing zone detection, tracking
QuadrupedsPower, terrain adaptationGround plane estimation, obstacle detection, SLAM
BipedsBalance, human interactionFull-body tracking, gesture recognition, scene understanding
AMRsNavigation, safetySLAM, obstacle detection, path planning
Edge AI (static)Cost, power, deployment scaleDetection, classification, anomaly detection

SubtaskDescriptionData Structure
KB-HW-001Catalog edge compute platforms (Jetson, Hailo, Coral, Qualcomm, etc.)Hardware specs, benchmarks
KB-HW-002Catalog accelerator modules (NPUs, GPUs, DSPs)TOPS, power, interfaces
KB-HW-003Define hardware capability ontologyCompute, memory, power, thermal, interfaces
KB-HW-004Store validated benchmark results per hardwareModel × hardware → latency, power, accuracy
KB-HW-005Track hardware availability, pricing, lifecycle statusSupply chain metadata
SubtaskDescriptionData Structure
KB-MOD-001Catalog perception models (YOLO, RT-DETR, SegFormer, etc.)Architecture, params, FLOPs
KB-MOD-002Catalog model variants and quantization levelsFP32, FP16, INT8, INT4
KB-MOD-003Store accuracy metrics per task/datasetmAP, mIoU, accuracy
KB-MOD-004Define model capability tagsdetection, segmentation, tracking, depth, pose
KB-MOD-005Track model optimization formatsONNX, TensorRT, OpenVINO, TFLite, Hailo HEF
SubtaskDescriptionData Structure
KB-SEN-001Catalog camera sensors (resolution, FPS, interface)Specs, power, cost
KB-SEN-002Catalog depth sensors (stereo, ToF, structured light)Range, accuracy, power
KB-SEN-003Catalog LiDAR sensorsPoints/sec, range, FoV, power
KB-SEN-004Catalog IMUs and other proprioceptive sensorsAccuracy, drift, fusion requirements
KB-SEN-005Define sensor-to-model compatibility matrixWhat sensors feed which model types
SubtaskDescriptionData Structure
KB-UC-001Define drone perception use casesObstacle avoidance, landing, tracking, inspection
KB-UC-002Define quadruped perception use casesTerrain, obstacles, navigation, manipulation
KB-UC-003Define biped perception use casesHuman interaction, scene understanding, manipulation
KB-UC-004Define AMR perception use casesSLAM, navigation, safety, picking
KB-UC-005Define static edge AI use casesSurveillance, quality inspection, access control
KB-UC-006Map use cases to constraint profilesWhich dimensions matter, typical thresholds
SubtaskDescriptionData Structure
KB-CON-001Define latency constraint taxonomyReal-time tiers (1ms, 10ms, 33ms, 100ms)
KB-CON-002Define power constraint taxonomyBattery classes, thermal limits
KB-CON-003Define accuracy constraint taxonomySafety-critical vs best-effort
KB-CON-004Define cost constraint taxonomyConsumer, industrial, military
KB-CON-005Define environmental constraint taxonomyIP rating, temp range, vibration
KB-CON-006Create constraint implication rules“outdoor drone” → IP65, wide temp range

SubtaskDescriptionOutput
TOOL-ACC-001Analyze model accuracy on standard benchmarksmAP, mIoU, precision, recall
TOOL-ACC-002Estimate accuracy degradation from quantizationFP32 → INT8 accuracy delta
TOOL-ACC-003Assess accuracy for specific use case conditionsLow light, motion blur, occlusion
TOOL-ACC-004Compare model accuracy vs requirement thresholdPASS/FAIL with margin
SubtaskDescriptionOutput
TOOL-LAT-001Estimate inference latency on target hardwarems per frame, with confidence
TOOL-LAT-002Analyze end-to-end pipeline latencySensor → inference → output
TOOL-LAT-003Model latency under thermal throttlingSustained vs burst performance
TOOL-LAT-004Compare latency vs requirement thresholdPASS/FAIL with margin
SubtaskDescriptionOutput
TOOL-PWR-001Estimate inference power consumptionWatts during inference
TOOL-PWR-002Calculate energy per inferencemJ per frame
TOOL-PWR-003Project battery life for duty cycleHours of operation
TOOL-PWR-004Analyze thermal envelopeTDP, cooling requirements
TOOL-PWR-005Compare power vs budget thresholdPASS/FAIL with margin
SubtaskDescriptionOutput
TOOL-MEM-001Calculate model memory footprintWeights, activations, workspace
TOOL-MEM-002Analyze memory bandwidth requirementsGB/s needed
TOOL-MEM-003Check fit on target hardwareDoes it fit in RAM/VRAM
TOOL-MEM-004Analyze multi-model memory sharingConcurrent model memory budget
TOOL-MEM-005Compare memory vs hardware capacityPASS/FAIL with margin
SubtaskDescriptionOutput
TOOL-COST-001Estimate BOM cost for hardware configCompute + sensors + peripherals
TOOL-COST-002Analyze cost vs performance trade-offsPareto frontier
TOOL-COST-003Project volume pricing1, 100, 10K, 100K unit pricing
TOOL-COST-004Compare cost vs budget thresholdPASS/FAIL with margin
SubtaskDescriptionOutput
TOOL-PHY-001Analyze weight budgetCompute + sensors + structure
TOOL-PHY-002Check form factor compatibilityDimensions, mounting
TOOL-PHY-003Verify environmental ratingsIP rating, temp, vibration
TOOL-PHY-004Compare physical specs vs requirementsPASS/FAIL per dimension

SubtaskDescriptionOutput
TOOL-REC-HW-001Recommend compute platform for use caseRanked list with rationale
TOOL-REC-HW-002Recommend accelerator configurationNPU/GPU/DSP allocation
TOOL-REC-HW-003Identify hardware alternatives at different price pointsGood/better/best options
TOOL-REC-HW-004Flag hardware risksEOL, supply chain, thermal
SubtaskDescriptionOutput
TOOL-REC-MOD-001Recommend perception model for taskModel + variant + quantization
TOOL-REC-MOD-002Suggest model optimization pathPruning, distillation, quantization
TOOL-REC-MOD-003Identify model alternativesAccuracy vs latency trade-offs
TOOL-REC-MOD-004Recommend multi-model pipelineDetection → tracking → reasoning
SubtaskDescriptionOutput
TOOL-REC-SEN-001Recommend sensor suite for use caseCamera, depth, LiDAR, IMU
TOOL-REC-SEN-002Optimize sensor selection for constraintsPower, cost, weight
TOOL-REC-SEN-003Validate sensor-compute compatibilityInterfaces, bandwidth
SubtaskDescriptionOutput
TOOL-REC-SW-001Recommend OS and runtimeLinux, RTOS, specific distro
TOOL-REC-SW-002Recommend middleware frameworkROS2, Isaac, custom
TOOL-REC-SW-003Recommend inference runtimeTensorRT, ONNX Runtime, etc.
TOOL-REC-SW-004Identify SDK/toolchain requirementsVendor SDKs, compilers

SubtaskDescriptionOutput
TOOL-SYN-001Generate Pareto frontier for accuracy vs latencyVisualization + data
TOOL-SYN-002Generate Pareto frontier for power vs performanceVisualization + data
TOOL-SYN-003Identify constraint conflicts“Cannot meet both X and Y”
TOOL-SYN-004Suggest constraint relaxation options“Relax latency by 20% to meet power”
SubtaskDescriptionOutput
TOOL-SYN-005Generate complete system configurationHW + sensors + models + SW
TOOL-SYN-006Validate configuration consistencyAll components compatible
TOOL-SYN-007Estimate system-level metricsE2E latency, power, cost, weight
SubtaskDescriptionOutput
TOOL-SYN-008Generate executive summaryKey findings, recommendations
TOOL-SYN-009Generate detailed analysis reportAll metrics, evidence, trade-offs
TOOL-SYN-010Generate comparison reportMultiple configurations side-by-side
TOOL-SYN-011Export machine-readable resultsJSON/YAML for downstream tools

SubtaskDescriptionOutput
PLAN-001Extract platform type from querydrone, quadruped, biped, AMR, edge
PLAN-002Extract use case from queryobstacle avoidance, SLAM, tracking, etc.
PLAN-003Extract explicit constraints from queryLatency < X, power < Y, cost < Z
PLAN-004Infer implicit constraints from platform/use caseReal-time → latency, battery → power
SubtaskDescriptionOutput
PLAN-005Identify which analysis dimensions are relevantlatency, power, accuracy, memory, cost
PLAN-006Rank dimensions by criticality for use caseSafety-critical first
PLAN-007Identify dimension dependencies“If memory fails, latency irrelevant”
SubtaskDescriptionOutput
PLAN-008Map dimensions to analysis toolslatency → analyze_latency
PLAN-009Determine parallel vs sequential executionIndependent dimensions in parallel
PLAN-010Handle tool failures gracefullyRetry, fallback, partial results
PLAN-011Synthesize multi-tool results into answerAggregate verdicts, identify blockers
SubtaskDescriptionOutput
PLAN-012Detect when initial query is underspecifiedAsk clarifying questions
PLAN-013Propose alternatives when constraints conflictTrade-off options
PLAN-014Support “what-if” explorationRe-run with modified constraints

SubtaskDescriptionOutput
VAL-001Execute inference benchmark on local hardwareMeasured latency, power
VAL-002Execute inference benchmark on remote hardware (SSH)Measured latency, power
VAL-003Execute inference benchmark on cloud/K8sScaled benchmark results
VAL-004Store benchmark results in knowledge baseFeedback loop
SubtaskDescriptionOutput
VAL-005Run model on validation datasetMeasured accuracy
VAL-006Compare measured vs claimed accuracyValidation status
VAL-007Test accuracy under edge conditionsStress test results
SubtaskDescriptionOutput
VAL-008Validate sensor-compute integrationData flow verified
VAL-009Validate end-to-end pipeline latencyMeasured E2E timing
VAL-010Validate thermal behavior under loadSustained performance

  1. KB-HW-001 - Hardware catalog (start with 5-10 platforms)
  2. KB-MOD-001 - Model catalog (start with YOLO, RT-DETR, MobileNet)
  3. KB-UC-001 through KB-UC-005 - Use case templates
  4. TOOL-LAT-001 - Latency analysis tool
  5. TOOL-MEM-001 - Memory analysis tool
  6. TOOL-PWR-001 - Power analysis tool
  7. PLAN-001 through PLAN-004 - Query understanding
  1. TOOL-REC-HW-001 - Hardware recommendation
  2. TOOL-REC-MOD-001 - Model recommendation
  3. TOOL-SYN-005 - Configuration generation
  4. PLAN-005 through PLAN-011 - Full orchestration
  1. VAL-001 through VAL-003 - Benchmark execution
  2. VAL-005, VAL-006 - Accuracy validation
  3. Feedback loop to knowledge base
  1. KB-SEN-* - Full sensor catalog
  2. TOOL-SYN-001 through TOOL-SYN-004 - Trade-off analysis
  3. PLAN-012 through PLAN-014 - Iterative refinement

Tool NamePrimary SubtasksDependencies
analyze_latencyTOOL-LAT-001 to TOOL-LAT-004KB-HW, KB-MOD
analyze_memoryTOOL-MEM-001 to TOOL-MEM-005KB-HW, KB-MOD
analyze_powerTOOL-PWR-001 to TOOL-PWR-005KB-HW, KB-MOD
analyze_accuracyTOOL-ACC-001 to TOOL-ACC-004KB-MOD
analyze_costTOOL-COST-001 to TOOL-COST-004KB-HW, KB-SEN
recommend_hardwareTOOL-REC-HW-001 to TOOL-REC-HW-004All KB
recommend_modelTOOL-REC-MOD-001 to TOOL-REC-MOD-004KB-MOD, KB-UC
generate_configTOOL-SYN-005 to TOOL-SYN-007All analysis tools
run_benchmarkVAL-001 to VAL-003Target hardware

The Agentic AI is “perfectly organized” when:

  1. Complete Coverage: Every query type maps to available tools
  2. Accurate Verdicts: Tools return correct PASS/FAIL with evidence
  3. Fast Execution: Parallel analysis where possible, < 10s for typical queries
  4. Graceful Degradation: Missing data → UNKNOWN, not hallucination
  5. Actionable Output: Every FAIL includes a suggestion
  6. Knowledge Growth: Benchmark results feed back into knowledge base

Document created: December 2024 Status: Subtask Enumeration Complete