architect-implementor

You can automate infrastructure builds from YAML blueprints by providing scenario.yml and exploit.yml files, which are expanded into a complete implementation.yml that generates canvases, VLANs, and machines via MCP primitives.

Idempotent creation for security-lab scenarios means running the build process multiple times yields the same infrastructure state without duplicating resources. It validates schemas, checks budgets, and uses diary journaling to support resuming from partial builds.

You resume a partial build in an MCP workflow by leveraging diary journaling and checkpoint reports. The system tracks previous progress, allowing orchestration to pick up from the last successful state and complete remaining infrastructure allocation without restarting.

Yes, YAML scenario validation checks resource budgets automatically during expansion. Before generating the implementation file and allocating canvases, VLANs, and machines, the system performs budget checks to ensure the requested scenario fits within defined constraints.

You audit orchestration plugins for infrastructure deviations by running the scenario build, which reviews plugin behavior and surfaces deviations for user review. All audited changes are staged as drafts to ensure the implementation state matches the expected YAML blueprint.

Limitations of automating scenario expansion with MCP tools include dependency on the Rogue Arena MCP workflow environment and strict schema validation. If input YAML files fail schema checks or exceed budget limits, the build halts and cannot proceed until corrected.