Inspect geometry_nodes capability availability for the running Blender version. Create declared group inputs, then address nodes by stable names and sockets by identifier or explicit name—never by UI position. Keep instances until downstream editing or export requires realization.
Use recipe.procedural_courtyard for the supported courtyard layout and its update recipe for dimensions, arch count and rubble density. Preserve object and node-group names so cameras and references survive parameter changes.
Inspect group interface, nodes and links after construction; evaluate the resulting mesh and review density, scale, clipping and scene complexity visually. A node type unavailable in the running Blender version must return a capability error, not fall back to expert Python or silently install an extension.
When to Use
Use when reusable Geometry Nodes, parametric environments, repeated instances, or generative systems that can be updated through inputs are needed.
Prerequisites
- Clarify the Blender version, node capabilities, input parameters, stable names for objects/node groups, and performance budget.
- Record whether instances must be preserved and when realization is allowed.
Workflow
Step 1. Probe runtime node and socket capabilities; return a clear capability error when missing. Step 2. Create named group inputs, and establish nodes and links by stable node names and socket identifiers. Step 3. Validate topology and semantics with small-scale parameters, then expand density and scope. Step 4. Inspect the interface, nodes, links, and evaluated mesh, and review from a delivery perspective. Step 5. When updating, reuse stable names, change only declared parameters, and do not rebuild unrelated references.
Validation and Delivery Evidence
Report the node group interface, node/link list, input values, instance/realization status, evaluated geometry statistics, performance information, and preview.
Rules and Capability Boundaries (Not Applicable Scenarios)
Do not bypass missing nodes through expert Python or silently installing extensions; do not realize all instances when there is no downstream requirement.
Gotchas (Common Issues and Recovery)
- Socket mismatch: re-probe by identifier/name and do not rely on UI position.
- Scene too heavy: reduce density and preserve instances, and record the performance budget.
- Update breaks references: restore stable object and node group names, then re-validate dependencies.