scene-lifecycle-composition-workflow

name	scene-lifecycle-composition-workflow
description	Operational workflow for composing scenes with explicit lifecycle ownership, signal boundaries, and instancing-safe refactor paths.
tier	operational
godot_version	4.6+
doc_anchors	["godot-docs/getting_started/step_by_step/nodes_and_scenes.rst","godot-docs/getting_started/step_by_step/instancing.rst","godot-docs/getting_started/step_by_step/signals.rst","godot-docs/tutorials/best_practices/scene_organization.rst"]
tags	["scenes","lifecycle","composition"]
depends_on	["godot-skills/godot-tertiary/scene-node-basics-contract/SKILL.md","godot-skills/godot-operational/scene-instancing-workflow/SKILL.md"]

Scene Lifecycle Composition Workflow

Use When

• Building new scene hierarchies with reusable child scenes.
• Refactoring scene trees that currently rely on fragile node paths.
• Stabilizing signal and ownership boundaries during scene growth.

Outcomes

• Scene composition boundaries remain stable under hierarchy changes.
• Lifecycle responsibilities are explicit per scene root/subscene.
• Signal wiring survives subtree moves and instancing updates.

Required Rules

• Assign one owning root per composed subsystem scene.
• Connect signals at composition boundaries, not deep leaf internals.
• Keep cross-scene dependencies explicit via injected references or contracts.
• Validate instancing contracts before and after hierarchy refactors.

Workflow

1. Define scene roots and ownership boundaries for each subsystem.
2. Instantiate child scenes through explicit composition points.
3. Wire signals between roots and managers at boundary nodes.
4. Perform subtree move/refactor rehearsal to test boundary resilience.
5. Run diagnostics and behavior checks after composition changes.

Validation

• Subtree relocation does not break runtime signal flow.
• Instanced scene updates do not introduce hidden path coupling.
• Scene enter/exit cycles leave no leaked connections.

Failure Modes

• Leaf-to-leaf node path coupling breaks on hierarchy changes.
• Ownership is ambiguous and mutation logic is split across scenes.
• Instancing contracts are implicit and drift during refactors.

Local Doc Anchors

• godot-docs/getting_started/step_by_step/nodes_and_scenes.rst
• godot-docs/getting_started/step_by_step/instancing.rst
• godot-docs/getting_started/step_by_step/signals.rst
• godot-docs/tutorials/best_practices/scene_organization.rst