architect

The agent validates module availability before designing, discovers existing resources to avoid conflicts, and wires cross-resource dependencies using expressions before applying definitions via the Raptor CLI.

State discovery identifies existing resources to avoid conflicts before materializing new definitions. This ensures the agent considers current state and safely wires cross-resource dependencies during deployment.

Yes, the agent enforces a schema-first approach with dry-run options and robust error handling to ensure safe materialization of infrastructure definitions via the Raptor CLI.

The best way to wire cross-resource dependencies is through expressions within Facets resource definitions. The agent handles this automatically after validating module availability and discovering current state.

Yes, module validation is required before designing infrastructure. The agent validates module availability to ensure current state is considered and dependencies are correctly wired before materialization.

Schema-first infrastructure materialization prevents deployment errors by enforcing a strict validation process with dry-run options and robust error handling before applying resource definitions via the Raptor CLI.