Skip to content

Fix example pipelines: 44 of 45 fail 'orchestrator validate' #104

Description

@jeremymanning

Background

During the removal of all mock/simulated functionality (#103), we discovered that many example pipelines use outdated syntax or reference non-existent functionality. To ensure we can properly test the core orchestrator functionality, we need to temporarily remove these examples and their associated tests.

Archived Examples

The following example YAML pipelines were archived and removed:

  • automated_testing_system.yaml
  • code_analysis_suite.yaml
  • code_optimization.yaml
  • content_creation_pipeline.yaml
  • creative_writing_assistant.yaml
  • customer_support_automation.yaml
  • data_processing_workflow.yaml
  • document_intelligence.yaml
  • financial_analysis_bot.yaml
  • interactive_chat_bot.yaml
  • multi_agent_collaboration.yaml
  • research_assistant.yaml
  • scalable_customer_service_agent.yaml

A complete backup of the examples directory has been saved at: /tmp/orchestrator_examples_backup.tar.gz (78KB)

TODO

Once the core orchestrator functionality is fully working with real models:

  1. Review archived examples - Check which examples use valid, current syntax
  2. Update example syntax - Ensure all examples follow the current YAML schema
  3. Verify real functionality - Each example should:
    • Use only real control systems and models
    • Not rely on any mocked or simulated behavior
    • Produce high-quality outputs when executed
  4. Test with various inputs - Examples should work for users with:
    • Different expertise levels
    • Various use cases and scenarios
    • Different model availability (OpenAI, Anthropic, etc.)
  5. Add comprehensive tests - Each example needs tests that:
    • Verify the pipeline executes successfully
    • Check that each step produces expected results
    • Manually validate output quality
    • Test with realistic user inputs

Related Issues

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingdocumentationImprovements or additions to documentationenhancementNew feature or requesthigh-priorityCritical issue that needs to be addressed ASAP

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions