Skip to content

Adding a New Industry

This guide provides a step-by-step process for adding a new industry to AgentV.

  1. Navigate to the industries/ directory in the root of the project.
  2. Create a new folder for your industry. The name should be lowercase and use underscores instead of spaces (e.g., real_estate, not Real Estate).
  3. Inside your new industry folder, create two sub-folders:
    • scenarios
    • datasets
  1. Inside the scenarios folder, you may want to create sub-folders for different use cases (e.g., crop_management in the agriculture industry).
  2. Create your first scenario .json file. The name should be numbered and descriptive (e.g., 01_mortgage_application_check.json).
  3. Populate the JSON file using the structure defined in the Evaluation Guide. Use existing scenarios as a reference.
  1. Add your new industry, its use cases, and core functions to the Core Functions Guide. These constructs relate to the industry, use_case, and core_function fields in your JSON files.
  2. Define the core functions to document their scope for future evaluators.

Realistic environments require data. If your scenarios require data (e.g., a CSV of customer transactions), you should link them via the dataset attribute.

Place your industry-specific database or transaction CSV/JSON files directly inside your industry’s datasets/ directory (e.g. industries/YOUR_INDUSTRY/datasets/records.csv), and reference them in your scenario metadata.

All scenarios are validated at load time against the AES schema. Your scenario must include these required fields:

Scenario level:

  • metadata: Contains id, name, capabilities, and aes_version (set to "1.4").
  • workflow: Contains nodes and edges.

Task Node level (each item in workflow.nodes):

  • id, task_description, success_criteria
  • (Optional) expected_outcome

Run schema validation locally:

Terminal window
agentv aes validate --path industries/YOUR_INDUSTRY/scenarios/YOUR_SCENARIO.json

Launch the dashboard to ensure your new industry and scenarios are appearing correctly in the library:

Terminal window
agentv console

Navigate to the Library tab to view your JSON structure and trigger a test run visually.