Agentsociety Experiment Config

Experiment Config

Generate and validate experiment configuration (init_config.json + steps.yaml) for AgentSociety2 simulations.

When to Use

• User says "set up experiment", "configure simulation", "prepare experiment run"
• Hypothesis and SIM_SETTINGS.json exist and need init_config.json + steps.yaml
• User wants to validate, check, or fix an existing experiment configuration
• The simulation scale budget is known or has already been clarified

Do NOT use when:

• No hypothesis or SIM_SETTINGS.json exists yet (use hypothesis skill first)
• User wants to run the experiment (use run-experiment skill)
• Agent count, step budget, or runtime budget still need to be chosen. Resolve those before generating files.

Quick Reference

Use the Python interpreter from .env. See CLAUDE.md for setup.

Scale Planning

If the experiment size is still open, ask for the simulation scale budget before generating files. Collect the target agent count or range, step budget, runtime budget, and preferred complexity tier. Offer 2-3 options with trade-offs and a recommendation, then use the selected budget to balance agent count, agent complexity, and run length.

Entry Conditions

• HYPOTHESIS.md and SIM_SETTINGS.json already exist for the target experiment
• module names are already known, or can be confirmed with scan-modules when needed
• user_data/ has been reviewed before generating defaults
• the selected scale budget is available before freezing agent counts or step counts
• any external dataset requirement has already been resolved with use-dataset or create-dataset

Common Mistakes

Pipeline Position

Predecessors: hypothesis Optional helpers: scan-modules (when module names are unknown or need validation) Successors: run-experiment Optional branches: create-agent, create-env-module, create-dataset, use-dataset

Directory Structure

hypothesis_{id}/
├── HYPOTHESIS.md              # Hypothesis description
├── SIM_SETTINGS.json          # Agent classes and env modules selection
└── experiment_{id}/
    ├── EXPERIMENT.md          # Experiment description
    └── init/
        ├── config_params.py      # Claude Code generates this
        ├── init_config.json      # Generated configuration
        └── steps.yaml            # Generated steps

Workflow

digraph experiment_config {
    rankdir=LR;
    node [shape=box, style=filled, fillcolor="#E8F4FD"];

    subgraph cluster_phase1 {
        label="Phase 1: Validation";
        style=dashed;
        validate [label="validate"];
        prepare  [label="prepare"];
        info     [label="info"];
        read     [label="Read HYPOTHESIS.md\nEXPERIMENT.md\nSIM_SETTINGS.json\nuser_data/"];
    }

    subgraph cluster_phase2 {
        label="Phase 2: Code Generation";
        style=dashed;
        generate [label="Generate config_params.py\n(stdlib imports only)"];
    }

    subgraph cluster_phase3 {
        label="Phase 3: Execution";
        style=dashed;
        run   [label="run"];
        check [label="check"];
        fix   [label="Fix errors\n(if any)"];
    }

    validate -> prepare -> info -> read -> generate -> run -> check;
    check -> fix [label="errors"];
    fix -> run;
}

Phase 1 -- Validation

1. Run validate to confirm experiment setup and selected modules.
2. Run prepare to create init/ directory and config_params.py template.
3. Run info to display selected module details.
4. Read HYPOTHESIS.md, EXPERIMENT.md, SIM_SETTINGS.json, and user_data/ files.
5. Confirm the selected scale budget before freezing agent counts or step counts.
6. If the experiment depends on external data, resolve dataset search or upload first, then continue.

Phase 2 -- Code Generation

Generate config_params.py that:

• Uses only standard library imports (json, pathlib, csv)
• Reads from user_data/ directory
• Outputs valid init_config.json and steps.yaml to stdout
• Uses the selected scale budget to keep total runtime aligned with the requested simulation size
• Resolves external data dependencies through dataset search or upload before freezing defaults

Delegate to subagent when: the config involves many agents (10+) or complex step sequences (questionnaires, multi-phase interventions). Dispatch a subagent with all gathered Phase 1 context, instructing it to read subagent-prompts/config-generator.md and produce the script.

Do NOT delegate: simple configs with 1-3 agents and standard run/ask/intervene steps.

Phase 3 -- Execution

1. Run run to execute config_params.py and write output files.
2. Run check to validate generated files (instantiates modules to verify).
3. Fix any validation errors and re-run.

Configuration Structure

See references/config-structure.md for the full schema of init_config.json, steps.yaml, and the questionnaire step type.

Important Notes

1. Use class names as type identifiers (PersonAgent, not person_agent).
2. All parameters go in kwargs.
3. agent_id must equal kwargs.id.
4. Read user_data/ files before generating configuration.
5. Confirm the scale budget before writing final agent counts or step counts.
6. Questionnaire steps must include a non-empty questions list; each question needs id and prompt.
7. Choice questions must provide choices; validation will fail otherwise.

Documentation Sync

After generating configuration, update EXPERIMENT.md with configuration parameters and agent selection criteria.

Progress Tracking

After config.py check passes:

$PYTHON .agentsociety/bin/ags.py research-pipeline update-stage experiment_config completed