manager-signal-architecture-workflow

name	manager-signal-architecture-workflow
description	Operational workflow for structuring scene coordinators, subsystem nodes, and signal wiring without global-framework creep.
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/signals.rst","godot-docs/tutorials/inputs/inputevent.rst","godot-docs/tutorials/best_practices/autoloads_versus_internal_nodes.rst","godot-docs/tutorials/best_practices/scene_organization.rst"]
tags	["architecture","managers","signals"]
depends_on	["godot-skills/godot-foundations/foundation-architecture/SKILL.md","godot-skills/godot-tertiary/event-hub-vs-signals-contract/SKILL.md"]

Manager Signal Architecture Workflow

Use When

• Systems are coupling through ad hoc node paths or sprawling buses.
• Manager responsibilities are ambiguous between global and scene-local scope.
• Signal graph is hard to trace or double-fires during scene churn.

Outcomes

• Scene-root coordinator and subsystem responsibilities are explicit.
• Signal wiring is centralized and lifecycle-safe.
• Global/autoload usage is limited to true cross-scene concerns.

Required Rules

• Prefer scene-root coordinators plus subsystem nodes before adding autoload managers.
• Connect gameplay-critical signals in one boundary location.
• Keep event channels descriptive and payloads explicit.
• Maintain single-writer mutation ownership separate from presentation listeners.

Workflow

1. Classify each manager concern as global service, scene coordinator, or subsystem node.
2. Define subsystem APIs and signal contract list.
3. Centralize signal connections at coordinator boundary and remove leaf-to-leaf wiring.
4. Replace broad global bus usage with local hubs where scope allows.
5. Validate scene reload/refactor resilience of wiring.

Validation

• Scene reload does not produce duplicate signal callbacks.
• Subtree refactor preserves event flow without deep-path rewiring.
• Mutation authority stays single-owner under event-heavy flows.

Failure Modes

• Global bus becomes hidden dependency injector and state hub.
• Multiple nodes commit gameplay state through side-effect listeners.
• Signals are used as polling substitutes and add event noise.

Local Doc Anchors

• godot-docs/getting_started/step_by_step/nodes_and_scenes.rst
• godot-docs/getting_started/step_by_step/signals.rst
• godot-docs/tutorials/inputs/inputevent.rst
• godot-docs/tutorials/best_practices/autoloads_versus_internal_nodes.rst
• godot-docs/tutorials/best_practices/scene_organization.rst