architect-validator

You can validate a scenario directory by running mechanical invariants and cross-phase consistency checks. This process reconciles canvas-YML alignment and verifies invariant conditions across groups A-D to detect divergences before deployment.

Cross-phase consistency validation for scenario YML files checks mechanical invariants across groups A-D to detect divergences. It ensures scenario data aligns with the live canvas state and references schema documentation to prevent misconfigurations from reaching deployment.

Yes, validating scenario invariants requires MCP calls such as architect_vlan_list, architect_machine_list, architect_machine_get, and architect_assigned_plugin_get. These calls perform checks against live canvas state and reference schemas to verify cross-phase consistency.

Yes, you can validate hand-edited YML files or post-canvas changes using standalone validation. This operates independently of auto-triggered validation, which typically runs after architect-brainstorm Phase 4 completion, and generates a final validation report.

Validating canvas-YML alignment requires reading refs/exploit-design.md, refs/escape-hatch-plugins.md, and refs/scenario-schema.md. These reference files provide the schema definitions and plugin configurations needed to perform mechanical invariants checks and cross-phase consistency verification.

You should run scenario validation after completing architect-brainstorm Phase 4, after hand-editing YML files, or following any canvas changes. This pre-deployment validation detects mechanical invariants divergences and cross-phase inconsistencies before misconfigurations reach deployment.