Terramate stack hierarchy limits on circular dependency detection

Terramate orchestrates Terraform configurations by managing stack hierarchies and generating repetitive code through templates. A critical aspect of this orchestration is the definition of dependencies between stacks to ensure the correct order of operations during deployment.

When defining complex architectures with deeply nested or interconnected stacks, there is a risk of introducing circular dependencies. While Terramate manages the generation phase, the specific behavior of the orchestrator when encountering recursive dependency loops in large-scale hierarchies remains unclear.

• Does the terramate generate command provide a deterministic validation check to prevent circular dependencies before file generation?
• What are the architectural limits for stack nesting depth before dependency resolution impacts performance?